ROR (Research Organization Registry) held its 2026 Annual Community Meeting across three online sessions in February 2026, and published a highlights recap in March. Two figures stand out for research-information teams tracking institutional identifiers: a sharp rise in East Asian coverage among new organization records, and a 2026 technical roadmap that makes ROR’s newer “single search” matching approach the default way systems resolve institution names to ROR IDs.
East Asia drove a large share of 2025’s record growth
ROR added more than 8,000 new organization records in 2025. Per ROR’s own recap, nearly 20% of those new records represent organizations located in East Asia — a concentration the registry’s team called out specifically as notable regional growth. This matters for anyone building or maintaining an ROR ID lookup against affiliation strings in publication, grant, or CRIS metadata: a large block of institutions that previously had no stable, open, machine-resolvable identifier gained one in a single year, which changes the completeness calculus for affiliation-disambiguation pipelines that draw on ROR as a reference set.
The growth wasn’t limited to net-new records. ROR’s curators processed more than 12,200 user-submitted curation requests in 2025, adding over 8,500 new relationship records (parent/child, related, and successor/predecessor links between organizations) — the kind of maintenance work that keeps a registry usable as institutions merge, split, or rebrand, and that a pure count of new IDs doesn’t capture on its own.
Single search becomes the default affiliation-matching strategy in 2026
The more consequential change for integrators is technical, not numerical. ROR’s team launched a new “single search” name-to-ROR-ID matching strategy in 2025, and one of the stated 2026 technical goals is to make single search the default affiliation-matching approach. This is a narrower, more accurately scoped change than “overhauling” affiliation matching outright: it is a change to which matching strategy ROR’s own tools default to when resolving a free-text institution name (as commonly appears in author affiliation strings) to a ROR ID, not a redesign of the ROR ID schema, the registry’s data model, or the record structure itself.
For systems that call ROR’s affiliation-matching service — CRIS platforms, publisher submission systems, repository ingest pipelines — the practical implication is that match results returned by ROR’s default endpoint in 2026 may differ from results returned under the matching strategy it replaces, even for affiliation strings the system has queried before. Teams with pipelines that cache matched ROR IDs, or that have tuned confidence thresholds against the outgoing default, should plan to re-validate a sample of previously matched affiliations once single search becomes the default, rather than assuming continuity of results across the change.
Adoption and integration signals from the same recap
The March recap also noted several adjacent adoption signals from 2025: Crossref added ROR IDs as a funder identifier option, and the count of Crossref records carrying a ROR ID more than tripled over the year. ROR support was also added or extended across several systems named in the recap, including Symplectic, RAID, DOCID, RDA, and OJS 3.5, alongside continued national/international funder adoption — the recap specifically named Australia’s ARC as incorporating ROR into its systems and funding acknowledgements. Separately, the deadline for ROR API users to register a client ID was extended to Q3 2026, giving integrators more runway before that requirement takes effect. CASRAI covered the related sunset of ROR’s version-1 API and schema in a separate 2025 piece; the client ID timeline is a distinct, ongoing item from that migration.
A separate March 2026 post: ROR’s POSI recommitment
It’s worth being precise about a second, unrelated ROR announcement published the same month that is sometimes conflated with the annual meeting recap. On March 27, 2026, ROR published “Strengthening ROR’s Commitment to the Principles of Open Scholarly Infrastructure”, marking ROR’s seventh anniversary as an operating registry. That post is a standalone reflection on ROR’s alignment with POSI (the Principles of Open Scholarly Infrastructure, covering governance/accountability, sustainability/resourcing, and protection of community interests such as insurance), following on from ROR’s original public POSI self-assessment in December 2020. It is not part of the Annual Community Meeting highlights post, was published roughly three weeks later, and addresses governance commitments rather than growth statistics or matching technology. Coverage or internal notes that merge the two into a single “meeting announcement” are conflating two distinct ROR communications.
What this means for CRIS and identifier teams
Taken together, the two real threads from ROR’s March 2026 communications are: (1) a measurable, regionally concentrated jump in registry coverage, most notably in East Asia, that changes what “complete” affiliation coverage looks like for pipelines built on ROR; and (2) a scoped, technical default-strategy change (single search) to how free-text affiliations get matched to ROR IDs, arriving alongside a separate client-ID registration deadline. Institutions and system integrators relying on ROR for affiliation disambiguation should track the single-search default change specifically — not as a data-model overhaul, but as a matching-behavior change worth re-testing against — while treating ROR’s POSI recommitment as a separate governance story about the registry’s own long-term sustainability.
