Closed tomkralidis closed 1 year ago
I agree! If we consider this as an "external" component of wis2box, this is something that can be used independently. So, a ready to use containerised webapp? We will need "glue" between this and wis2box for the "publish" part. So, "import" the record in the wis2box, "publish" availability. Or something like that.
As it happens, ISRIC has been working on a metadata UI which works off a metadata schema to dynamically create a UI/UX. This is very powerful for validation and generation of any metadata. Excellent work here by @pvgenuchten.
We have since repackaged the project as part of the OSGeo ecosystem as mdme (Model Driven Metadata Editor). https://github.com/OSGeo/mdme, which we can use in wis2box in support of WCMP2. Load/validate/save workflow will work in conjunction with wis2box-api (pygeoapi API transaction endpoint).
Update:
A WCMP2 schema bundle is now available from https://github.com/wmo-im/wcmp2/blob/fix-schema/wcmp2-bundled.json
2 modes:
Auth:
Topic hierarchy:
@sabers: should be ready today with local tests.
Would be valuable to generate entire WCMP2 document for non-wis2box use cases.
@tomkralidis to point to Python code for implementation in admin ui.
wis2box-ui-admin uses Vue 2 because it is required by vjsf not by Vuetify. For instance, wis2box-ui uses Vuetify with Vue 3
First pass implemented in wis2box-ui-admin in experimental mode.
User story
As an operator, I want to have access to a user interface to manage discovery metadata, so that I can create discovery metadata using a web-based editor/wizard.
Acceptance criteria
Definition of done