DataCite DOI: Data & Software DOIs

Ask about DataCite DOI

Answers are drawn from this dictionary entry and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

DataCite is a global non-profit membership organisation, founded in 2009, that operates as a DOI Registration Agency for research outputs beyond the journal article — datasets, software, samples, instruments, dissertations, preprints, and other non-traditional outputs. Member organisations (data centres, institutional repositories, universities, national libraries) hold one or more DOI prefixes and deposit metadata, following the DataCite Metadata Schema, at the point a DOI is minted. A ‘DataCite DOI’ is any DOI registered through DataCite rather than through Crossref or another registration agency — the prefix alone does not tell you which agency registered it, but the metadata schema and the record returned by the DOI resolver do.

What problem DataCite solves

Before DataCite, research data generally had no persistent, citable identifier of its own — it lived inside a paper’s supplementary material, or on a lab website with no guarantee it would still resolve in five years. DataCite gives repositories a way to mint a permanent, resolvable identifier for a dataset (or software release, or physical sample) and attach structured, discoverable metadata to it, so that data can be cited, tracked, and linked back to the people and funders behind it in the same way a journal article can.

How a research office encounters DataCite

An institutional repository or data repository (Dryad, Harvard Dataverse, Zenodo, an institution’s own DSpace instance) mints a DataCite DOI when a researcher deposits a dataset.
A data management plan that requires deposited data to receive a ‘persistent identifier’ is, in practice, usually asking for a DataCite DOI — see the ‘Data Management Plan (DMP)‘ entry.
Research offices reconciling outputs across systems need to recognise that a dataset’s DOI and its associated article’s DOI were very likely minted by two different registration agencies (DataCite for the dataset, Crossref for the article) even though both resolve through the same doi.org infrastructure.
DataCite Commons aggregates DataCite’s own DOI metadata with ORCID (people) and ROR (organisations) records, giving a combined view of an institution’s or researcher’s outputs, affiliations, and funders in one place.

The DataCite Metadata Schema

Every DataCite DOI is registered with metadata conforming to the DataCite Metadata Schema, which defines a small set of mandatory properties (Identifier, Creator, Title, Publisher, PublicationYear, ResourceType) plus a large set of optional, repeatable properties covering contributors, funding, related identifiers, geolocation, rights, and versioning. This is what lets a DataCite DOI carry citation-ready information — not just an identifier, but the structured description needed to generate a formal citation automatically. See ‘DataCite metadata schema‘ for the full property list.

How it relates to other identifiers in this cluster

‘Crossref DOI‘ — the equivalent registration agency for journal articles, books, and conference proceedings; see ‘Crossref vs DataCite‘ for the full comparison.
‘ROR ID‘ — DataCite is one of ROR’s founding governance partners, and DataCite metadata records reference ROR IDs for organisational affiliation and funding.
‘OAI-PMH‘ — DataCite also exposes its metadata corpus for harvesting via OAI-PMH, alongside its REST API, so aggregators such as OpenAIRE can pull DataCite-registered records.

Frequently asked questions

Does every dataset need a DataCite DOI? No — funders and journals increasingly expect a persistent identifier for shared data, but not every dataset is required to have one; check the specific funder or journal data policy.

Can an institution mint its own DataCite DOIs directly? Yes, if the institution (or its repository) is a DataCite member or works through a DataCite member consortium and holds a DOI prefix; otherwise a repository like Zenodo or Dryad mints the DOI on the depositor’s behalf.

Is a DataCite DOI different from a Crossref DOI in format? No — both are ordinary DOIs (10.prefix/suffix) resolved through the same doi.org infrastructure; the difference is which registration agency holds the metadata and which schema that metadata follows.

References

DataCite, ‘About DataCite’ (datacite.org).
DataCite, ‘DataCite Metadata Schema’ documentation (schema.datacite.org).
Brase J., ‘DataCite — a global registration agency for research data’, Cooperation and Promotion of Information Resources in Science and Technology, 2009.

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="DataCite DOI"
      vocab-term-identifier="https://casrai.org/dictionary/term/datacite-doi" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/datacite-doi",
  "name": "DataCite DOI",
  "identifier": "https://casrai.org/dictionary/term/datacite-doi",
  "description": "A DOI registered through DataCite, the DOI Registration Agency that serves research data, software, samples, dissertations, instruments, and other non-article research outputs, accompanied by metadata in the DataCite Metadata Schema.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/persistent-identifiers#set",
  "url": "https://casrai.org/dictionary/term/datacite-doi",
  "sameAs": [
    "DataCite identifier"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-08-22T12:12:32",
  "inLanguage": "en"
}

DataCite DOI