6.7.0
Pre-releaseCatalogue 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).