Update mapping*.csv files to make them valid

[ThomasreburG]

Motivation

The mapping*.csv files should be valid against https://gbv.github.io/sssom-js/

Modification

• Add object_source and subject_source curie
• Adjust object_source and subject_source accordingly
• Change mapping_set_id to URL to the mapping file
• fix column switches and capital curies in the table

Result

Creates valid JSON-LD mapping files

Related Issues

closes #460

[ThomasreburG]

open Questions:

• Check object_source , link owl or something similar
• Add mapping files as part of the release asset with own versioning
• Change mapping_set_id to curie or URL with w3id

[kara-mela]

Thanks for your improvements!

I just checked the files. The HI mapping does not validate for me. I copied the content into the validator and I receive

Missing mapping slots at line 20: subject_id, predicate_id, object_id, mapping_justification

For the rest, we need to discuss the following points

• panet prefix not working, w3id not resolving
• mapping_set_id does not include a version, but should
  - include in file name?
• mapping_set_version should be date of commit. The changes we are doing here also update the mapping. It should be reflected in the version.

[ThomasreburG]

If you have a csv file you have to choose SSOM/CSV. SSSOM/TSV is preselected. Otherwise you would have to paste a TSV file with tabs instead of ,

[kara-mela]

I received links for sssom-valid example files.

• mapping_set_id: is a url to the file in their repo: https://github.com/selgebali/datacite-metadata-toolkit/blob/main/mappings/datacite-dcterms.sssom.tsv
• additionally, they use mapping_set_version: 0.2.0 and mapping_date: 2026-05-22
  • in my opinion, these two information should reflect the last changes on the file
• w3id needs further discussion elsewhere