modelbaker-wizard-redesign

modelbaker-wizard-redesign.md

Redesign of the Wizard 🧙

Motivation and components

• Model order issue: needs a sollution
• ReferenceData heuristic: make models magically appear (even if those referenceData are not chosen later on.
• UsabILIty Hub Metaconfig and Topping Selection
• New components:
  • OID (TID/BID) Generator
  • XSLT Integration

Model order issue

All info you can find here opengisch/QgisModelBaker#580

The requested improvements are:

• all models from repo in one command

Optional improvements are:

• evtl. ili2db improvement to be able to pass multiple ili-files
• warning when multiple ili-files are there from different folders
• XTF shouldn't recognize so many models that are imported anyway (smarter model heuristic ¹)
• DEPENDING ON and IMPORT models are parsed (smarter model heuristic ¹)

ReferenceData heuristic

What could be a sollution here is to choose the referenceData before the whole model settings, so there could be a smarter model heuristic¹.

UsabILIty Hub Metaconfig and Topping Selection

Requests and issues

• Getting it on project create opengisch/QgisModelBaker#479, opengisch/QgisModelBaker#768
• Passing it to import/update opengisch/QgisModelBaker#786 but not sure if this should be done

What are the sources and where do they come from?

• Model:
  • locally
  • repo (over ilimodel) directly
  • repo (over ilimodel) over metaconfig
• Reference Data:
  • locally
  • repo (over ilidata) directly
  • repo (over ilidata) over metaconfig
• Extra Meta Attribute File (toml):
  • locally
  • repo (over ilidata) directly (nyi)
  • repo (over ilidata) over metaconfig
• Project Topping:
  • locally (nyi)
  • repo (over ilidata) directly (nyi)
  • repo (over ilidata) over metaconfig
• Meta Config:
  • locally (nyi)
  • repo (over ilidata) directly
• XSLT Trafo (maybe)
  • locally (nyi)
  • repo (over ilidata) directly

Where do I need (or wish) to select them in the wizard?

• Model Selection: XSLT Trafo
  • XSLT Trafo File
• Schema Import: Meta Config
  • Meta Config
• Schema Import: Extra Meta Attribute File
  • Extra Meta Attribute File
• Data Import / Update: Reference Data
  • Reference Data
  • Meta Config (to get Reference Data from)
• Project Generation: Project Topping
  • Project Topping
  • Meta Config (to get Project Topping from)

New components

OID (TID/BID) Generator

TID and BID Manager one new page after Schema Import Config Page and before the Schema Import Session Page.

In case the expression are stored in the project (and not on DB) we need to configure it before the the Project Generate Session.

TID and BID part should be strictly split...

XSLT Integration

Transformation page needed before the Schema Import Config Page (maybe a sync with UsabILIty Hub needed).

Support on Drag'n'Drop or according to the model (UsabILIty Hub). Does it need to be linked to a model or automatically detect it?

Possible sollution approaches

Source Selection all on the same place (including UsabILIty Hub Widget)

https://excalidraw.com/#json=HCmpj_f1m_7CLtNUm2GZN,Mze_8oUqCZAJ50itVrRRKw

Means UsabILIty Hub Widget will disappear everywhere else (Schema Import Config and Data Import Config Page)

Consider

• Needs a heuristic, what is dominant when choosing a metaconfig and a projecttopping or a meta attribute file etc... Maybe best is that metaconfig gives the base and everything additional overrides metaconfig (same as manual configuration)
• This means on metaconfig selection the models appear there automatically (as well on referenceData selection?) - or no?
• It cannot catch all the cases: On Project Generation of existing DBs, we still need a separate UsabILIty Hub Widget.
• How powerfull is Schema Import Configuration Page anymore?

New workflow with sessions

Schema Import Config -> Basket / BID Generator -> Data Import Config -> Sessions

https://excalidraw.com/#json=B_HLDPA6XqwIxbvO2rw-T,ootqxC_sHut2ym11WaEgZg

Footnotes

1. model heuristic listing the models of interest in the schema config page - what models should be appended and what models should be checked etc. ↩ ↩² ↩³