<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
LTER IMs,
<div class="moz-forward-container">
<p>Corinna brought to my attention the more strongly worded text
in the 2020 DEB RFP for data citations.<br>
I took advantage of this to try to reel in more datasets for HBR
as well as NSF non-LTER datasets direct to EDI. This was
motivated by the fact that we have field and lab techs who have
been transitioned to telework, and my hope is that this might
spark some ideas for new (or old) LTER or non-LTER datasets that
they could begin to tidy up and document with their PIs for
submission. <br>
</p>
<p>Corinna asked me to share the email that I sent (below) - and
has offered EDI assistance if it pulls in NSF non-LTER data.
Maybe something similar would work at your site.....<br>
</p>
<div class="moz-forward-container">I hope everyone is well, and
finding that IM work goes on almost as usual in these
challenging times.</div>
<div class="moz-forward-container">-Mary<br>
</div>
<div class="moz-forward-container"><br>
</div>
<div class="moz-forward-container"><br>
</div>
<div class="moz-forward-container">=========================================================<br>
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<p>Hubbard Brook COS,</p>
<p>Although earlier NSF DEB RFPs have requested data citations
in Prior Support, the 2020 version has strengthened this
statement. I'm including the relevant text from the RFP, and
an offer of assistance to help you meet this requirement.<br>
</p>
<p>From <a class="moz-txt-link-freetext"
href="https://www.nsf.gov/pubs/2020/nsf20502/nsf20502.htm"
moz-do-not-send="true">https://www.nsf.gov/pubs/2020/nsf20502/nsf20502.htm</a>:<strong><br>
</strong></p>
<blockquote>
<p><strong>"Results from Prior NSF Support.</strong> In
addition to the reporting requirement format described by
the PAPPG (see Results from Prior NSF Support,
II.C.2.d.iii), the Results from Prior NSF Support section<font
color="ff0000"> must include evidence of deposition of
samples, data and/or data products in recognized,
accessible, community-accepted repositories by listing
such repositories and, if practical, metadata.</font> <font
color="ff0000">All publications, data, data products,
programs and/or scripts that are specifically mentioned in
the Results from Prior NSF Support section must be
referenced in the References Cited section and must
provide unique, resolvable and persistent identifiers
(such as Digital Object Identifiers [DOIs]; Uniform
Resource Locators (URLs), or similar). "<br>
</font></p>
</blockquote>
<p><font color="ff0000"><font color="000000">As you already
know, the data that we curate for Hubbard Brook will meet
these requirements, so if data that you reference in
'prior support' is already in the EDI repository, that's
great! <br>
</font></font></p>
<p><font color="ff0000"><font color="000000">There are likely
two additional types of data that may need attention. The
first is Hubbard Brook data that are not already in the
EDI repository that you refer to in 'prior support'. It's
my job to work with you to get those data into EDI and
cite-able as instructed above. Most of you are familiar
with this routine, and I'm here to help if you have new
(or old) HB data, or updates to existing datasets.</font></font></p>
<p><font color="ff0000"><font color="000000">The second class of
data would be NSF data you have collected outside of the
scope of Hubbard Brook. If you have field and lab staff
who have transitioned to telework, this might be a great
project to have them work on - preparing your
non-HubbardBrook data for the EDI repository. I would be
happy to meet over zoom with you and your staff to review
potential datasets, and to provide guidance on preparing
data tables and filling out metadata templates. My initial
idea was to help you implement the entire data-to-EDI
workflow, but when I mentioned this to EDI folks, they
jumped right in with an offer to share in this effort -
this is an offer you should not turn down! EDI folks can
work with you on NSF non-LTER data in the same manner that
you work with me on HBR data. I'm proposing here, that I
would provide a little intermediate guidance to get you on
the EDI path with these datasets. <br>
</font></font></p>
<p><font color="ff0000"><font color="000000">Please drop me an
email to let me know how I can best help you to meet this
more strongly worded NSF data requirement!<br>
</font></font></p>
<p><font color="ff0000"><font color="000000">Regards,<br>
-Mary</font></font></p>
<p><font color="ff0000"><font color="000000">Mary Martin<br>
Hubbard Brook Information Manager<br>
Earth Systems Research Center <br>
Morse Hall, Univ of NH <br>
Durham, NH 03824 <br>
Voice: 603 862 4508 <br>
Email: <a class="moz-txt-link-abbreviated"
href="mailto:mary.martin@unh.edu" moz-do-not-send="true">mary.martin@unh.edu</a><br>
<br>
</font></font></p>
<p><font color="ff0000"><font color="000000"><br>
</font></font></p>
<p><font color="ff0000"><font color="000000"><br>
</font></font></p>
<p><font color="ff0000"><font color="000000"><br>
</font></font></p>
</div>
</div>
</body>
</html>