90 likes | 191 Vues
Changing Implementation of NSF Data Policy. Dr. Jennifer M. Schopf, NSF OD/OIA/EPSCoR On behalf of the NSF Data Working Group March 17, 2011 CASC Spring Meeting. Long Standing NSF Data Policy is NOT changing.
E N D
Changing Implementation of NSF Data Policy Dr. Jennifer M. Schopf, NSF OD/OIA/EPSCoR On behalf of the NSF Data Working Group March 17, 2011 CASC Spring Meeting
Long Standing NSF Data Policy is NOT changing “Investigators are expected to share with other researchers, at no more than incremental cost and within a reasonable time, the primary data, samples, physical collections and other supporting materials created or gathered in the course of work under NSF grants. Grantees are expected to encourage and facilitate such sharing.” (p VI-8, Award & Administration Guide, NSF 10-1)
New Implementation:Data Management Plans NSF is changing the implementation of its long-standing policy on data sharing • Changes designed to address needs for modern data-driven science. • Avoids a one-size-fits-all approach to data sharing due to differences between disciplines. • First step in a more comprehensive approach to data. • Revision to PAPPG • DCL and FAQ
Changes to PAPPG After Jan 18, 2011, all proposals must have a data management plan (supplemental doc, 2 pages max) • Describe how the PI will conform to data policy associated with the competition to which the proposal is submitted. If none exists, to NSF’s generic policy. • Plan will be part of the merit review considered as Intellectual Merit or Broader Impacts or both, as appropriate. • Plan may simply say “No plan is needed”, but this needs a justification. Statement will be subject to peer & PO review/consideration. • Update to PAPPG: Oct 1, 2010
Guidelines will beCommunity Driven • Avoid a one-size-fits-all approach • Different disciplines encourage the approaches to data-sharing as acceptable within those discipline cultures • Data management plans will be subject to peer review, community standards • Flexibility at the directorate and division levels • Tailor implementation as appropriate • Request additional funding to implement their data management plan
DMP may include: • Types of data, samples, physical collections, software, curriculum materials, and other materials to be produced in the course of the project; • Standards to be used for data and metadata format and content (document where existing standards are absent or deemed inadequate, along with any proposed solutions or remedies); • Policies for access and sharing including provisions for appropriate protection of privacy, confidentiality, security, intellectual property, or other rights or requirements; • Policies and provisions for re-use, re-distribution, and the production of derivatives; and • Plans for archiving data, samples, and other research products, and for preservation of access to them.
Directorate, Office, Program Specific Requirements • If guidance specific to the program is not available, then the requirements in GPG apply • Individual solicitations may have additional requirements as well http://www.nsf.gov/bfa/dias/policy/dmp.jsp
Expectations • This will grow and change over time • Think about how Broader Impacts was introduced as a review criteria • Peer review will in part determine next steps • Working group will be looking at outcomes of initial panels • NSB Expert Panel in Data Policies meeting http://www.casc.org/meetings/11mar/ • Suggestions welcome
More Information • Jennifer Schopf – OIA/EPSCoR • jschopf@nsf.gov • Jean I. Feldman • Head, Policy Office • x4573, jfeldman@nsf.gov • NSF DMP Web Page http://www.nsf.gov/bfa/dias/policy/dmp.jsp • FAQ’s http://www.nsf.gov/bfa/dias/policy/dmpfaqs.jsp