<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>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.</p>
<p>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.</p>
<p>Kerstin<br>
</p>
<div class="moz-cite-prefix">On 5/26/20 13:06, Parsons, Mark via
Esip-preserve wrote:<br>
</div>
<blockquote type="cite"
cite="mid:FBD5B638-B7E0-4535-A7A5-BDA757AB6836@rpi.edu">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi Matt,
<div class=""><br class="">
</div>
<div class="">When I was at NSIDC, we assigned major versions to
things that “might change the science”. A very crude rule of
thumb, but helpful.</div>
<div class="">The Arctic Data Center at NCEAS, on the other hand,
assigns a new DOI for any little change to the data
or metadata. </div>
<div class="">Much depends on the nature of the data: how dynamic
it is, what expected use patterns are… </div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">cheers,</div>
<div class=""><br class="">
</div>
<div class="">-m. </div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 26 May 2020, at 10:32, Matthew Mayernik via
Esip-preserve <<a
href="mailto:esip-preserve@lists.esipfed.org" class=""
moz-do-not-send="true">esip-preserve@lists.esipfed.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">Hi all,</div>
<div class="">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.
<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">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?</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Any input on how you are actually
implementing the ESIP recommendations (or others) on
this would be much appreciated,</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Matt</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Matthew Mayernik, Ph.D.</div>
<div class="">NCAR Library</div>
<div class="">National Center for Atmospheric Research
(NCAR)</div>
<div class="">University Corporation for Atmospheric
Research (UCAR)</div>
<div class="">Boulder, CO</div>
<div class=""><a href="mailto:mayernik@ucar.edu"
class="" moz-do-not-send="true">mayernik@ucar.edu</a><br
class="">
</div>
</div>
_______________________________________________<br
class="">
Esip-preserve mailing list<br class="">
<a href="mailto:Esip-preserve@lists.esipfed.org" class=""
moz-do-not-send="true">Esip-preserve@lists.esipfed.org</a><br
class="">
<a class="moz-txt-link-freetext" href="https://lists.esipfed.org/mailman/listinfo/%">https://lists.esipfed.org/mailman/listinfo/%</a><br class="">
(_internal_name)s<br class="">
<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Esip-preserve mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Esip-preserve@lists.esipfed.org">Esip-preserve@lists.esipfed.org</a>
<a class="moz-txt-link-freetext" href="https://lists.esipfed.org/mailman/listinfo/%">https://lists.esipfed.org/mailman/listinfo/%</a>
(_internal_name)s
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
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</pre>
</body>
</html>