Persistent Identification
Assign stable identifiers to records, versions, datasets, software, and other enduring outputs.
The JR Institute intends to describe, identify, link, index, and preserve scholarly records through accurate metadata, persistent identifiers, researcher identity systems, stable citations, and durable discovery infrastructure.
This page presents a planned public standard. Final identifier providers, metadata schemas, indexing agreements, authority files, deduplication procedures, and correction workflows should be established before repository launch.
Titles change, websites move, authors share names, institutions reorganize, and files are revised over time.
The Institute should use persistent identifiers and structured metadata to keep the scholarly record connected despite those changes.
Assign stable identifiers to records, versions, datasets, software, and other enduring outputs.
Connect authors to verified identity systems while avoiding forced disclosure beyond legitimate need.
Describe titles, authors, subjects, dates, versions, funders, rights, and related objects consistently.
Use standards that support exchange with repositories, libraries, indexes, funders, and citation systems.
Update metadata without concealing prior versions, corrections, withdrawals, or retractions.
Maintain identifier landing pages, redirects, and preservation plans when systems or domains change.
This policy is intended to apply to preprints, publications, datasets, software, models, technical reports, institutional records, authors, organizations, projects, grants, versions, corrections, and related scholarly objects.
Eligible records should receive a stable identifier appropriate to the object type, repository, preservation model, and discovery ecosystem.
Identifier assignment should occur only after required metadata and landing-page elements are complete enough to support durable citation.
Authors and contributors should be encouraged to connect records with persistent researcher identifiers and verified institutional affiliations.
Names should preserve diacritics, preferred forms, historical changes, and distinctions between people with similar names.
A researcher identifier helps disambiguate identity, but it should not replace the author’s chosen public name or become a condition for unnecessary personal-data collection.
Repository records should include complete and structured information sufficient for discovery, citation, rights review, preservation, and relationship mapping.
Metadata should distinguish submitted, accepted, revised, corrected, withdrawn, retracted, and formally published versions.
Relationships should identify which record updates, supplements, cites, is derived from, replaces, or is replaced by another record.
Records should provide a recommended citation and support export in commonly used citation formats.
Reference metadata should preserve identifiers, authors, titles, dates, publication venues, versions, and links to corrections or retractions where available.
The repository should support standards-based discovery by libraries, search engines, scholarly indexes, funders, aggregators, and preservation networks.
Indexing relationships should not be presented as endorsement, peer review, or certification unless that status is separately established.
The Institute should review metadata for completeness, consistency, duplicate records, invalid identifiers, incorrect affiliations, and broken relationships.
Authority control may be used for names, organizations, subjects, funders, grants, and geographic entities while preserving appropriate local terminology.
Persistent identifiers should resolve to stable landing pages rather than directly to a file that may later change.
When repositories, domains, platforms, or organizational structures change, redirects and identifier resolution should be maintained without breaking citations.
Metadata errors should be corrected promptly, with visible notices when the change materially affects authorship, title, status, rights, version, findings, or citation.
Withdrawn and retracted records should retain their identifiers and landing pages unless an exceptional legal, privacy, safety, or security reason requires another approach.
Framework date: July 2026
Inquiries may concern DOIs, researcher identifiers, affiliations, duplicate records, metadata corrections, repository indexing, redirects, citations, withdrawals, or retractions.
Identify the record, author, identifier, metadata field, requested correction, and available supporting information.
Contact the Institute