[Esip-preserve] Assigning DOIs to data set versions?

Matthew Mayernik mayernik at ucar.edu
Tue May 26 12:32:30 EDT 2020

Hi all,
I have a question about how you all are dealing with version tracking and
DOIs. I am familiar with the ESIP data citation recommendation that talks
about "major" vs "minor" versions, but I am curious about how this is
actually being implemented.

Does your repository assign DOIs for each denoted version, e.g. version 1,
version 2, etc? Do you assign DOIs for incremental version changes, e.g.
version 1.2 or version 2.3? What constitutes a version change in these
cases? Does anybody assign DOIs to any change at all regardless of how
large (e.g. a wording update in metadata)? Does anybody not assign new DOIs
regardless of any versioning or dataset changes?

I'm asking because we are bringing in a fairly complex group of datasets
into one of our NCAR repositories, and tracking versions is not at all
straightforward. Since we intend to assign DOIs to the data, we're working
through the above scenarios with no clear optimal outcome yet.

Any input on how you are actually implementing the ESIP recommendations (or
others) on this would be much appreciated,


Matthew Mayernik, Ph.D.
NCAR Library
National Center for Atmospheric Research (NCAR)
University Corporation for Atmospheric Research (UCAR)
Boulder, CO
mayernik at ucar.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-preserve/attachments/20200526/ec1e808b/attachment.htm>

More information about the Esip-preserve mailing list