<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
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="">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="">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="">Esip-preserve@lists.esipfed.org</a><br class="">
https://lists.esipfed.org/mailman/listinfo/%<br class="">
(_internal_name)s<br class="">
<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>