4. The persistent identifier must be embedded in the landing page in machine-readable format.

Short Title: 4. The persistent identifier must be embedded in the landing page in machine-readable format.
Source Documnent: A data citation roadmap for scholarly data repositories
Source Document Link: https://doi.org/10.1038/s41597-019-0031-8
Publishing Organisation: FORCE11.org and BioCADDIE Data Citation implementation Pilot Repositories Expert Group
Date of Publication: 2021-04-10
Topic: Discovery/ indexing/ search, Interlinking/ interoperability, Machine-actionability
Keywords: PID, identifier, landing page, machine-actionability, embedding
Addressed Stakeholders: data service providers
Full Text: To verify that a persistent identifier resolves to a correct landing page, the persistent identifier must be embedded in the landing page in human-readable and machine-readable formats. This enables checks that the persistent identifier properly resolves to a landing page describing that iden- tifier, and enables basic data citation by reference managers, and minimal validation by the publisher of persistent identifiers cited in documents. The persistent identifier should be found somewhere on the landing page, but is ideally embedded in schema.org markup and/or using HTML meta tags. Example schema.org/JSON-LD: <application type="application/ld+json"> {"@id": "https://doi.org/10.5061/dryad.q447c/3"} </application> Example HTML meta tags: <meta name="DC.identifier" content="https://doi.org/10.5061/dryad. q447c/3">

← Back