ROR is operated as a collaborative initiative by California Digital Library, Crossref, and DataCite, in conjunction with a broad network of community stakeholders. Read more about ROR’s governance model, steering group, and community advisors.
During its first few years, ROR relied on a mixed funding model that included in-kind support from the three ROR governing organizations, contributions from supporting organizations, and grants. ROR is transitioning to a resourcing model where all staffing and core expenses will be supported entirely by the three ROR governing organizations. Additional funding from community supporters or future grants will be used to offset operating costs and support time-limited projects. Learn more about ROR’s business model.
The ROR roadmap is available on Github.
ROR is freely and openly available to anyone. There is no cost to access and use ROR data and services.
ROR is not a membership organization. As a community-based initiative, ROR has open channels for community participation, such as joining the community advisory group or giving feedback on development work. Learn more about how to get involved.
ROR defines “research organization” as any organization that is involved in research. To meet this definition, an organization should be involved in research in one or more of the following ways:
- Producing research
- Funding research
- Employing researchers
- Facilitating research
- Managing research
- Publishing research
- Educating researchers
ROR is focused on identifying “top-level” organization affiliations for research outputs. To meet the definition of “top-level” entity, an organization should be:
- A standalone organization
- Sufficiently independent from other organizations it might be related to
- Not a subdivision within an organization
Common types of entities that are out of scope for ROR include:
- Departments and subdivisions within organizations
- Companies that are not involved in research
ROR metadata includes basic relationships and hierarchies between top-level organizations, such as medical centers affiliated with a research university.
ROR is different from other organization identifiers in a few key ways:
- ROR is completely open (CC0 data, open API) and noncommercial
- ROR is focused specifically on identifying affiliations
- ROR is designed to be supported in core scholarly infrastructure (e.g., Crossref, DataCite, ORCID)
- ROR is developed as a community initiative
ROR first launched in 2019 using seed data from GRID, which had been selected as the foundational data source for ROR to start with and then build upon. As ROR began developing its technical infrastructure to support independent management of the registry, we coordinated updates via GRID and kept the two registries in sync while working toward a point of divergence.
In July 2021, GRID announced its plans to sunset its public data and officially pass the torch to ROR. GRID published its final public release in September 2021 and removed its public IDs in July 2022. ROR and GRID officially diverged when ROR published its first independent release in March 2022.
ROR has some overlap with the Crossref Funder Registry because many funding organizations are also included in ROR. ROR IDs map to Funder Registry IDs when one is available. Crossref plans to merge the Funder Registry into ROR at some point in the future.
ROR is supported and integrated in ORCID in several ways. ROR can be used with ORCID’s API and Affiliation Manager to record research institution identifiers and metadata, and it is the default identifier for affiliations manually added to a user’s record.
The ROR support site offers guidance for those integrating ROR in their systems. If you need additional support, reach out via the technical support discussion forum or send an email to firstname.lastname@example.org.
ROR has a REST API that supports retrieving, searching and filtering organization records in the registry. Consult the ROR support site for API documentation.
ROR is more than just an identifier: each record associated with a ROR ID contains useful information about the organization’s name in multiple languages, acronyms, aliases, location, website, Wikipedia page, and other persistent identifiers. See the ROR support site for the full model of the ROR data structure.
A ROR ID consists of a unique 9-character string appended to the ROR domain. The preferred form of a ROR identifier is the entire URL:
https://ror.org/02mhbdp94 rather than
02mhbdp94. The unique strings in ROR identifiers are assigned randomly, not sequentially, and contain no organizational information; therefore, the ROR ID of one organization cannot be predicted from the ROR ID of a related organization. The unique strings in ROR identifiers have a predictable pattern and can be validated with regular expressions.
In general, ROR IDs should operate behind the scenes, helping systems interoperate: there is usually no need for researchers to know the ROR ID of their institution and no need for institutions to display their own ROR ID. If you do choose to display ROR IDs and/or the ROR logo, please read and abide by our display guidelines.
ROR is being integrated by publishers, repositories, funding platforms, and other services. See a list of current integrations.
To suggest a new organization to be added to ROR, submit feedback via the curation request form.
To request a change to an organization’s ROR record, submit feedback via the curation request form.
The ROR registry is maintained through a centralized, community-based curation process. Organizations are not responsible for maintaining their own records in ROR. Anyone can suggest a new ROR record or a change to a ROR record via the curation request form.
ROR is updated on a rolling basis. Every request needs to go through a curation process before it can be incorporated into ROR. We aim to process requests as quickly as possible, but the timelines can vary depending on the complexity of the request and the volume of requests in the backlog.
Currently, releases are published approximately every month. You can track your request through the curation process by following it on Github.
Contact email@example.com if you have a list of organizations you would like to suggest for ROR.
After a request is submitted via the feedback form, an issue will be created in the ror-updates Github repository and added to a project board. You can track the status of your request by following the repository and by signing up as a watcher on the issue associated with your request.
ROR is updated on a rolling basis. New registry releases are published on Github and new data dumps are published on Zenodo approximately once a month. Following the Github repository and signing up to watch individual issues is the best way to be notified when a new release is available. Releases are also announced on Github, in the ROR Slack, technical support forum, and on Twitter.