ROR, ISNI, Ringgold, GRID: How They Map

Research administrators routinely hit the same wall: a grant portal wants a ROR ID, a publisher submission system stores the institution as a Ringgold number, a legacy CRIS record still carries a GRID code, and a funder’s compliance system resolves affiliations through ISNI. These four institutional identifiers were built by different organizations, for different purposes, at different times — and none of them is a universal key to the other three. This guide lays out, from primary documentation, exactly how ROR, ISNI, Ringgold, and GRID actually cross-reference each other: which mappings are formally built into a schema, which require an intermediary lookup, and which have no direct path at all.

This is a companion to two related CASRAI guides: Identifier Crosswalk: Connecting DOI, ORCID, ROR, and Institutional IDs in Practice covers how ROR interoperates with DOI and ORCID in citation and deposit metadata, and ROR IDs Explained covers registering and maintaining a ROR record. Neither covers the institutional-identifier-to-institutional-identifier mapping mechanics this guide focuses on.

The four identifiers at a glance

Identifier	Governing body	Status	Format	Access model
ROR ID	ROR Community (Crossref, DataCite, California Digital Library)	Active, launched January 2019	`https://ror.org/0abcdefgh` (9-character alphanumeric)	Open, free, CC0 data
ISNI	ISNI International Agency (ISNI-IA), under ISO 27729	Active	16-digit number in four groups of four (e.g. `0000 0001 2345 6789`)	Open lookup; registration through accredited Registration Agencies
Ringgold ID	Ringgold, owned and administered by Copyright Clearance Center (CCC)	Active, commercial	Numeric ID (no fixed digit count)	Proprietary — the Identify database is a licensed product
GRID	Originally Digital Science; donated to ROR in 2019	Frozen — no longer actively maintained as an independent registry	`grid.XXXXXX.XX`	Historical data preserved inside ROR records

How ROR formally cross-references the other three

ROR’s own data structure documentation defines an external_ids field on every ROR record, and it formally supports exactly four external identifier types: GRID, ISNI, Wikidata, and the Crossref Open Funder Registry (the identifier scheme formerly branded FundRef). Each type carries an array of all known values of that kind for the organization, plus (where applicable) a single preferred value. Ringgold is not one of the four — it is not part of ROR’s formal external_ids schema at all, which is the single most important fact to internalize before building any mapping workflow between these systems.

Two consequences follow directly from that schema:

GRID and ISNI lookups against ROR are direct and reliable, when the ROR record includes them. You can query the ROR REST API for a record containing a specific GRID or ISNI value inside external_ids, or download the full ROR data dump and match offline — ROR’s own mapping documentation describes both approaches. Not every ROR record carries every ID type, though: coverage is partial, particularly for smaller or newer organizations that predate GRID or were never independently ISNI-registered.
Ringgold lookups against ROR require an intermediary, because there is no direct field to match on. ROR’s own mapping guidance is explicit about this and gives two workable paths, covered below.

GRID → ROR: the direct predecessor relationship

GRID is not a peer identifier to ROR so much as its direct ancestor. When ROR launched in January 2019, Digital Science donated the GRID database it had curated for years to seed ROR’s initial dataset, released under a CC0 public-domain dedication. ROR retained GRID identifiers as a permanent field inside external_ids specifically so that the very large body of existing datasets, publications, and legacy CRIS records that cite an organization by its grid.XXXXXX.XX code can still be resolved forward to the correct, actively-maintained ROR record. GRID itself is no longer independently updated as a registry — if an institution’s structure changes today (a merger, a name change, a new campus), that change is made in ROR, not in a standalone GRID system, and only surfaces back through the GRID field if ROR’s curators choose to retain the historical mapping.

Practically, this is the cleanest of the four cross-references: any dataset, system, or record that stores a GRID ID can be matched to its current ROR ID with a single query against external_ids.grid.all, with no intermediary required.

ISNI → ROR and ISNI → Ringgold

