Table 1 Guidelines for Repositories.
From: A data citation roadmap for scholarly data repositories
Level | # | Guideline |
|---|---|---|
Required | 1 | All datasets intended for citation must have a globally unique persistent identifier that can be expressed as an unambiguous URL. |
2 | Persistent identifiers for datasets must support multiple levels of granularity, where appropriate. | |
3 | The persistent identifier expressed as an URL must resolve to a landing page specific for that dataset, and that landing page must contain metadata describing the dataset. | |
4 | The persistent identifier must be embedded in the landing page in machine-readable format. | |
5 | The repository must provide documentation and support for data citation. | |
Recommended | 6 | The landing page should include metadata required for citation, and ideally also metadata facilitating discovery, in human-readable and machine-readable format. |
7 | The machine-readable metadata should use schema.org markup in JSON-LD format. | |
8 | Metadata should be made available via HTML meta tags to facilitate use by reference managers. | |
9 | Metadata should be made available for download in BibTeX and/or another standard bibliographic format. | |
Optional | 10 | Content negotiation for schema.org/JSON-LD and other content types may be supported so that the persistent identifier expressed as URL resolves directly to machine-readable metadata. |
11 | HTTP link headers may be supported to advertise content negotiation options |
