Skip to content

Persistent Identifier Minting

Identifier-minting procedure — instantiates Open Reuse Publication Infrastructure

Assigns a durable, resolvable identifier — a DOI, handle, accession, or reserved package name — that keeps pointing at the artifact even after it moves, is mirrored, or is superseded.

A raw URL is a location, and locations break. Persistent Identifier Minting is the procedure that manufactures identity that outlives location: it assigns the artifact a durable, resolvable name — a DOI, a handle, an ARK, an accession number, a reserved package name — that routes through an indirection layer whose target can be updated. Its defining move is that the reference and the current whereabouts are decoupled: when hosting changes or a mirror takes over, the identifier is repointed and every citation and dependency that used it keeps working. Where the registry helps a human find the artifact today, the minted identifier guarantees that tomorrow's link, citation, and dependency still resolve — and, because minting binds metadata at the moment of assignment, it also records who made this and where it came from.

Example

An astronomy team finishes a multi-year sky-survey dataset and deposits it in a repository (a service like Zenodo), which mints a DOI through DataCite. Minting isn't just handing out a string: the DOI is registered with mandatory metadata — creator, title, publisher, publication year — and set to resolve to the dataset's current landing page.

Three years later the hosting institution reorganizes its servers and every old direct URL 404s. But the papers that cited the DOI are unaffected: the identifier resolves through DataCite's indirection to the new location. A researcher building a meta-analysis cites the exact DOI, and the provenance metadata tells them who produced the data and when — before they've downloaded a byte. The dataset moved; its identity, and the trail back to its authors, did not.

How it works

What separates minting from "copy the URL" is the machinery of durability and origin behind the string:

  • Indirection over location. The identifier resolves through a registry to the current target, so the pointer survives moves and mirrors.
  • Metadata bound at mint time. Authorship, publisher, date, and relations are recorded when the identifier is created — the provenance travels with the name.
  • Immutability of the identifier. A minted identifier is never reassigned to something else; withdrawn artifacts get a tombstone, not a recycled name.
  • A registration agency standing behind it. The persistence is a maintained commitment (a resolver plus governance), not a hope about a domain name.

Tuning parameters

  • Identifier scheme — DOI vs. handle vs. ARK vs. reserved package name vs. domain accession. Heavier schemes carry governance and metadata mandates and stronger guarantees; lightweight ones are cheaper but promise less.
  • Granularity of minting — one identifier per artifact, per version, or per file. Per-version identifiers make citation exact but multiply the things to resolve and maintain.
  • Metadata richness at mint — minimal required fields vs. rich provenance and relationship links. Richer metadata powers citation and lineage but costs curation effort up front.
  • Resolution and tombstone policy — how promptly targets are updated and how withdrawn or superseded artifacts are represented rather than left dangling.
  • Concept-to-version linkage — whether a stable "all versions" identifier umbrellas the version-specific ones, so citers can point to either the exact release or the evolving work.

When it helps, and when it misleads

Its strength is that it defeats link rot — the steady decay of URLs into dead ends — and in the same act makes the artifact citable and anchored to its origin, even as copies, forks, and mirrors proliferate.[1]

Its failure modes come from mistaking the string for the guarantee. An identifier is only as persistent as the institution and resolver behind it; mint from a fragile or short-lived registrar and you have bought false durability. Minting also says nothing about whether the content at the end is unchanged — that is an integrity-and-signature concern, not an identity one. The classic misuses are minting fresh identifiers for trivial changes (fragmenting the citation record) and minting to look authoritative while letting resolution quietly rot. The discipline is to back the identifier with a committed registration agency, keep resolution current, and pair it with integrity verification and a version scheme.

How it implements the components

Persistent Identifier Minting fills the identity-and-origin slice of the archetype — the components an identifier procedure genuinely produces:

  • persistent_address_and_identifier — its primary output: the durable, resolvable name that downstream references depend on.
  • provenance_and_authorship_record — the metadata bound at mint time (creator, publisher, date, relations) records where the artifact came from and who stands behind it.

It does not make the artifact searchable (access_equity_accommodation — Public Artifact Registry), deliver the bytes (open_access_channel — Package Manager Distribution), or cryptographically verify authenticity (that's Integrity Checksum or Signature — minting records the claimed origin; the signature proves it wasn't altered).

Notes

Persistence is a property of the resolver and the institution, not of the identifier string. A DOI that no one keeps pointing at a live target is no more durable than a bare URL — it just looks durable. Choosing a registrar is therefore choosing a maintenance commitment, and that choice matters more than which identifier syntax you adopt.

References

[1] Link rot (or reference rot) is the well-documented tendency of URLs to stop resolving over time as content moves or hosts disappear. Persistent identifiers exist specifically to interpose a maintained indirection layer between a citation and a location, which is the whole reason scholarly and data-publishing communities mint DOIs and handles rather than citing raw URLs. ↩