The title of your case study
Mapping from DataCite to Schema.org for datasets
Short title
DataCite-Schema.org
Summary
The schema.org metadata served from the DataCite API for data (and software) does not produce metadata that validates in the schema.org validator. Additionally, there are erroneous mappings of various contributor types, and terms included in the ESIP standard for describing datasets are not included in the mapping or are not updated to that standard. DataCite is interested in an updated mapping to be implemented in their API, both for mapping to schema.org and for mapping from schema.org.
Domain
Science data
Use case category
No response
Purpose of the mapping
- Translating DataCite metadata into Schema.org in a standard way centralizes that metadata generation into a trusted resource. Once the mapping is corrected, the correct schema.org metadata can be pulled from DataCite's API and then automatically inserted into dataset landing pages, increasing the discoverability of data across all sciences. (discovery, integration)
- This bases the creation of correct schema.org on DataCite metadata, which is regarded by publishers as the most trusted resource for metadata about data (and software). Schema.org metadata is commonly embedded on landing pages and websites to support discovery. (transformation)
- Data repositories are interested in measuring the potential increase in traffic on the data landing pages where this updated schema.org is embedded to aid in the search engine optimization, particularly as searching with AI tools becomes more commonplace. (analysis)
Type of mapped resources
Science datasets are supported by this mapping. Science software will be supported by another mapping effort led by CodeMeta.
Links to an existing mappings
SSSOM file
The sections of the mapping are also split out into multiple GitHub issues hosted by the ESIP Science-on-schema.org group.
Related Github issue
Tools used for creating the mapping
We did this by hand.
Type of mapping relations
We aimed to include all metadata fields included in the ESIP recommended for expressing science datasets on schema.org. ESIP link
Examples (samples) of different types of mapping implementations
DataCite's API
The title of your case study
Mapping from DataCite to Schema.org for datasets
Short title
DataCite-Schema.org
Summary
The schema.org metadata served from the DataCite API for data (and software) does not produce metadata that validates in the schema.org validator. Additionally, there are erroneous mappings of various contributor types, and terms included in the ESIP standard for describing datasets are not included in the mapping or are not updated to that standard. DataCite is interested in an updated mapping to be implemented in their API, both for mapping to schema.org and for mapping from schema.org.
Domain
Science data
Use case category
No response
Purpose of the mapping
Type of mapped resources
Science datasets are supported by this mapping. Science software will be supported by another mapping effort led by CodeMeta.
Links to an existing mappings
SSSOM file
The sections of the mapping are also split out into multiple GitHub issues hosted by the ESIP Science-on-schema.org group.
Related Github issue
Tools used for creating the mapping
We did this by hand.
Type of mapping relations
We aimed to include all metadata fields included in the ESIP recommended for expressing science datasets on schema.org. ESIP link
Examples (samples) of different types of mapping implementations
DataCite's API