Since the implementation of datalink service and its connection to the OAI interface, we now have two places where metadata are stored:
the general metadata (schema, tables, columns and functions)
the instance specific metadata (objects: fields, files, stacks, spectra...)
The first ones are stored in the django app database (i.e.: schema_metadata...) the second ones are stored in the form of the datalink tables (i.e.: tap_schema.datalink)
We offer three oai interfaces: oai_datacite, oai_dublin_core and oai_ivoa. Each of them provide a different metadata schemata using both the general and the specific metadata in different ways.
It would be a great importance to documents the exact mapping and origin of the provided metadata
Since the implementation of datalink service and its connection to the OAI interface, we now have two places where metadata are stored:
The first ones are stored in the django app database (i.e.: schema_metadata...) the second ones are stored in the form of the datalink tables (i.e.: tap_schema.datalink)
We offer three oai interfaces: oai_datacite, oai_dublin_core and oai_ivoa. Each of them provide a different metadata schemata using both the general and the specific metadata in different ways.
It would be a great importance to documents the exact mapping and origin of the provided metadata