Updates and curation

Requesting additions and changes

Anyone can request for a new organization to be added to ROR or for an existing ROR record to be changed via a public curation request form, which is linked to from each ROR record in the browser-based ROR search. You do not need to be affiliated with an organization to suggest changes to the organization’s record in ROR, since each request is evaluated on its own merits by ROR curators.

If you have more than one request, please submit a separate curation request form for each organization/record or create the corresponding issues in our ror-updates GitHub repository. The latter method requires a GitHub account, but it is generally faster to create a GitHub issue than to complete the form. If you have a large number of requests, please contact [email protected] for assistance.

Read more about how the registry is curated.


Does the organization already have a ROR ID?

Before submitting a request to add a new organization to ROR, be sure to search https://ror.org/search to see if it already exists.

Community-based curation model

ROR uses a community-based curation model to maintain the registry. After a registry request is submitted, the proposed change is reviewed by ROR’s metadata curation lead and, if necessary, by the volunteer ROR Curation Advisory Board to ensure it is in scope and in line with ROR’s metadata policies.

Approved changes are assigned to a future release and the records go through a metadata preparation process and schema validation check before they are deployed on the ROR production site and made available in the ROR API and data dump.

ROR curation activities are openly available in the ror-updates GitHub repository. Anyone can follow along with the curation process by watching individual issues in the GitHub repository and following their progress on the ROR Updates tracker


Not all requests are approved

We accept any and all requests for changes and additions to ROR records, but we do not approve all requests. We review all requests carefully and approve only those that are in line with ROR's scope and policies.

Update frequency and process

Changes to the ROR registry are made in batches and added to new versions of the entire registry, which are then released at least once a month, usually twice a month. An approved request therefore can take anywhere from a few days to 4 weeks to appear in the registry, depending on the timing of the request in relation to our release schedule. When a new version of the ROR registry is released, the data is immediately available in the ROR search interface, in the ROR API, and in the public ROR data dump on Zenodo. Learn how to download the data dump programmatically.

To see which records were added or modified in in a given release, see the ROR release notes on GitHub. Release notes for each release give a summary of the changes, the number of records added, the number of records modified, and a full list of added and modified records. Join the ROR Tech Forum to receive announcements of each new release.

Changes made in registry releases

Each new release of the ROR registry is different, but typically a new release includes modifications and additions requested by the public. The ROR Curation Lead and community curation board also initiate quality assurance and metadata reconciliation projects that result in new and updated records.


Changes to geographical information in updated records

Some geographical information in ROR comes from the GeoNames geographical database. When a ROR record is updated for any reason, geographical information from GeoNames is also updated, which can result in changes in other fields. Common examples include alteration of the values in fields lat (latitude) and lng (longitude) and removal of the value in the state_code field.

Other resources you might find helpful