Data Management Plan (DMP)

In a nutshell, your goal is to organize your research lab in a way that will let you document and preserve your scientific products - including raw and derived data when possible. When delivering a project to a funder, it is important to ensure the funder can understand and reuse the products (code, data, apps) you have developed. For those reasons, more and more funders require a data management plan as part of their proposal submission process; therefore, it is a great skill to develop.

Having a plan to manage your data will save you from some potential painful hiccups and time as you progress through your project data life cycle. In other words, it is time well spent to develop your data management plan, and the earlier in your project, the better you have a good sense of how you will manage your data. The discussion with your project team about what should be included in the plan is as important as the plan itself since the questions you will have to answer will help you think more about your data (e.g., type, size, processing methods, etc.) and assign roles and responsibilities among project members.

Once your lab data are well managed, it becomes easier to archive and share relevant data in a publicly accessible data repository such as Dryad as your projects are completed or important milestones are achieved. For your work to generate a reproducible data archive, metadata and documentation must also be provided, as well as the scripts you have developed for your analysis. Here is a good example of a well-documented data archive: https://doi.org/10.25349/D9JK6N

Before writing your plan, we recommend you get familiar with the FAIR and CARE principles to guide your process.

Those two principles should be the overarching guidelines that will guide the development of your data management plan.

Developing your Lab Data Management Plan (DMP)

You might already have experience with writing project specific data management plans as they are often required in proposals. The process to develop your lab’s data management plan is very similar, but will be more focused on developing general guidelines for your lab that can be adapted for project specific needs. We recommend using the FAIR & CARE principles as guidance to maximize the reusability of your data by you, your collaborators, other researchers, and futureself. Your plan should ensure that detailed documentation adopting existing standards is developed during the entire duration of your project (don’t wait until the very end!!) and that this documentation is archived along with your data and code in a publicly accessible data repository will set you up for success.

Below is a set of questions that will help your team to develop your guidelines about the data and resources you will need along projects’ data lifecycle in your research lab.

  1. Describing the research data generated by your lab: Provide a description of the data the group will collect or re-use, including the file types, data set size, the number of expected files or sets, content, and source of the data (creator and method of collection).

    1. What data are needed?
    2. Are such data available?
    3. When and how will the data be acquired?
  2. Data formats:

    1. Are there any standard formats in the specific research field for managing or disseminating the data sets that have been identified (e.g., XML, ASCII, CSV, .shp, .gdb, GeoTIFF)?
    2. Who from the group will have responsibility for ensuring that data standards are properly applied, and data are properly formatted?
  3. Metadata: Metadata is documentation that helps make data sets reusable. Think about what details someone would need in order to be able to understand and use these files. For example, perhaps a readme.txt file is necessary to explain variables, the structure of the files, etc. In addition, it is recommended to leverage metadata disciplinary standards, including ontologies and vocabularies. Here is a good resource for metadata standards in environmental sciences. When applicable, also describe other scientific products - models, scripts, and/or workflows - your group will be producing using README files and documenting your code.

  4. Intellectual property and re-use: If data were collected from the client organization, does the group have the right to redistribute it? If so, are there any restrictions on redistribution? If the group created its data files, would it assign a Creative Commons license to its data?

  5. Data sharing and preservation: The data may have significant value to other researchers beyond this project, and sharing this data can be a valuable contribution to your field. Specify the extent to which data can be reused, including any access limitations. List any proprietary software that might be needed to read the files. If some data is not shareable due to confidentiality, non-disclosure agreements (NDA), or disclosure risk, state such limitations and the rationale behind them. Note that not being allow to share your data does not mean you can not document!! Not all data needs to be saved. Here are some questions to ask yourselves:

    1. If another researcher wanted to replicate the group’s work or re-use the group’s data, what data and documentation would be required for them to do so?
    2. Where will the data and metadata be stored after the project is completed?
    3. Is there a subject-specific and/or open-access repository that is appropriate for the data?

One advantage to depositing your data in a data repository is that you can get a DOI that lets you easily share and cite your data. Most of the data repositories also track views, downloads, and citations for your data archive, which can be used as a metric or a proxy for research impact.

Using your Data Management Plan

Ok, you have a plan, now what!? A data management plan should be seen as a living document that you update as your projects develop and data needs evolve. We thus recommend sharing this plan with all your team members and external partners when relevant. You can also encourage contribution from your lab members by choosing a file format that can be collectively edited and provide some versioning/track changes feature, such as Google Docs or other cloud-based storage and documents.

Further Reading Recommendations

  • Good overview of Data management concepts: Arteaga Cuevas, Maria; Taylor, Shawna; and Narlock, Mikala. (2023). Introduction to Research Data Management for Researchers. Data Curation Network Primer for Researchers on how to Manage Data
  • Good overview of the data lifecycle, including itemized checklist: https://osf.io/d8fqh


This work is licensed under CC BY 4.0

UCSB logo