We're looking for your feedback on a draft proposal for managing ROR API client identification with 'mailto' parameters or API keys, and comments are open through October 4th, 2024.

The third blog post about metadata matching by ROR’s Adam Buttrick and Crossref’s Dominika Tkaczyk discusses a few common myths about metadata matching that are often encountered when interacting with users, developers, integrators, and other stakeholders. Read all posts in the series on metadata matching.

Optica Publishing Group was one of the earliest publishers to send ROR IDs to Crossref in DOI metadata. In this interview, we speak with them to learn more about their rigorous processes for cleaning organization names.

Several widely used scholarly systems are using ROR IDs to identify and disambiguate funders. In this post, we’ll give you a glimpse of how and why these systems use ROR IDs for funder identifiers.

Crossref, with the help of CWTS Leiden, has just released an exciting update to their participation report, adding metrics for both affiliations in general and ROR IDs in particular. Now Crossref members can easily see how well they are doing in providing open affiliation metadata.

The American Physical Society (APS) has become the largest society publisher to adopt Research Organization Registry Identifiers. Institutional metadata in the Physical Review journals are now easier to find, track, and reference — a move that strengthens open science and research transparency.

We're looking for your feedback on a draft proposal for criteria to include additional external identifiers in ROR records. Comments are open through August 16th. ROR records already include mappings to Crossref Funder IDs, Wikidata, ISNI, and GRID. What additional external IDs do you feel should be added? What criteria do you think other identifiers should meet in order to be added to ROR?

The second blog post about metadata matching by ROR's Adam Buttrick and Crossref's Dominika Tkaczyk describes some basic matching-related terminology and the components of a matching process, then poses some typical product questions to consider when developing or integrating matching solutions.

ROR is fortunate to have a small but mighty team that strives every day to make ROR as good as it can be and to support the diverse needs of our global community. Ever since ROR was established, we’ve continually adjusted our resourcing and staffing to keep up with ROR’s needs and to align ROR activities with the needs and priorities of ROR’s operating organizations.

ROR Curation Lead Adam Buttrick has been working with Crossref Head of Strategic Initiatives Dominika Tkaczyk to explore improvements in automatic metadata matching strategies that can result in better metadata for everyone. Read more about this important work here and in other posts in the matching series.

Today, we are delighted to announce the launch of version 2 of the ROR schema and API! This new version of our schema and API will serve as a rock-solid foundation for everything ROR users want to accomplish now and in the future.