ISNI (International Standard Name Identifier, ISO 27729) is the connective tissue between the other three systems, because it is the one identifier both ROR and Ringgold formally recognize. ROR includes ISNI directly in external_ids, matchable the same way as GRID. On the Ringgold side, the relationship goes back to how ISNI itself was extended to cover organizations, not just people: NISO’s Institutional Identifiers (I2) Working Group, whose 2013 recommended practice (ANSI/NISO RP-17-2013) specified applying the ISNI standard to institutions rather than defining a competing identifier scheme, named Ringgold and Bowker as the first ISNI Registration Agencies for institutions. Registration Agencies are the accredited bodies that actually assign ISNI numbers on ISNI-IA’s behalf — so a substantial share of institutional ISNI records in the registry originate from Ringgold’s own institutional database.

That shared lineage is exactly why ROR’s own mapping guidance points to ISNI as the practical bridge for the one identifier it doesn’t recognize directly.

Ringgold → ROR: no formal schema field, two documented workarounds

Because the Ringgold Identify database is a licensed, proprietary product, ROR cannot legally redistribute Ringgold IDs inside its own open records, which is why Ringgold sits outside the external_ids schema entirely. ROR’s own mapping documentation lays out two paths for anyone who needs to connect a Ringgold-identified organization to its ROR record:

Via ISNI, if you have access to Ringgold’s Identify database. Since ISNI numbers appear in both Ringgold records and ROR’s external_ids.isni field, an organization’s ISNI number can be used as the join key between the two systems.
Via Wikidata, if you don’t have Ringgold access. ROR references a community-maintained mapping approach that uses Wikidata as the bridge, since many organizations’ Wikidata entities carry both a Ringgold ID and a ROR ID as properties, alongside GRID and ISNI where available. ROR’s documentation links to a reference script on its GitHub for this approach.

There is no single authoritative crosswalk file that maps Ringgold IDs directly to ROR IDs the way external_ids.grid or external_ids.isni does — any Ringgold-to-ROR mapping a system relies on today is either built through one of the two bridges above, licensed directly from a data provider that has already done that matching, or maintained as a manually curated local table. Treat any claim of a direct, official Ringgold-to-ROR crosswalk with skepticism unless it names its actual mechanism.

None of this makes Ringgold obsolete for research-administration purposes. Ringgold IDs remain widely embedded in scholarly-publishing infrastructure: many journal submission systems (Editorial Manager, ScholarOne, and others) use Ringgold’s institution list for author-affiliation autocomplete, and CCC’s Identify database is licensed by major systems for subscription and entitlement management — PLOS and Frontiers both announced adoption of the CCC Ringgold Identify database as their persistent-identifier solution for institutional affiliation and open-access agreement matching. A research administrator reconciling a publisher invoice, an author-affiliation record, or an institutional repository entry may well need to resolve a Ringgold number even though ROR has become the default identifier for grant and funder-facing systems.

Practical lookup workflows

You have a GRID ID and need the current ROR ID

Query the ROR API or search interface for the GRID value; ROR resolves it against external_ids.grid and returns the current, actively-maintained record. This is the most reliable of the four lookups because GRID data was inherited wholesale into ROR at launch.

You have an ISNI and need the ROR ID (or vice versa)

Query external_ids.isni directly through the ROR API, or use ISNI’s own public search at isni.org to confirm the organization’s ISNI record and cross-check its associated names/variants before matching. This is direct in both directions when the ROR record has an ISNI populated — coverage is good but not universal.

You have a Ringgold ID and need the ROR ID

If you have Ringgold/Identify database access, pull the organization’s ISNI number from that record and match it against external_ids.isni in ROR. If you don’t have Ringgold access, use a Wikidata-based crosswalk (matching on the organization’s Wikidata entity, which frequently carries both identifiers as properties) or fall back to a name-and-location match against the ROR search API, then manually verify. Because there is no single authoritative file, always verify a Ringgold-to-ROR match against a second signal (official institution name, location, or parent/child relationship) rather than trusting a one-to-one automated match blindly, especially for organizations with common names or multiple campuses.

