[Esip-preserve] NSF data management & sharing policies

[Bruce Barkstrom]

The policies vary not just because of the agency differences; they also
vary because of the practices regarding data distribution
and quality control.  For example, weather reports are published within a
few hours of data ingest into the forecasting centers.
In the cases I've been involved with in NASA's EOS missions, the rate of
data production for the larger data centers can lie
between 10,000 and probably many more than 100,000 files per day - 24-7.
The science teams on these projects undertake large-scale
validation efforts to check data consistency and uncertainty.  Just
gathering the intercomparison data (checking against in-situ
measurements, for example, as well as seasonal or longitudinal averages)
could take three to six months.  The same scale issues
arise in climate model intercomparisons.  In the case of the investigation
of Clouds and the Earth's Radiant Energy System (CERES),
we did release the data (at whatever level) provided the data user was
willing to sign on to a notice that he or she had read a caveat
about the use of the data and would report back on findings before
attempting to publish them.  Of course these kinds of projects
are different from laboratory experiments in the life sciences, as well as
other scientific disciplines.

Bruce B.

On Thu, Apr 28, 2016 at 12:27 AM, Arctur, David K via Esip-preserve <
esip-preserve at lists.esipfed.org> wrote:

> Folks, I have some q’s related to data management policy requirements &
> oversight, would appreciate your feedback.
>
> Reviewing the policies of the individual NSF Directorates shows variations
> in the policy - for example Geosciences permits for a 2-year hold period *following
> collection* <http://www.nsf.gov/geo/ear/2010EAR_data_policy_9_28_10.pdf> while
> Engineering which permits for 2-year hold following publication
> <http://nsf.gov/eng/general/ENG_DMP_Policy.pdf>. Even within Geosciences
> there is variation (e.g. Division of Ocean Sciences requirement to archive
> data in specific National Data Center).
>
> Some questions that come up for me include:
>
>    - Which aspects of the current data management and sharing policy have
>    been most effective and which aspects does the NSF hope to improve?
>    - How does the NSF monitor researchers' managing and sharing their
>    data consistent with the policies and researchers' proposals?
>    - How much flexibility do PIs of ongoing research projects have in how
>    they satisfy data management and sharing requirements, in relation to what
>    they included in their proposal?
>    - Re: Engineering Directorate - I understand that data that could lead
>    to commercialization is not subject to the publication requirement. Is this
>    defined when a proposal is made? How has this been observed and used in
>    practice?
>
> Thanks for your help and thoughts on this.
>
> Best, dka
> —
> David K Arctur
> Research Scientist & Fellow, University of Texas at Austin
>
>
>
>
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-preserve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-preserve/attachments/20160428/20ebb02c/attachment.html>