Skip to content

DMP IDs and Networked Data Management Plans (maDMPs)

Mary Uhlmansiek edited this page Mar 11, 2024 · 7 revisions

We are often asked if DMPs within the DMPTool are machine-actionable, and we can now confidently say yes! Over the past year we have added several new features to achieve this milestone. This work is funded by an EAGER grant from the NSF.

Below is a description of DMPTool features to support the creation of Networked DMPs.

What is a networked or machine-actionable DMP?

Networked DMPs are a vehicle for reporting on the intentions and outcomes of a research project that enable information exchange across relevant parties and systems. They contain an inventory of key information about a project and its outputs (not just data), with a change history that stakeholders can query for updated information about the project over its lifetime.

Why are IDs for DMPs important?

Utilizing IDs for DMPs allows information within a DMP to be fed across stakeholders, linking metadata, repositories and institutions, and allowing for notifications and verification, and reporting in real-time. A key goal of this new system is to reduce the burden on researchers by generating automated updates to a plan and facilitating seamless integration with systems and groups that support research.

As the NSF detailed in their May 2019 Dear Colleague Letter on Effective Practices for Data, it is recommended that researchers utilize PIDs for their data outputs and generate DMPs that allow for automated information exchange (machine-actionable DMPs, “maDMPs”). Expanding on the NSF Dear College Letter, the recent report by ARL, AAU, APLU and CDL, Implementing Effective Data Practices: Stakeholder Recommendations for Collaborative Research Support, provided key recommendations for effective data practices to support a more open research ecosystem and focused on using PIDs and maDMPs.

What identifiers are recorded within DMPs created using the DMPTool?

The DMPTool currently supports the following identifiers within a DMP:

  • IDs for DMPs
  • RORs for research organizations
  • Funder Registry IDs for funders
  • ORCiDs for DMP creators and collaborators
  • Registry of Research Data Repositories
  • RRID (in development)

How to get a unique ID for your DMP?

Anyone can receive a unique ID for their DMP via the DMPTool. For a user to generate an ID they are required to complete at least 50% of the questions within the DMP template, enter their ORCID and include the funder. There is a tab in the Create Plan module called “Finalize/Publish” within this tab users can set the visibility of the DMP and “Register” their plan by generating an ID. The ID will then display within the tool and link to a landing page for the identifier.

What is the connection between DMP IDs and ORCIDs?

DMP IDs generated via the DMPTool are automatically linked to the DMP creator’s ORCID record. This means that when a DMPTool user “Registers” their plan, a DMP ID is generated, and this record is automatically pushed to ORCID and included as a work on their ORCID profile page.

Where do DMP IDs resolve to?

The DMPHub was built to generate persistent identifiers (PIDs) for DMPs created via the DMPTool and to record updates to the DMP that occur over time. For example, as a project progresses the record would include related datasets and/or journal articles connected to a DMP.

The landing pages for DMP IDs also demonstrate the types of connections made possible by tracking a research project over time from the point of DMP creation.

Integrating networked DMPs with external systems

We welcome integrations utilizing networked DMPs. The DMPTool API complies with the RDA Common Standard Metadata schema v1.0, which is recommended for the transfer of DMP metadata between systems. Documentation on our API is available here. If you have an integration project please email us. We are actively looking for pilot partners and would love to hear from you.

Learn more

Clone this wiki locally