Map date to schema.org temporalCoverage

[ezwelty]

Is your feature request related to a problem? Please describe.

For https://zenodo.org/records/15005624, I added a date as "1842-07-20/2023-08-01" with type {"id": "collected"} but this renders, in the schema.org JSON-LD as "temporal": ["1842-07-20/2023-08-01"]. I would have wanted and expected temporalCoverage to be used instead, see:

• https://schema.org/temporalCoverage (versus https://schema.org/temporal)
• https://github.com/ESIPFed/science-on-schema.org/blob/main/guides/Dataset.md#temporal-coverage
• https://developers.google.com/search/docs/appearance/structured-data/dataset

I believe temporalCoverage (and [spatialCoverage](https://schema.org/spatialCoverage)) are important for data discoverability. The DataCite date types does not contain coverage, but collected – or rather valid, since data for an earlier date may be collected at a later date – are the most appropriate.

See also zenodo/zenodo#567.

Describe the solution you'd like

Have a way to have temporalCoverage in the embedded JSON-LD of a Zenodo item page. This could be achieved by:

• explicitly mapping date of type valid (?) to temporalCoverage property with text value (rather than array of text)
• updating serializer tests

  invenio-rdm-records/tests/resources/serializers/test_schemaorg_serializer.py

  Line 104 in 7c47cdc

  "temporal": ["1939/1945"],

• updating documentation at https://inveniordm.docs.cern.ch/reference/metadata/#dates-0-n

[github-actions]

This issue was automatically marked as stale.