You have a ROR ID and need to find the others

Retrieve the ROR record directly (via the API or ror.org) and read the external_ids block — GRID, ISNI, and Wikidata (and Crossref Funder ID, if the organization is also a funder) will be listed there if known, with no further lookup required. Ringgold will not appear; use the ISNI or Wikidata bridge above if you specifically need it.

Why this matters for research administration specifically

These four identifiers surface constantly, and inconsistently, across a research administrator’s daily systems: funder portals and most current grants-management platforms increasingly require a ROR ID for the applicant institution; many CRIS and repository platforms still carry legacy GRID codes from records created before 2019; publisher-facing submission and licensing systems frequently key on Ringgold; and ISNI, because it also covers individual researchers, occasionally shows up in funder or publisher identity-verification workflows alongside ORCID. Reconciling a single institution’s records across a grant-reporting system, a CRIS, and a publisher relationship can genuinely mean tracking all four identifiers for the same organization, not just one. Building (or buying) a crosswalk table that resolves all four for your institution once, rather than re-deriving the mapping ad hoc every time a system asks for a different identifier, is the practical payoff of understanding how these systems actually connect.

It’s also worth knowing where OCLC’s institutional identifiers fit relative to this stack: as covered in OCLC WorldCat Institutional Identifiers and CRIS Records, OCLC Registry IDs serve library-system interoperability rather than the funder/publisher/CRIS identification role that ROR, ISNI, Ringgold, and GRID cover, and there is no documented, formal crosswalk between the OCLC Registry and this identifier group.

Common pitfalls

Assuming every ROR record has all four external IDs populated. Coverage is partial, especially for smaller organizations, newly-registered ROR records, and organizations outside GRID’s original curated scope. Always check before building an automated pipeline that assumes the field is populated.
Treating Ringgold-to-ROR matching as a solved, direct lookup. It isn’t — it’s a bridged match through ISNI or Wikidata, or a licensed third-party mapping, and any of those can produce false matches for organizations with ambiguous names, multiple campuses, or recent mergers. Verify, don’t assume.
Confusing ISNI-for-organizations with ISNI-for-people. ISNI covers both researchers and institutions in the same numbering scheme; make sure a lookup is matching against the organization’s ISNI record, not a same-named individual’s.
Expecting GRID to reflect current institutional structure. GRID is frozen as a standalone registry; a merger or restructuring since 2019 will be reflected in ROR’s current record, but the GRID field attached to it is historical, not live.

Frequently asked questions

Is there a single file or API that maps all four identifiers to each other directly?

No. ROR’s external_ids schema directly links ROR to GRID, ISNI, Wikidata, and Crossref Funder ID within its own open records — that part is a single authoritative source. Ringgold sits outside that schema entirely because it is proprietary data; any Ringgold-inclusive crosswalk is built through ISNI or Wikidata as an intermediary, or licensed separately.

Why doesn’t ROR just include Ringgold IDs directly?

Because Ringgold’s Identify database is a commercial, licensed product administered by Copyright Clearance Center, not open data ROR can freely redistribute under its CC0 model. ISNI, GRID, Wikidata, and the Crossref Open Funder Registry are all either open or accessible in a way ROR’s data model can incorporate directly; Ringgold is not.

Should our institution still track its Ringgold ID if we already have a ROR ID?

Generally yes, if your institution engages with publishers, licensing agreements, or submission systems that key on Ringgold — it remains embedded in significant parts of scholarly-publishing infrastructure. For funder, grant, and most modern CRIS/repository purposes, ROR has become the default and is the identifier worth prioritizing when only one can be supplied.

Is GRID still being updated?

No. GRID was folded into ROR at ROR’s January 2019 launch and is not maintained as an independent, actively-curated registry. Institutional changes are made in ROR; the GRID identifier attached to a ROR record is retained for backward-compatible lookups, not as a live data source.

How ROR, ISNI, Ringgold, and GRID Cross-Reference Each Other