Examples
Worked examples
- Is an instance
The British Library leading the UK DataCite Consortium.
- Is an instance
TIB (Technische Informationsbibliothek) leading DataCite Germany.
- Is an instance
CSC – IT Center for Science leading the Finnish DataCite consortium.
Counter-examples
Looks similar, but isn't
- Not an instance
A bilateral repository partnership between two universities is not a DataCite consortium.
- Not an instance
Joining ORCID through a Jisc consortium does not give DataCite membership.
Editorial commentary
A DataCite consortium is a national or regional grouping of DataCite member organisations, coordinated by a single Consortium Lead that holds the master membership agreement with DataCite. Member institutions — Consortium Organizations in DataCite’s own terminology — join under that lead’s agreement, gaining the ability to mint DOIs for datasets, software, and other research outputs under a shared fee structure and shared local support model, without negotiating membership terms directly with DataCite.
What the Consortium Lead actually does
Beyond holding the contractual relationship, a Consortium Lead typically provides local-language support, training on DataCite’s metadata schema and API, and, in several countries, a shared repository or DOI-minting service that smaller member institutions can use instead of running their own infrastructure.
Real examples of consortium structure
The British Library leads the UK DataCite Consortium; TIB, which also operates DataCite Germany more broadly, leads the German consortium; CSC – IT Center for Science leads the Finnish consortium. As with ORCID, the specific type of body that leads a national consortium varies by country, but the underlying contractual shape — one lead, many recruited member organisations — is consistent.
How this differs from an ORCID consortium
A DataCite consortium and an ORCID consortium share the same organisational shape but are memberships in different registries. ORCID consortium membership buys Member-API access to the researcher-identity and affiliation registry; DataCite consortium membership buys the ability to mint DOIs for research outputs through the DataCite registry. Many institutions hold both simultaneously via entirely separate agreements and separate consortium leads — the two are not contractually linked, even where, as in Germany, related organisations happen to lead both.
Frequently asked questions
Does joining a DataCite consortium include ORCID membership?
No — the two are separate registries with separate consortium agreements, even where the same national body happens to lead both.
Can an institution mint DOIs without joining a consortium?
Yes — direct DataCite membership is available outside a consortium; joining through a consortium is a cost and support choice, not the only path to DOI-minting capability.
References
- DataCite, ‘DataCite Membership Models — Consortia’ (datacite.org/membership.html).
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="DataCite consortium"
vocab-term-identifier="https://casrai.org/dictionary/term/datacite-consortium" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/datacite-consortium",
"name": "DataCite consortium",
"identifier": "https://casrai.org/dictionary/term/datacite-consortium",
"description": "A national or regional grouping of DataCite member organisations led by a 'Consortium Lead' that holds the master agreement with DataCite, allowing member institutions to mint DOIs under a shared fee structure and shared support model.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/persistent-identifiers#set",
"url": "https://casrai.org/dictionary/term/datacite-consortium",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"author": {
"@id": "https://casrai.org/#editorial-team"
},
"datePublished": "2026-05-21T02:09:41",
"dateModified": "2026-08-22T15:52:33",
"inLanguage": "en-GB",
"isAccessibleForFree": true
}
