Skip to main content
v2026.1714 entries · CC-BY 4.0
CASRAI

Editorial · CASRAI · The persistent identifier ecosystem

DOI Versioning: Concept DOIs, Version DOIs and Citing the Right Thing

Research outputs are no longer static. Datasets are corrected and extended, software is released in successive versions, and preprints are revised in response to feedback. This dynamism creates a persistent identifier problem: should a citation point to a specific, frozen version, or to the evolving work as a whole? The DataCite concept DOI and version DOI model, implemented most prominently by Zenodo, answers this by minting a concept DOI that always resolves to the latest version alongside distinct version DOIs for each release. This article examines the DataCite concept and version DOI model, Crossref’s handling of versioned content, how preprint servers manage versions, the isVersionOf and hasVersion relationship types in the DataCite Metadata Schema, software versioning through the Zenodo-GitHub integration, and why citing a specific version matters for reproducibility.

ByCASRAI Editorial Board
Published 1 Jan 1970· 1 minute read

Referenced across the research world

University of Cambridge logoColumbia University logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoCrossref logoUniversity of Cambridge logoColumbia University logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoCrossref logo
  • University of Cambridge logo
  • Columbia University logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo
  • Crossref logo

View CASRAI adoption →