John Lewis, Data Operations Manager at Cambridge University Press, tells us why and how Cambridge uses ROR in this latest installment of our short case study series.
John Lewis, Data Operations Manager at Cambridge University Press, tells us why and how Cambridge uses ROR in this latest installment of our short case study series.
Have you ever wondered exactly what happens once you request a new ROR record or suggest a change to an existing ROR record? In this blog post, we take you through all the steps involved in ROR's open, community-driven process for making sure that the information in the ROR registry is complete and accurate.
We are thrilled to introduce the newest member of the ROR pride: Joseph Rhoads joined the ROR team in September as our new Technical Lead.
In this interview with HighWire Press's Tony Alves, we learn that thanks to customer requests and a PID-aware development process, the publishing platform DigiCore Pro uses ROR in form lookups and automatic extraction processes for author affiliations, funder identification, peer reviewer affiliations, user disambiguation, and research integrity.
Exciting news: Symplectic, a global leader in research information management systems, has integrated ROR into its flagship platform, Symplectic Elements.
Version 2 of the ROR API will become the query default in July 2025, and version 1 of the ROR API and dataset will be deprecated entirely in December 2025.
Peyton Tvrdy of the US National Transportation Library tells us why and how her team did such exemplary work in producing metadata for Rosa P, a national digital repository for open transportation research.
In this dual case study, we learn why the Howard Hughes Medical Institute (HHMI) relies on OA.Report and why OA.Report relies on ROR to help HHMI track compliance with its open access policy. “Even back then [in 2019], the best option was to lean on a big, community-owned solution. And it’s been great to see ROR effectively become the standard, the clear way forward for identifying organizations.” “We think ROR is terrific.
Crossref members can now use ROR IDs to identify funders in any place where they currently use Funder IDs in their metadata.
Highlights of the 2025 ROR annual meeting sessions, including the Community Update, the panel on National PID Policies and Practices, and the session on Successes and Opportunities for ROR in the Asia-Pacific Region.
OpenAlex has added a new metadata matching strategy co-developed by ROR and Crossref to its affiliation matching processes: ROR is also investigating the prospect of incorporating this new matching strategy into the ROR API in 2025. If you’ve been reading our recent series of blog posts about metadata matching, you know that automatic metadata matching at scale is a topic dear to our hearts.