As you may have heard, After 6 years, Digital Science’s GRID will be retiring its public releases in Q4 of 2021 to make way for ROR to develop further.
We’re excited about this transition, and thankful to Digital Science for providing the GRID seed data to launch ROR and for helping to coordinate registry updates. ROR and Digital Science are committed to making the transition as smooth as possible for anyone who may wish to make the switch from GRID to ROR.
We realize that current GRID users may have questions about the technical details of this transition. Some of these details are still taking shape, but we'll update the FAQ list below as we have more information.
ROR data is currently available in Figshare, so you can download existing datasets from the Figshare UI or API, just like with GRID.
In the future, ROR is planning to migrate to Zenodo. The most recent dataset is already available there, and you can use the Zenodo API (which works very similarly to Figshare's API) to download it. For instructions, see downloading the ROR data dump using the Zenodo API.
ROR's JSON data structure is identical to GRID, so you should be able to adapt any code that you used to process GRID data in order to process ROR data relatively easily.
Every ROR ID has a one-to-one match to a GRID ID. In ROR records, you'll find the corresponding GRID ID in
externals_ids.GRID.all. If a given record also contains a non-null value in
externals_ids.GRID.preferred, it is identical to the value in
externals_ids.GRID.all, since ROR and GRID records have a 1 to 1 correlation.
Most GRID records include a ROR ID, which you will find in
externals_ids.ROR.all. Because GRID and ROR have different release cycles, you'll find that new records in the GRID dataset don't yet have ROR IDs. ROR IDs for new GRID records are typically added in the next ROR release after a GRID release. This means that in the most recent GRID release (June 2021), ~1200 organizations do not yet have ROR IDs. We are coordinating with GRID to ensure that all GRID records in the final Q4 2021 GRID release release contain a ROR ID.
If you have entire GRID metadata records in your system, you can find the corresponding ROR ID in
externals_ids.ROR.all. If a given record also contains a non-null value in
externals_ids.ROR.preferred, it is identical to the value in
externals_ids.ROR.all, since ROR and GRID records have a 1 to 1 correlation.
If you only have GRID IDs and not entire metadata records, you can search for the matching ROR ID using the ROR API, data dump, or this CSV file extracted from the April 2021 ROR data dump. For more information and examples, see our guide Map other organization ID types to ROR
ROR is continuing to accept curation requests as usual through its curation request form. There may be a delay in processing some requests as we work to ensure that the GRID and ROR datasets are aligned at the time of the final GRID public release.
GRID is currently preparing the final public release of its dataset and is no longer accepting requests for updates.
Yes! ROR is coordinating with GRID to ensure that the ROR and GRID datasets are aligned at the time of the final GRID release, and that all GRID records in the final release contain a corresponding ROR ID.
No. After the final GRID release, the ROR dataset will diverge from GRID and new records added to ROR will not contain a GRID ID.
Technical details surrounding the future of the GRID website are still being determined by the GRID team. See this thread on the PIDForum ROR Chat Room for more information (and please join the discussion there if you have feedback).
Updated 17 days ago