<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1174689114;
mso-list-template-ids:969716560;}
@list l1
{mso-list-id:1340767537;
mso-list-template-ids:485232794;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Hi Rob<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Yes – it is so complex.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">I am doing some work on MT data in Australia, and what I think we are going to move towards is a DOI for each individual station in an MT survey/network, but that is a very confronting
suggestion to some geophysicists so it is softly, softly at the moment. The idea is that when the stations are aggregated into a dataset, this also gets a DOI. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">The UNAVCO people presented this work on DOIs in either the 2018 or 2019 AGU and I tried to get them to publish something on their composite and aggregate DOIs, but I can’t see that
they have done this yet (it’s like trying to get IRIS to publish a referenceable paper on their ‘Dirt-to-Desktop concept – hint, hint).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">This way with something like CRediT we can finally start to acknowledge the people that go out in the field and dig the holes and actually collect the data, and more importantly, recognise
those who funded the data collection initiative. Once you go into the more highly evolved data products, these people are rarely if ever citable in a machine-readable way (if you are lucky it is in free text in the acknowledgements).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Critical to this is Data Versioning and the NASA processing levels – have you see the outputs of the RDA Data Versioning Working Group? This WG produced a
<a href="https://rd-alliance.org/group/data-versioning-wg/outcomes/principles-and-best-practices-data-versioning-all-data-sets-big">
white paper</a> based on <a href="https://rd-alliance.org/group/data-versioning-wg/outcomes/compilation-data-versioning-use-cases-rda-data-versioning-working">
39 use cases</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">It would be great to know if anyone else is working on this apart from UNAVCO and Oceans Network Canada.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Take care<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Lesley<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Robert Casey <rob@iris.washington.edu><br>
<b>Date: </b>Wednesday, 23 December 2020 at 8:03 am<br>
<b>To: </b>Lesley Wyborn <lesley.wyborn@anu.edu.au><br>
<b>Cc: </b>Mark Parsons <parsonsm.work@icloud.com>, Esip-citationguidelines <esip-citationguidelines@lists.esipfed.org><br>
<b>Subject: </b>Re: [Esip-citationguidelines] Esip-citationguidelines Digest, Vol 24, Issue 3<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Thank you Mark and Lesley for your responses. I like where UNAVCO was going with this as well and it's a model that they put into practice that certainly should be a set piece for discussion.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">For IRIS's part, we're currently implementing Network PIDs mainly for the purpose of credit. This covers most aspects of the Campaign Dataset and Continuous Station Dataset identifiers that UNAVCO implements.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In terms of aggregation, IRIS has the notion of Virtual Networks, which are the arbitrary collection of stations for specific periods of time. Some represent major, governance-driven efforts, while others are convenient tags developed
internally to represent a widely accepted collection. However, I do not think there has been a consistent effort to provide DOI representations for these affiliations, though I do think they are important.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What we are not yet prepared for is the capability of providing to the investigator a single DOI for their specific custom data gather. This would indirectly serve the needs of credit, but is really aimed at the need for reproducibility.
To get to this level, IRIS has to track the details of every request and supply versioning on its datasets to reproduce a point in time reproduction of the data as it existed when the piece was written. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">All of this will take considerably more infrastructure, though it looked like Ocean Networks Canada was on the way to supporting versioned reproduction of data in their repository. Between this as UNAVCO's works on producing aggregates,
it seems we're starting to see a convergence toward full reproducibility.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">-Rob<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Dec 22, 2020, at 11:42 AM, Lesley Wyborn <<a href="mailto:lesley.wyborn@anu.edu.au">lesley.wyborn@anu.edu.au</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Hi Rob and Mark</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">This topic has been something that has interested me for a while – that is, in ensuring credit to the person that created the component of the dataset that I am using, particularly for data collected from the same station
but over a long period of time where the PIs may change.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">The best logical organisation I have seen are in these recommendations from UNVACO, which sorts out GPS/GNSS datasets into</span><o:p></o:p></p>
</div>
<p class="MsoListParagraph" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span lang="EN-GB">Campaign;</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span lang="EN-GB">Continuous (which is similar to the RDA dynamic data citation Mark mentions below);</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span lang="EN-GB">Aggregated; and</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span lang="EN-GB">Composite.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">These further details are extracted from<span class="apple-converted-space"> </span><a href="https://www.unavco.org/community/policies_forms/data-policy/data-policy-faq/data-policy-faq.html">https://www.unavco.org/community/policies_forms/data-policy/data-policy-faq/data-policy-faq.html</a><span class="apple-converted-space"> </span> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:Symbol">·</span></b><b><span style="font-size:12.0pt"> How does UNAVCO handle GPS/GNSS dataset DOIs for campaigns vs. continuous/permanent stations vs. networks of stations and<span class="apple-converted-space"> </span><span style="color:black;background:yellow">special
cases where the Principal Investigators have changed over time?</span></span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">For GPS/GNSS datasets (raw and RINEX data), UNAVCO publishes (assigns DOIs) for four different dataset types, all with associated data that have been archived to quality standards described above. The types are GPS/GNSS Campaign Datasets;
GPS/GNSS Continuous Station Datasets; Aggregated Datasets; and Composite Datasets. The first two are considered primary dataset types. The third and fourth types are derived or secondary dataset types because they are composed of two or more datasets of the
primary type.<o:p></o:p></p>
</div>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo2">
<b>GPS/GNSS<span class="apple-converted-space"> </span><a href="https://www.unavco.org/help/glossary/glossary.html#campaign">Campaign</a><span class="apple-converted-space"> </span>Dataset</b><span class="apple-converted-space"> </span>- This will be a dataset
defined between UNAVCO and the Principal Investigators at the time of archiving, and generally will include observations as raw and/or RINEX data files and metadata from GPS/GNSS data collection at a number of recoverable monuments that occurred within a well-defined
time window. Once archiving is complete and the DOI is assigned, there is no intention to add data to the campaign that extends the end time or otherwise modifies the data included in the DOI.<o:p></o:p></li></ol>
<div style="margin-left:35.7pt">
<p class="MsoNormal" style="text-indent:-17.85pt">2.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span><b>GPS/GNSS<span class="apple-converted-space"> </span><a href="https://www.unavco.org/help/glossary/glossary.html#continuous site">Continuous
Station</a><span class="apple-converted-space"> </span>Dataset</b><span class="apple-converted-space"> </span>Observations and metadata from GPS/GNSS raw and/or RINEX data collection at a single recoverable monument. Unlike the campaign dataset type, which
is complete and unchanging through time, the Continuous Station Dataset is open ended (until the station is retired). The DOI will be associated with an increasing dataset through time; because of this aspect of this dataset type it is important when citing
this data to qualify the citation with an access date of the data and the temporal window of data used in the research. See<span class="apple-converted-space"> </span><b><a href="https://www.unavco.org/community/policies_forms/attribution/attribution.html#citation">Citation
Guidance</a></b><span class="apple-converted-space"> </span>for a permanent/continuous station dataset.<o:p></o:p></p>
</div>
<div style="margin-left:35.7pt">
<p class="MsoNormal" style="text-indent:-17.85pt">3.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span><b>Aggregated GPS/GNSS Datasets</b><span class="apple-converted-space"> </span>- These
will often be an associated group of campaign datasets or a network of stations. A campaign example is the Mammoth/Mojave 1994 campaign -<span class="apple-converted-space"> </span><a href="https://doi.org/10.7283/T57H1GGM">https://doi.org/10.7283/T57H1GGM</a>,
which consists of three individual primary datasets: Mammoth, Mojave, and Combined Sites). For permanent/continuous stations, networks or sub-networks of stations may be assigned an aggregated DOI. An example is Plutons GPS Network -<span class="apple-converted-space"> </span><a href="https://doi.org/10.7283/T5V98697">https://doi.org/10.7283/T5V98697</a>.
The collection of stations aggregated does not have to be a network; in this case, the purpose of the aggregated dataset is for collecting a potentially large number of station DOIs for citing in a journal article (ie, in order to avoid citation lists containing
tens or hundreds of dataset references).<o:p></o:p></p>
</div>
<div style="margin-left:35.7pt">
<p class="MsoNormal" style="text-indent:-17.85pt">4.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> <span class="apple-converted-space"> </span></span><b>Composite GPS/GNSS Datasets</b><span class="apple-converted-space"> </span>- A
composite dataset DOI is one that is comprised of two or more subset DOIs that together make up what would normally be considered to be a single dataset. The most common example is a permanent (continuous) GPS/GNSS station where the principal investigator
(author) changed at a particular point in time. The existing network (Nucleus) stations that were adopted by UNAVCO as part of PBO are examples. The entire dataset is one DOI and is comprised of a separate DOI for each time period with a different author or
set of authors. An example is the composite DOI for the station NOMT -<span class="apple-converted-space"> </span><a href="https://doi.org/10.7283/T5B27SN9">https://doi.org/10.7283/T5B27SN9</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Take care</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Lesley</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt">From:<span class="apple-converted-space"> </span></span></b><span style="font-size:12.0pt">Esip-citationguidelines <<a href="mailto:esip-citationguidelines-bounces@lists.esipfed.org">esip-citationguidelines-bounces@lists.esipfed.org</a>>
on behalf of Mark Parsons via Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Reply to:<span class="apple-converted-space"> </span></b>Mark Parsons <<a href="mailto:parsonsm.work@icloud.com">parsonsm.work@icloud.com</a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Wednesday, 23 December 2020 at 4:49 am<br>
<b>To:<span class="apple-converted-space"> </span></b>Robert Casey <<a href="mailto:rob@iris.washington.edu">rob@iris.washington.edu</a>><br>
<b>Cc:<span class="apple-converted-space"> </span></b>Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>Re: [Esip-citationguidelines] Esip-citationguidelines Digest, Vol 24, Issue 3</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Hi Rob,<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Different data centers take different approaches for different time series. For infrequently updated time series, it may be appropriate to assign a new PID with every update or provide periodic “snapshots”. For frequently updated data (daily
or more often), data centers will often assign a PID to the general data stream and only create a new one when there is a new version of the stream. This is discussed more in the ESIP guidelines.<span class="apple-converted-space"> </span><a href="https://doi.org/10.6084/m9.figshare.8441816">https://doi.org/10.6084/m9.figshare.8441816</a>. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">For subsets, the RDA Dynamic Data Citation guidleines (<span style="font-family:"Arial",sans-serif"><a href="https://dx.doi.org/10.15497/RDA00016">https://dx.doi.org/10.15497/RDA00016</a>) </span>recommend that one provide a PID for the
overall collection and then assign a PID to any arbitrary subset as obtained through a query. So a citation of a subset would have two PIDS — one for the collection and one for the subset.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">None of this has much to do with credit, however. For many time series the credit is the same for the collection and the granule or subset, but in some cases different individuals may be responsible for different granules within a collection
and should therefore be credited accordingly. There has been a little work showing how the RDA methodology can be used to do this, but that was not the original intent of the Recommendation. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">What we are finding as we go through this exercise, is that credit is a human concern and often requires human judgement. We discuss this a bit in Parsons, M. A., R. E. Duerr, and M. B. Jones. 2019. “The history and future of data citation
in practice.” Data Science Journal 18 <a href="https://doi.org/10.5334/dsj-2019-052">https://doi.org/10.5334/dsj-2019-052</a> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">cheers,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">-m. <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>