[LTER-im] Updated 2020 NSF DEB Prior Support section - Data repositories

[Mary Martin]

LTER IMs,

Corinna brought to my attention the more strongly worded text in the 
2020 DEB RFP for data citations.
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.

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.....

I hope everyone is well, and finding that IM work goes on almost as 
usual in these challenging times.
-Mary


=========================================================

Hubbard Brook COS,

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.

 From https://www.nsf.gov/pubs/2020/nsf20502/nsf20502.htm:*
*

    *"Results from Prior NSF Support.* 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
    sectionmust 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. 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). "

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!

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.

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.

Please drop me an email to let me know how I can best help you to meet 
this more strongly worded NSF data requirement!

Regards,
-Mary

Mary Martin
Hubbard Brook Information Manager
Earth Systems Research Center
Morse Hall, Univ of NH
Durham, NH 03824
Voice:  603 862 4508
Email: mary.martin at unh.edu




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lternet.edu/pipermail/im/attachments/20200402/60cdf2c5/attachment.html>