6.7.0

Catalogue dataset handling in wizard

On importing data you can mark a file as catalogue. If so, then there is no dataset selectable.

The data is imported to a dataset called Catalogueset. It stays technical and it's hidden for the user (It's not listed in the Dataset Manager, it's not listed in the Dataset Selector and it's not listed as option in the Relation Reference of the basket ids. On export it's not listed as dataset).

Export of baskets / models / datasets in wizard

On the data export page of the wizard you can filter for model(s) but also dataset(s) and basket(s).

In the ili2db doc they say you can use models or alternatively datasets or baskets (so this implies that you only use usually one of them). And it makes no conjunction (AND) but a disjunction (OR) if multiple parameters are given. A conjunction can still be done by selecting the smallest instance (baskets).

Getting catalogues from the UsabILIty Hub

On entering the Import Schema Configuration Page the ilidata.xml on the UsabILIty Hub repositories are parsed for the modelnames (from the listed models) and the type referenceData in the categories. There the modelLink properties are read and the models are loaded into the list of models to import automatically.

On the Import Data Configuration Page we have an autocomplete drop down containing the referenceData items (transfer files) found according all the models in the current database schema (not only the previously imported ones). You can add and remove them by +/-. xml files receive the default property that they are catalogues (considering the datasets).

6.6.7

• fix ilidata.xml parsing on title element

6.6.6

• The possibility to disable validation on import / export is provided again.
• Do not pass a dataset on import when it's not requested
• Allow to drop XML files on the source selection page
• Don't add unused models from the parsed XTF to the import list

6.6.5

• Fix weird dialog order in MS Windows
• Default CRS is 2056 instead 21781
• Update configuration change in ili2db command sessions when "going back" in wizard
• Wizard GUI improvements

6.6.4

• pass iface to Wizard to be able to generate QGIS projects

6.6.3

• Supports XTF model parsing on multiple lines.
• The strange window order (on MS Windows) introduced with 6.6.2 is reverted to the status before.

Known issues:

• The settings are not updated in wizard when going back #561
• Wizard dialog don't stays in front on MS Windows #564

6.6.2

• Dataset combobox stays stable on unexpected data sources (like an xtf file).
• Drop of multiple files (including ili-files) in QGIS opens source selection page in wizard.
• File list in source selection page supports drop of multiple files.
• Check the export-configuration instead of the import-configuration on export if there has been a basket handling.
• Wizard dialog stays always in front of QGIS.
• Only check the models in the import model list when same named models are not checked already.
• Only pass models as list in the same session/ili2db command when they are contained in the same ili file.
• Smarter parsing for models in xtf.
• Do not create nm-relation direct relation editor when already a relation_editor to the linktable has been created (because it's not a pure link table but with attributes instead).

6.6.1

• Validation of input (by disabling the button) in the Dataset Manager.
• Use of QGIS Theme icon (so no path problems in Windows) in the Workflow Wizard source selection page.
• Update all the configurations of the Workflow Wizard on the schema import config page. So on data import the same configuration is considered.
• Remove the empty Toolbar when refreshing (updating) Model Baker
• Correct topic parsing (e.g. when there are structures in the model that are not in a topic)
• Basket handling of tables having no topic, like structs that are used in multiple topics. There it should be possible to choose the dataset of it's parent. So all baskets are enabled for them:
  
• Fix error on trying to use an authentication configuration without super user
• Support Dataset Selector on layers using an authentication configuration
• Avoid error of Dataset Selector on layers using the (not supported by the Dataset Selector) PG service file

6.6.0

Workflow Wizard to import Interlis and Transfer Files / Generate Projects and Export Data

The user starts with the files (or the Interlis models chosen from a repository) as sources. According to this sources the workflow leads to the database configuration, the schema creation or the transfer file import. The Dataset Handling is fully integrated in the wizard as well as the export of the data to transfer files.

The icon on the left is to open the wizard - on the right you can see the icon to open the Dataset Manager (read below)

Dataset Integration

When --createBasketCol is active (with this release the default behavior) the layers have a t_basket column (ili2db) and the fields are integrated in the form. The layers t_ili2db_basket and t_ili2db_dataset are loaded in the project. They are needed to have the reference to them (to fill up t_basket in the single layers). For the layer t_ili2db_basket a display expression is created to provide the user a nice selection in the Relation Reference Widget of t_basket. The default value can be set over the Dataset Selector in the toolbar. New datasets can be created over the Dataset Manager.

Dataset Selector

With the Dataset Selector the user is able to select the dataset to be filled in as default value (actually the basket_id of the selected dataset and the topic of the current layer). The content of the Dataset Selector is loaded according to the layer's topic and datasource. The chosen basket_tid is stored in the project variables (<host>_<db>_<schema>_<topic> or <filepath>_<topic>) and accessed in the default expression of the layer's basket_tid field.

See the Dataset Selector Combobox in the Model Baker Toolbar

Dataset Manager

With the Dataset Manager the user is able to create and rename datasets as well as generate the baskets for each existing topic and the selected dataset.

Improved Relation Editor Widget creation

Multiple many-to-many connection over one link table

When having a relation pointing to a link table pointing to multiple parent tables, there is a relation editor widget created for each connection.

Set the direct cardinality and direct link to the linked table

For many to many relations the carnality is set to the the linked parent table. Exceptions are the link tables having additional attributes that are not foreign keys (associations with attributes).

Fixes

• Create tabs when the layer is the referenced layer (parent) and not when it's the child.
• Use save file browser for import data to have the ability to choose a non-existing file, because you can create the schema with ili2db Parameter --doschemaimport.
• Allow null in relation references always on domains - when the value is mandatory the constraints will concern that the user has to choose something.

6.5.2

• ili2db Version 4.5.0
• better Logtexts for UsabILIty Hub processes
• improved UX and fixes on changing models while having already metaconfiguration selected
• fix unreliable drop down on model search / metaconfiguration search
• avoid loading of invalid ili files (with wrong extensions)