Crossref supports the collection of ROR IDs in the metadata we collect in order to help with the reliable identification and downstream use of affiliation data connected to research outputs.
“Author affiliations, and the ability to link them to publications and other scholarly outputs, are vital for numerous stakeholders across the research landscape. ROR is completely open, specifically focused on identifying affiliations, and collaboratively developed by, with, and for key stakeholders in scholarly communications.”" - Maria Gould, ROR Project Lead
What is ROR?
ROR is the Research Organization Registry – a global, community-led registry of open persistent identifiers for research organizations. The registry currently includes globally-unique persistent identifiers and associated metadata for more than 103,000 research organizations.
ROR IDs are specifically designed to be implemented in any system that captures institutional affiliations and to enable connections (via persistent identifiers and networked research infrastructure) between research organizations, research outputs, and researchers. ROR IDs are interoperable with those in other identifier registries, including GRID (which provided the seed data that ROR launched with), the Crossref Funder Registry, ISNI, and Wikidata. ROR data is available under a CC0 Public Domain waiver and can be accessed via a public API and a data dump.
](/images/services-images/ror-record.png)
Who is ROR?
ROR is operated as a joint initiative by Crossref, DataCite, and the California Digital Library, and was launched with seed data from GRID in collaboration with Digital Science. These organizations have invested resources into building an open registry of research organization identifiers that can be embedded in scholarly infrastructure to effectively link research to organizations. ROR is not a membership organization (or an organization at all!) and charges no fees for use of the registry or the API. Read more about ROR’s sustainability model.
For a long time, Crossref only collected affiliation metadata as free-text strings, which made for ambiguity and incomplete data. An author affiliated with the University of California at Berkeley might give the name of the university in any of several common ways:
- University of California, Berkeley
- University of California at Berkeley
- University of California Berkeley
- UC Berkeley
- Berkeley
- And likely moreâŚ
While it isnât too difficult for a human to guess that âUC Berkeley,â âUniversity of California, Berkeley,â and âUniversity of California at Berkeleyâ are all referring to the same university, a machine interpreting this information wouldnât necessarily make the same connections. If you are trying to easily find all of the publications associated with UC Berkeley, you would need to run and reconcile multiple searches at best, or miss data completely at worst.
This is where an affiliation identifier comes in: a single, unambiguous, standardized identifier that will always stay the same. For UC Berkeley, that would be https://ror.org/01an7q238.
Crossref members indicated that the ability to associate research outputs with organizations in a clean and consistent fashion was one of their most desired improvements to Crossref metadata. In January of 2022, therefore, Crossref added support for ROR IDs in its metadata schema and APIs.
Publishers and service providers can implement ROR in their systems so that submitting authors and co-authors can easily choose their affiliation from a ROR-powered list instead of typing in free text. Authors themselves do not have to provide a ROR ID or even know that a ROR ID is being collected. This affiliation information can then be sent to Crossref alongside other publication information.
If the submission system you use does not yet support ROR, or if you don’t use a submission system, you’ll still be able to provide ROR IDs in your Crossref metadata. ROR IDs can be added to JATS XML, and Crossref helper tools will start to support the deposit of ROR IDs. There’s also an OpenRefine reconciler that can map your internal identifiers to ROR identifiers.
ROR IDs for affiliations stand to transform the usability of Crossref metadata. While itâs crucial to have IDs for affiliations, itâs equally important that the affiliation data can be easily used. The ROR dataset is CC0, so ROR IDs and associated affiliation data can be freely and openly used and reused without any restrictions.
The ROR IDs registered by members in their Crossref metadata are available via Crossrefâs open APIs so that it can be reused by tools, services and anyone interested in this information. Examples include
- Institutions who want to monitor and measure their research output by the articles their researchers have published
- Funders who want to be able to discover and track the research and researchers they have supported
- Academic librarians who want to find all of the publications associated with their campus
- Journals who want to know where authors are affiliated so they can determine eligibility for institutionally sponsored publishing agreements
The inclusion of ROR IDs in Crossref metadata will eventually help all these entities make all these connections much more easily.
Get ready to ROR đŚ!
ROR is already working with publishers, funders and service providers who are integrating ROR in their systems, mapping their affiliation data to ROR IDs, and/or including ROR IDs in publication metadata. Libraries and institutional repositories are also beginning to build ROR into their systems and to send ROR IDs to Crossref in their metadata. See the growing list of active and in-progress ROR integrations for more stakeholders who are supporting ROR.
For information on how ROR IDs are supported in the Crossref metadata, you can take a look at this .xsd file (under the âinstitutionâ element) or in this journal article example XML. ROR also has some great help documentation for publishers and anyone else working with the ROR Registry.
Get in touch with ROR if you have questions or want to be more involved in the project. If you have questions about adding ROR IDs to your Crossref metadata, get in touch with our support specialists or ask on the Crossref Community Forum.
