Data Management Plans (DMPs) provide a blueprint for how to manage data throughout their life-cycle. In addition, many funders require a DMP as part of the grant application. We can help you create a DMP and provide feedback on your draft in a timely way to meet grant deadlines.
Get started with our DMP template
If you don't already have a draft data management plan, then start one now. Make a copy of our U of M DMP Template (Google Doc) or log in with your U of M ID to the DMPTool to draft a new plan to manage your data.
These templates conforms with federal funder requirements for data management plans.
Send us a copy of your DMP for feedback
We will review your plan within two business days and suggest additional things to consider or recommend using available tools and resources found across campus. Email your draft plan in MS Word doc, or send a Google doc link, to firstname.lastname@example.org.
Helpful tip: Please include a link to your funder/proposal that you are applying to so that we ensure any specific data sharing requirements are met.
Boilerplate language for using DRUM in your grant
The Data Repository for the University of Minnesota (DRUM) is the university’s open access data repository for data sharing that enables long-term access and preservation. If appropriate for your data, use this boilerplate language in your DMP to demonstrate your institutionally-backed strategy for data sharing and preservation:
A long-term data sharing and preservation plan will be used to store and make publicly accessible the data beyond the life of the project. The data will be deposited into the Data Repository for the University of Minnesota (DRUM), http://hdl.handle.net/11299/166578, a trusted data repository certified in 2017 by an international community-recognized CoreTrustSeal. This University Libraries’ hosted institutional data repository is an open access platform for dissemination and archiving of university research data. DRUM provides long-term preservation of digital objects using services such as migration (limited format types), off-site backup, bit-level checksums, and assigns a Digital Object Identifier (DOI) for archival citations. The data will be accompanied by the appropriate documentation, metadata, and code to facilitate reuse and provide the potential for interoperability with similar data sets.