- 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:
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 1)
- DEPENDING ON and IMPORT models are parsed (smarter model heuristic 1)
What could be a sollution here is to choose the referenceData before the whole model settings, so there could be a smarter model heuristic1.
- Passing it to import/update opengisch/QgisModelBaker#786 but not sure if this should be done
- 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
- repo (over ilidata) directly
- repo (over ilidata) over metaconfig
- Meta Config:
- locally (nyi)
- repo (over ilidata) directly
- XSLT Trafo (maybe)
- locally (nyi)
- repo (over ilidata) directly (nyi)
- 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)
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?
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)
- 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?
Schema Import Config -> Basket / BID Generator -> Data Import Config -> Sessions
https://excalidraw.com/#json=B_HLDPA6XqwIxbvO2rw-T,ootqxC_sHut2ym11WaEgZg