"The DMP should describe data formats, media, and dissemination approaches that will be used to make data and metadata available to others. Policies for public access and sharing should be described, including provisions for appropriate protection of privacy, confidentiality, security, intellectual property, or other rights or requirements. Research centers and major partnerships with industry or other user communities must also address how data are to be shared and managed with partners, center members, and other major stakeholders. "
Data Management for NSF SBE Directorate Proposals and Awards, p. 3. http://www.nsf.gov/sbe/SBE_DataMgmtPlanPolicy.pdf
Please note that these DMP excerpts are copyrighted by their respective authors.
“These data will provide a detailed experimental look at the mechanical regulation of mesenchymal stem cell osteogenesis. The data will further delineate the functional role of the cytoskeleton-focal adhesion-extracellular matrix signaling axis in the mechanoresponsive mesenchymal stem cell osteogenesis, as described in the main body of the proposal. As such, they will be of interest to the tissue engineering and regenerative medicine communities.”
This is a thorough description of who would be interested in the data.
“No, or very little, derivative use of the data is expected since the research is aimed at developing machining process models and the data to be gathered is directed toward this end.”
A belief that others won’t be interested in your data is an insufficient reason for declining to share it.
“The PIs will make copies of data available to co-investigators, students, and others by request within 45 days from receipt of the request unless a longer period is necessary for protection of intellectual property.... To facilitate the sharing of data, project data will be made publicly available via a university-controlled repository, Deep Blue.”
If planning to use Deep Blue to archive and disseminate your data you should first become familiar with its policies.
“Access to raw data will be allowed at the discretion of the PI and co-PI.”
This example should contain an explanation of how access will be given.
“Our software is already and will remain publicly available at the Center for Space Environment Modeling website. Scientists and researchers can obtain the software and documentation after filling in a simple form and user agreement and sending back a signed hard copy to us. The registration and user agreement are legal requirements by the University of Michigan, and this procedure is similar to those used by other similar projects.”
This is a good start, but the plan should include more information about the user agreement, preferably with a link to the form.
“Data can be accessed by general public through publications in conferences, journals, etc.”
Most journals are restricted to subscribers, so supplementary material is certainly not available to all. Publication ≠ data sharing.
Explain, in as much detail as possible, how and when your data will be made available to people outside your research group. Keep in mind the potential users of the data as well as any norms for data sharing that exist within their communities. For instance, if you are generating data that is of potential interest to researchers who are heavy users of a disciplinary data repository then it is probably not sufficient to make your data available by email request to the PI. On the other hand, if that is the standard method of data sharing in the relevant user communities then it may be any acceptable solution.
In regard to data sharing, we strongly encourage you to consult with ORSP and the Office of Technology Transfer if you have any special licensing requirements or intellectual property concerns. The Library’s Copyright Office is also available for consultations regarding the licensing of software and research data.