Examples
Worked examples
- Is an instance
A new biomedical institute requesting a ROR ID via the public submission form.
- Is an instance
A university merger resulting in a new ROR ID for the merged entity and 'predecessor' relationships on the originals.
Counter-examples
Looks similar, but isn't
- Not an instance
Editing a researcher's ORCID employment is not ROR curation.
- Not an instance
Updating a publisher's Crossref membership metadata is not ROR curation.
Editorial commentary
A request to add a new organisation, or to update, merge, or split an existing one, is submitted through one of three channels: ROR’s public curation request form, a GitHub issue against the ror-community/ror-updates repository (for requesters with a GitHub account, using dedicated new-organisation and update templates), or a bulk spreadsheet submitted by email for large batches.
Review and inclusion criteria
Requests are reviewed by ROR’s metadata curation lead against the registry’s published inclusion criteria — broadly, that the organisation produces, funds, facilitates, manages, publishes, or is otherwise involved in scholarly research, and that it is a collective, enduring entity rather than a single individual. Complex or contested cases are escalated to the volunteer ROR Curation Advisory Board, which also meets monthly to work through difficult cases and broader policy questions.
Release cadence
Approved changes are grouped and published as part of a data release at least once a month (in practice, batches are typically grouped every two to four weeks); the end-to-end turnaround from submitting a request to seeing it live in the registry is typically around four to six weeks. Major structural events — mergers, splits, dissolutions — are recorded through relationship fields and successor/predecessor links rather than by mutating or reissuing the previous ROR ID, which is what lets a citation or affiliation tagged years ago continue to resolve correctly even after the organisation it names has changed.
How this differs from Curated org record (ROR)
This entry covers the process — how a request moves from submission through review to a published release. Curated org record (ROR) covers the resulting artefact — the record’s structure and the identifier-stability guarantee that curation exists to protect. See also the CASRAI guide ROR ID: Why and How to Register for the institutional registration process end to end.
References
- ROR, ‘ROR Curation Policy’ (ror.org).
- ROR, ‘Journey of a Curation Request’ (ror.org/blog).
Also known as
ROR registry curation
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="ROR Curation"
vocab-term-identifier="https://casrai.org/dictionary/term/ror-curation" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/ror-curation",
"name": "ROR Curation",
"identifier": "https://casrai.org/dictionary/term/ror-curation",
"description": "The community-driven process by which the Research Organization Registry receives, reviews, and acts on requests to add new organisations, update existing records, merge duplicates, or split records, governed by a published curation policy and managed by ROR's curation team.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/persistent-identifiers#set",
"url": "https://casrai.org/dictionary/term/ror-curation",
"sameAs": [
"ROR registry curation"
],
"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:11:37",
"dateModified": "2026-08-22T16:17:05",
"inLanguage": "en-GB",
"isAccessibleForFree": true
}
