Create UI for schema mapping

[benanhalt]

@grantfitzsimmons:

A user interface for mapping a Specify query to Darwin Core terms. This could be used multiple times throughout the interface, used to calculated MIDS levels for each record (#4604), share data easily to GBIF and other data aggregators, and much more.

[grantfitzsimmons]

At the very least, there should be support for carrying over the DWC terms established in 6. Is it very difficult to have those correspond with the term on their website?

I need to modify the structure of the XML and add term elements to each item in the query. Is there a way to make this process easier and at least convert the 6 mapping to a ready-to-go 7 format? @benanhalt

[maxpatiiuk]

@benanhalt @grantfitzsimmons would you like to meet and discuss a proper implementation of this?

From what I heard so far, it does not sound complicated.

[benanhalt]

I think Sp6 only records the DwC property name of the terms and not the name space. To be able to automatically convert the mapping we would have to make sure all the properties that Sp6 uses have unique fully qualified terms.

See: https://rs.gbif.org/core/dwc_occurrence_2022-02-02.xml
And https://rs.gbif.org/extensions.html

For the full implementation of the mapper, it should use those xml resources to generate the options in the UI.

[grantfitzsimmons]

Max:

Default mapping:
https://github.com/specify/specify6/blob/master/config/dwcdefaultmap.xml
Possible Terms:
https://github.com/specify/specify6/blob/master/config/tdwg_dwcterms.xsd

It seems like the bulk of the work is done, we just need to have the queries export in a way that a ton of manual user edits are not required.

[grantfitzsimmons]

Per my conversation with Max

It would require

• Schema mapper (QB with the ability to assign DwC terms to query fields)
• Schema mapping --> XML converter (which assigns term="" attributes for each line based on the assigned term)
• Automatic detection of User ID, collection ID, collection GUID, and function to create the ExportFeed with those valuess
• Ability to edit the XML of the ExportFeed
• DwC Metadata editor (XML/EML)

It looks to require both
The metadata would be a tough component since currently it’s on the user to literally go to GBIF and download already existing EML metadata. We don’t have a template to create it from scratch
And we’d have to either store or plug into the API for darwin core terms

[grantfitzsimmons]

So so so important. I cannot overstate the importance of this component, and it is not extraordinarily complex either.

After xml-editor has been added, I urge the team to seriously consider moving forward with this.