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

Kerstin Lehnert lehnert at ldeo.columbia.edu
Tue May 26 13:23:52 EDT 2020

At the EarthChem Library, we generate a new version & DOI only if the 
actual data in the data file have changed as such change will have an 
impact on the outcomes of the data use i.e. reproducibility of the 
scientific interpretation. If changes are made to metadata, especially 
if it's just a correction of a method or sample location, we do record 
that change in an annotation, but do not issue a new version.

If a correction of the data (fixing typos) is made shortly after 
publication and before a published dataset has ever been downloaded, we 
usually allow the corrected version to replace the old one without 
issuing a new DOI.


On 5/26/20 13:06, Parsons, Mark via Esip-preserve wrote:
> Hi Matt,
> When I was at NSIDC, we assigned major versions to things that “might 
> change the science”. A very crude rule of thumb, but helpful.
> The Arctic Data Center at NCEAS, on the other hand, assigns a new DOI 
> for any little change to the data or metadata.
> Much depends on the nature of the data: how dynamic it is, what 
> expected use patterns are…
> Of course, the RDA dynamic data citation rec. addresses the issue to a 
> large degree. This might be a good time to try and implement. I know 
> Reyna Jenkins at Ocean Networks Canada is grappling with this with 
> similar types of data.
> cheers,
> -m.
>> On 26 May 2020, at 10:32, Matthew Mayernik via Esip-preserve 
>> <esip-preserve at lists.esipfed.org 
>> <mailto:esip-preserve at lists.esipfed.org>> wrote:
>> 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,
>> Best,
>> Matt
>> Matthew Mayernik, Ph.D.
>> NCAR Library
>> National Center for Atmospheric Research (NCAR)
>> University Corporation for Atmospheric Research (UCAR)
>> Boulder, CO
>> mayernik at ucar.edu <mailto:mayernik at ucar.edu>
>> _______________________________________________
>> Esip-preserve mailing list
>> Esip-preserve at lists.esipfed.org <mailto:Esip-preserve at lists.esipfed.org>
>> https://lists.esipfed.org/mailman/listinfo/%
>> (_internal_name)s
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> https://lists.esipfed.org/mailman/listinfo/%
> (_internal_name)s
Dr. Kerstin A. Lehnert
Doherty Senior Research Scientist
Director, Geoinformatics Research Group
Director, Interdisciplinary Earth Data Alliance
Lamont-Doherty Earth Observatory of Columbia University
61 Route 9W, Palisades, NY, 10964, USA
+1 (845) 365-8506

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-preserve/attachments/20200526/041203e1/attachment-0001.htm>

More information about the Esip-preserve mailing list