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)

6.5.1

• fix on accessing dict values on getting topping files
• fix unreliable drop down on metaconfiguration selection widget

6.5.0

UsabILIty Hub integration

The idea of the UsabILIty Hub is to receive meta data like ili2db settings, layer styles and orders etc. automatically over the web. Like we can now receive models by connecting the ilimodels.xml of https://models.interlis.ch and with it's ilisite.xml many other repositories, we will be able to get this meta data with the file ilidata.xml on the UsabILItyHub (currently https://models.opengis.ch - could be in future models.interlis.ch as well or something else).

Information for ili2db and Modelbaker settings are configured in a metaconfiguration file (INI-file), as well as a link (id) to a file containing layer order and grouping information and a mapping to the qml files (containing style and attribute form configurations). These metaconfiguration files can be found by the Modelbaker according the chosen model (scanning ilidata.xml).

Fix Layernames for tables with multiple geometry columns

GeoPackage:
Fix layernames on tables that are created twice in geopackage and contain the iliname with brackets (e.g. KbS_LV95_V1_4.Belastete_Standorte.Belasteter_Standort.Geo_Lage_Punkt(KbS_LV95_V1_4.Belastete_Standorte.Belasteter_Standort)) They are now named Belasteter_Standort (Geo_Lage_Punkt) This fixes #469

Postgres:
On creating layers from a Postgres dataset where a table has multiplegeometry columns, this table is loaded for each geometry column. To have a unique name, we check for duplicate tablenames and if we found one we check out the t_ili2db_attrname for the geometry column and add it's proper name to the table.

No double loading of layers in layertree

On having a project open and importing an additional model into the same schema /db file, the layers are reloaded and double. So the fix is, that it does not reload the already existing layers (considering it's datasource).

6.4.0

• ili2db version 4.4.6
• Drop XTF / ITF improvements (not overriding QGIS behavior)
• Fix model directory support of % values

6.3.4

Fixes

• Support to drag and drop XTF/ITF files to import data

6.3.3

Fixes

• Use internal packaging library

6.3.2

Fixes

• Support Java path with spaces again
• Support newer Java (>1.8.0)