Why Persistent Identifiers Are the Next Layer on Top of Clean Research Data

Getting your own house in order with a single source of truth for projects, researchers, and outputs is the dream for many research centres. Platforms like turnKeyRM solve the internal problem: no more re-typing the same researcher details into three systems, no more chasing down which spreadsheet is the "real" one. But a research centre doesn't operate in isolation. It reports to funders, partners with universities and industry, and exists inside a global research ecosystem that has its own record of what a researcher or organisation has produced…a record the centre doesn't fully control and, more often than not, doesn't fully see.

The real opportunity Persistent Identifiers (PIDs) open up: is not fixing internal data, but connecting a centre's clean internal picture to the outside world, in both directions. This is why Foveal is using the Australian National PID Strategy and Roadmap lead by the ARDC, as its guide to implement PIDs within turnKeyRM.

A PID is a permanent, unique reference to an entity: a researcher, an organisation, a publication, a dataset, or a research project itself, that stays stable even as the underlying details change. As such, PIDs are a core infrastructure component of a world-class, global digital information ecosystem.

The most established examples in the research sector are:

• ORCID: a unique identifier for individual researchers, decoupled from name, institution, or career stage
• DOI (Digital Object Identifier): persistent references to publications, datasets, and other outputs
• ROR (Research Organization Registry): identifiers for institutions and research organisations
• RAiD (Research Activity Identifier): an Australian-originated, ISO-standardised identifier for entire research projects or activities, not just their outputs

Each is globally maintained and independently resolvable, which is exactly what makes them useful once a centre's own data is already clean and wants to connect outward.

Getting your own house in order with a single source of truth for projects, researchers, and outputs is the dream for many research centres. Platforms like turnKeyRM solve the internal problem: no more re-typing the same researcher details into three systems, no more chasing down which spreadsheet is the "real" one. But a research centre doesn't operate in isolation. It reports to funders, partners with universities and industry, and exists inside a global research ecosystem that has its own record of what a researcher or organisation has produced…a record the centre doesn't fully control and, more often than not, doesn't fully see.

Consistent, verifiable reporting across every partner and funder. Research centres rarely report to one audience. There's the funder, the university partners, the industry partners, and government reporting regimes layered on top, each with its own format and expectations. When researcher and output records are anchored to PIDs rather than free-text names, the same underlying data can be reshaped to satisfy each of those requirements without re-verifying identity every time. A partner university doesn't have to take the centre's word for who authored what, the ORCID and DOI are independently checkable against the global record. That's what turns multi-stakeholder reporting from a negotiation into a formality: everyone is citing the same identifier, not their own version of the name.

Surfacing outputs the centre never captured itself. Even with excellent internal systems, no reporting cycle catches everything a researcher does. People publish, present, and deposit datasets without always remembering (or being formally obliged) to log it back through the centre. Because ORCID and DOI records are globally maintained and openly queryable, a centre can pull a researcher's or organisation's full public output record and reconcile it against what's actually logged internally. This surfaces genuine outputs: a conference paper, a dataset deposit, a co-authored piece with another funded project, that would otherwise sit outside the centre's reported impact entirely, even though the centre is fully entitled to claim credit for them. For a centre building its impact case to a funder, that gap can be material, and closing it costs nothing beyond making the identifier query part of the routine reporting workflow.

Together, these two effects extend a centre's source of truth beyond its own walls: not just clean, but complete and independently verifiable to everyone downstream.

The research lifecycle spans years, often decades, and PIDs are what let that history remain queryable rather than becoming a forensic exercise:

Researcher mobility. Researchers move institutions, change surnames, or hold joint appointments. An ORCID travels with the person, so a centre's record of their contribution doesn't fragment every time their institutional email changes, and neither does the centre's ability to later find what that researcher published elsewhere, under a different affiliation.

Funder and government alignment. Funders are steadily moving toward PID-based reporting as the expectation rather than the exception. ORCID is now required or strongly encouraged in a growing number of grant applications, and RAiD is gaining traction as the standard for identifying funded activities across their full lifecycle, from proposal through to final reporting. Centres that already report via PIDs are simply ready for this shift rather than retrofitting for it.

Project-level identity, not just output-level. RAiD extends the same logic to the project or activity itself, giving a whole funded program a single identifier that ties together its contributors, organisations, and outputs, resolvable independently of whichever internal system the centre happens to be using at the time.

Implementation doesn't need to be a big-bang project, it layers naturally on top of data a platform like turnKeyRM already holds cleanly:

• Capture ORCID at researcher onboarding, and make it a required field rather than optional metadata
• Capture ROR IDs for organisational onboarding rather than free-text institution names
• Implement RAiD adoption: it's the identifier most directly relevant to research activity and project tracking, the layer that a research management system like turnKeyRM is built around
• Adopt DOIs consistently for all citable outputs, including datasets, not just journal articles

We are currently focused on integrating PIDS in turnKeyRM to extend the “single source of truth” proposition beyond the platform itself. Through a range of relevant open source integrations, we have implemented ORCID and ROR, and are working with the ARDC to set implement RAiD

The centres that treat PIDs as the connective layer between their internal system of record and the external research ecosystem are the ones whose reporting will hold up under scrutiny, and whose impact case is more complete than the one sitting in their own database.