The Your grant proposal's data management and sharing plan (DMP) in your grant proposal should DMS plan) will include information on the repository where you will share your datasets. If you do not know which repository meets your project and funder need needs, you can search the R3Data.org repository index to find the apt repository to share your research data. In cases where you do not have a disciplinary or funder/journal mandated repository, the ASU Dataverse Research Data Repository may be an option for sharing your research datasets. Powered by Harvard’s Dataverse platform the repository facilitates the reuse phase of your project and should not be confused with active storage and management. Your Research Advancement team member and Research Data Managers can work with you on the details of your plan.
Before developing your proposal, contact ASU's Office of Research Data Management. You can also use the DMPTool to help draft your proposal which includes , including direct funder guidance and institutional recommendations. The DMPTool has options for indicating repositories, and if appropriate, you can select ASU Dataverse ASU’s Research Data Repository. Learn how to use the DMPTool.
...
| Info |
|---|
Proposal data management and sharing plans are typically 1 to 2 pages and should not be confused with the entire project DMP DMS plan you will refer to and update throughout your project. Proposal DMPs DMS plans are summaries of your plan and not exhaustive explanations. You can add and manage your whole plan in your research or lab notebook. Plans should simple but specific. |
Costs
The ASU Library does not charge for dataset submissions of ASU-affiliated projects. However, if your dataset is larger than a terabyte, you must talk with the ASU Research Data Management Office. While there may not be a direct cost, there is a process to publishing your data, so you will want to ensure you have given us time before any publication deadlines. We would also work with you to determine what portions of the data should be shared (it may not be everything) and ensure the ASU repository is appropriate for your data.
Boilerplate language
There is no one-size-fits-all to your proposalsproposal's DMS plan, and the exact language you use will be specific to your project needs, sharing and use restrictions and other elements. Below is some suggested text that can be adopted and integrated into your plan's sharing and preservation components.
Repository information
Datasets will be released to the public as soon as possible upon completing the data gathering and analysis in Arizona State University's Research Data Repository powered by the Harvard Dataverse platform. The institutional repository allows ASU-affiliated, interdisciplinary researchers to share, store, preserve, cite, explore, and make research data accessible and discoverable. Upon publication, the ASU Library assigns each dataset a Digital Object Identifier (DOI) to provide a persistent and citable reference point registered through Datacite. We will systematically copy the dataset files and their respective structure and provide metadata that describes describing the software coding information so that others may understand and make use of the files. We will also work with ASU research data managers and library research data curators to organize and describe our data so that it is findable, accessible, interoperable, and reusable.
Licensing
We will assign a CC0 - "Public Domain Dedication" license for Datasets to facilitate the reuse of the files, and the platform provides will provide a suggested citation.
See the FAQ on determining the best license for your dataset.
If there is human subject information:
We will strip human subject datasets of identifying sensitive information before publication.
...