Report a bug or request a featureContact support
Guides

Transition from Open Funder Registry to ROR

Suggest Edits

In September 2023, Crossref and ROR announced a long-term plan to deprecate the Open Funder Registry (formerly known as FundRef) and merge it into ROR, the Research Organization Registry. We're thrilled that ROR is set to become the standard identifier for funders, and we're determined to help make this transition as easy as possible for all concerned. Here are some answers to frequently asked questions about this transition, including guidance on how to switch from using Funder IDs to using ROR IDs.

Why is this transition happening?

Merging the two registries will make workflows more efficient and less confusing for all concerned while allowing ROR and Crossref to develop new services to support the funding use case, such as improving funder matching. The Open Funder Registry currently includes about 44,000 IDs and records for funders, and a large majority of the most-used of these Funder IDs already exist in ROR, with others being continually added through ongoing curation work. Funders, publishers, and others should not need to decide whether to use Funder IDs or ROR IDs and should not need to use both: a single registry, ROR, can fulfill the purpose of identifying research organizations -- including funders.

When is this transition happening?

This transition is happening now! Users of the Open Funder Registry can begin the work of switching to ROR at any time. ROR's data structure has always included an external identifier field to enable mapping of ROR IDs to Funder IDs, and ROR has been working since 2022 to add and update ROR records from Open Funder Registry data. The Open Funder Registry will continue to be updated through at least the end of 2024, and the existing technical infrastructure for the Open Funder Registry will remain available while Crossref works to support ROR IDs for funders by updating schemas and APIs and by building and improving tools to automatically map Funder IDs to ROR IDs and match funder names to ROR IDs.

Will every Funder ID have a corresponding ROR ID?

Our aim is to provide comprehensive coverage of Funder IDs that are widely used, are not duplicates or errors, and are in scope for ROR. Based on our analysis of funding data in Crossref, DataCite, and ORCID metadata, about one-third of the Funder Registry accounts for the majority of actual usage, so we’re creating and updating ROR IDs for funders on this basis. Currently, there are ROR IDs for over 94% of cases where a Funder ID is used in DataCite and Crossref DOI records. We will continue to improve this coverage during 2024 to bettter support the funding use case. See How ROR and the Funder Registry Overlap to learn more and check the ROR / Funder Registry Overlap tool for current data on Funder ID to ROR ID mapping.

Will Funder IDs continue to resolve?

Absolutely! Funder IDs are DOIs, and as such are persistent. The Funder ID for the Alfred P. Sloan Foundation, for instance, is <https://doi.org/10.13039/100000879> (or 100000879 in some usages), and Crossref will ensure that all such Funder IDs continue to resolve to a page with information about that funder.

Will the Crossref Funder API remain available?

Yes, Crossref will maintain the current funder API endpoints at https://api.crossref.org/funders at least until ROR IDs become the predominant funding identifier for newly registered content, and perhaps beyond.

Will the Crossref Funding Data search remain available?

Yes, Crossref will maintain the current funding data search, which connects funders to published works, at least until ROR IDs become the predominant funding identifier for newly registered content, and perhaps beyond.

I use Funder IDs in my system. How can I switch to ROR?

We're here to help! Take a look at the guidance below and write [email protected] with any questions.

👍

Three quick resources for switching from Funder IDs to ROR IDs

Find both IDs for a single funder

Here are two ways to find both the Funder ID and the ROR ID for a single funder.

  1. Go to https://ror.org/search and search for a funder name to determine whether that funder has a ROR record. If the ROR record exists and is mapped to a Funder ID, the ROR record will include both the ROR ID and the Crossref Funder ID.
ROR record for the Alfred P Sloan Foundation

ROR web record for the Alfred P. Sloan Foundation (schema v1)

  1. Use the Funder Mapping Lookup to search for a funder name and find its corresponding Funder ID and ROR ID:
Alfred P. Sloan Foundation with its Funder ID and its ROR ID

Get a CSV file of all Funder ID to ROR ID mappings

🚧

ROR IDs and Funder IDs are not always mapped on a one-to-one basis

A single ROR ID can often be mapped to multiple Funder IDs. When a ROR ID has multiple corresponding Funder IDs, the preferred Funder ID is stored in the field external_ids.FundRef.preferred in v1 of the ROR metadata schema. Be sure to check the status of the mapped ROR record to ensure that it has a status of "active."

Here are two ways to get a CSV file of all Funder ID to ROR ID mappings.

  1. Get the latest copy of the ROR Data dump from Zenodo at https://zenodo.org/doi/10.5281/zenodo.6347574 and download and unzip the .zip file. The provided CSV will show mappings between ROR IDs and, where available, one or more Funder IDs in the external_ids.FundRef.all field. Remember that one ROR ID can have multiple corresponding Funder IDs. When this is the case, the preferred match is stored in the field external_ids.FundRef.preferred.
  2. In the ROR / Funder Registry Overlap tool, click the "Download mapped funders as CSV" button on either "Aggregate overlap" page to download a CSV file that maps Funder IDs to ROR IDs.
Download mapped funders as CSV

The resulting CSV file will have two columns: Funder ID and ROR ID. Additional metadata is not included. Remember that one ROR ID can have multiple corresponding Funder IDs.

Note that the ROR / Funder Registry Overlap tool is manually updated periodically with both new ROR records and new Open Funder Registry records. Be sure to check the last updated date on the left-hand side of the screen to see which versions of the registries have been loaded.

Last updated date and registry versions

Get a CSV file of Funder ID to ROR ID mappings by Crossref member

When Crossref members deposit DOI metadata for a journal article or other research output, they can include Funder IDs to identify the sources of funding for that research. For instance, the Royal Society of Chemistry (RSC) is the publisher of an article that acknowledges three funding sources, and each funder is identified by name and by Funder ID. This single article therefore has three "funding assertions":

article metadata including funder ids

A single funder such as the Japan Society for the Promotion of Science may be referenced in many funding assertions, but that funder has a single Funder ID (501100001691 or 10.13039/501100001691 or https://doi.org/10.13039/501100001691 ) and a single corresponding ROR ID ( https://ror.org/00hhkn466 ).

You can use the ROR / Funder Registry Overlap tool to look up a Crossref member, see how many funding assertions they have made in Crossref DOI records, and download CSV files that map the Funder IDs the member has used to ROR IDs.

The resulting CSV file will have two columns: Funder ID and ROR ID. Additional metadata is not included. Remember that one ROR ID can have multiple corresponding Funder IDs.

Royal Society of Chemistry funder assertions

Map a custom list of Funder IDs to ROR IDs

Because Funder IDs are included in ROR records in the external_ids field, you can map a custom list of Funder IDs to ROR IDs using the ROR API or ROR data dump. This method will also allow you to retrieve additional ROR metadata. For more information and examples, see our guide Map other organization IDs to ROR IDs.

Build ROR-powered forms

You can build ROR-powered funder lookups into your system so that researchers, editors, funder staff, and other users can easily select a funder by name that is connected to a ROR ID and its associated metadata. See Create ROR-powered forms for guidance.

How can I give feedback on or get support for this transition?

Where can I learn more?

Updated 9 months ago