7.8.0

This release focuses on topping handling (UsabILIty Hub) but brings as well some improvements of the workflow wizard in general. It makes some missing bits available like for example the using of a project topping on generating a project and the possiblity to delete the data in the schema before import.

Improvements

UsabILIty Hub: Topping on Generate Project

Since ili2db 4.11 the id of the metaconfiguration file used to create the physical database is stored in the meta-tables. This means, on Project Creation we consider this id and provide the linked project topping.

Get Topping by selection

Still it's possible to disable it and choose another project topping file (YAML).

You can choose a project topping file (identified by model, db-type etc.) from the UsabILITy Hub repositories or as well a YAML file from the local system.

Why, project topping file

... and not "metaconfiguration* file?

Because on this step only project topping files are relevant. Metaconfiguration files are only relevant, when the schema is created. We thought about to provide them, to choose the same like on schema import, but this part is already provided by getting the topping from the DB.

Sponsors

Financed by Canton of Schwyz and the QGIS Model Baker Group

UsabILIty Hub: Filter Toppings according to the Database Source

Model Baker only provides the toppings that are made for the current database source (GeoPackage, PostgreSQL etc.) in case it's defined in the ilidata at the category with the key http://codes.modelbaker.ch/preferredDataSource. If there is no such category it's always displayed - so there are no backwards compatibility issues.

UsabILIty Topping Exporter

Here it detects what database sources are used and suggests you to optimize. You still can choose none.

Sponsors

Financed by the QGIS Model Baker Group

Delete before import

It is now possible to delete the existing data before importing new data. This means on using baskets, the ili2db parameter --replace is executed instead of --update. On not using baskets, the parameter --deleteData is added to the command. Note that on using baskets, only the data from the corresponding dataset is deleted, whereas on not using baskets all data from the schema is deleted.

Sponsors

Financed by the QGIS Model Baker Group

Busy bar to indicate that Model Baker is doing something

Sometimes the wizard has to load - mostly checking the repos to suggest data / reload the comboboxes. And there users are confused, what's happening. For this reason it does now disable the page (instead of just freeze) and show a busy indicator as a bar below the log panel.

Sponsors

Financed by the QGIS Model Baker Group

Other improvements

• Introduce prefix qgis.modelbaker for Model Baker specific Meta Attributes. See documentation
• With the UsabILIty Hub Topping Exporter the transaction mode of the project is exported as well and considered on generating a project using this topping.
• On generating a project the optimize strategy is stored to the project variables. This setting is then exported by the UsabILIty Hub Topping Exporter and considered on generating a project using this topping.
• Checkbox to use superuser in OID Manager
• Name OID and TID strictly "OID" to avoid confusions

Fixes

• Update schemas in separate task to avoid freezes in #854
• Check if the layer is a QgsVectorLayer before getting the fields in opengisch/QgisModelBakerLibrary#77
• Don't handle xml files 2 times in #845
• Display --- when no oid-domain defined in the OID Managerin #864

ili2db

Using ili2db version 5.0.1

Library

Using modelbaker library 1.7.0