Metadata handling

[hvwaldow]

Problem

Currently the metadata-schema is hardcoded in ResourceBase. If GeoNode should be more used to cover the archive/publish/search/find - part of the research data life cycle, this setup will be a serious nuisance on different levels for a long time.

However, changing the situation likely involves large architectural changes.

Next to the technical solution, it is necessary to consider financing and startegiccal-political interactions with the GeoNode community (mainly GeoSolutions at the moment).

Material

• Notes Metadata Workshop @ 1. UG-meeting

[hvwaldow]

There should be a meeting (GeoSolutions Core Developer, ZALF, UFZ, TI) to develop requirements and possible approaches.

Who is organizing that?

[gannebamm]

We will discuss this topic further at the GeoNode user group meeting at the FOSSGIS. Likely, Helmholtz Metadata Collaboration will also join.

[gannebamm]

Thünen is working on a new metadata editor which shall enable configuration. You can see the discussion here: GeoNode/geonode#11511

[ridoo]

This work is making progress. Currently, a preview is deployed on https://development.demo.geonode.org

Note: The development is done on a metadata branch for GeoNode and geonode-mapstore-client. Looks quite good on a first glimpse. Good to see, they took over the idea to re-work their OpenAPI schema approach and use react-jsonschema-form to auto-generate forms from the schema 👍 .

Note: this client is rendered based on the OpenAPI schema mostly.

There is some detailed information about the Metadata API which will make it possible to better handle (custom) metadata using GeoNode API. However, with this in place the ResourceBase class will further be split up, so that metadata extensibility will become better maintainable. To be honest, I am not sure yet, though, how complex it will be, as metadata handlers put together the different parts of the metadata and metadata extensions. These have to handle related parts of the OpenAPI schema by themselves.