UsabILIty Hub / Topping Naming

[signedav]

Some people complained about confusion when those names popping up.

In the Schema Import Configuration

In the Advanced Settings

In the Data Import Configuration

On Project Generation

as well in the log

And as UsabILIty Hub Topping Exporter

As confusing it seems, the naming is clearly defined. We have:

• Metaconfiguration File (the INI file containing the ili2db settings, linking to reference data (catalogue), meta attribute files and the project topping file)
• Project Topping (the YAML file containing all the infos used for the QGIS Project and linking to the needed topping files)
• Topping Files (all the Files used in this context: The reference data (catalogue), the meta attribute file, the project topping (see above) and the topping files needed by the project topping (like qml or qlr) files.
• UsabILIty Hub the whole Ecosystem and as well the Network of ilidata files (opengisch-repo and others) and maybe future hub for non-cantonal users...

Suggestions:

• Use the word topping only for the QGIS related files: project topping (YAML), additional topping files (files used by the project topping like QML etc)
• Use metaconfiguration, reference data, extra meta attribute file etc. no matter if they come from local system, repositories or UsabILIty Hub...
• Not mention UsabILIty Hub (because for an end user it makes no sense to make a difference if this is a file from UsabILIty Hub or another repository) - but very much hesitating. If we won't use the word in the Model Baker Plugin we shouldn't use it elsewhere. But do we want that? It described the whole solution until now quite good. But maybe it's only clear for me. Maybe it would be cool only to use it for the current models.opengis.ch Repository and in case there would be a "public" repository needed for that one...

In the Schema Import Configuration

Here it would be only "Metaconfiguration" and "[Seach metaconfig from repository]"

In the Advanced Settings

Leave it like it is.

In the Data Import Configuration

Remove "Topping" - maybe use "Referenced Data" and "[Search referenced data file from repository]"

On Project Generation

Leave it as it is.

as well in the log

Change accordingly.

And as UsabILIty Hub Topping Exporter

Name it just Topping Exporter.

[signedav]

@romefi Your opinion is much appreciated.

[romefi]

@signedav sorry for my late reply. I need some more time to think this trough. I fully understand the confusion with all the labels. In particular if you're not familiar with UsabILIty Hub. Maybe there's a way to simplify it even more and make the labels more understable to what they're actually for. I'll come back to you...

[beistehen]

As confusing it seems, the naming is clearly defined. We have:

• Topping Files (all the Files used in this context: The reference data (catalogue), the meta attribute file, the project topping (see above) and the topping files needed by the project topping (like qml or qlr) files.

This is my biggest struggle: A catalogue being referenced as a Topping File. The concept of transfer data and catalogue data has nothing to do with toppings so they shouldn't be mixed...

[signedav]

I guess you are right @beistehen Though I always thought that a catalogue is kind of a topping file when creating a schema with a model. Because it's in a way more part of the database structure than of the "Nutzdaten" and is used one time when creating the physical DB. Still, as suggested above, it might not be called topping...