About this document
This is a metadata application profile to provide basic interoperability between systems producing or consuming machine-actionable data management plans (maDMPS). Further fields can be added in specific deployments, but they do not guarantee interoperability. DMP tools can use any other fields in their internal data models.
This application profile is intended to cover a wide range of use cases and does not set any business (e.g. funder specific) requirements. I represents information over the whole DMP lifecycle.
For more information see examples, FAQ and useful links to consultations, documents, tools, prototypes, etc. developed by the working group.
Provides high level information about the DMP, e.g. its title, modification date, etc. It is the root of this application profile. The majority of its fields are mandatory.
Describes the project associated with the DMP, if applicable. It can be used to describe any type of project: that is, not only funded projects, but also internal projects, PhD theses, etc.
For specifying details on funded projects, e.g. NSF of EC funded projects.
Specifies the party which can provide any information on the DMP. This is not necessarily the DMP creator, and can be a person or an organisation.
For listing all parties involved in the process of the data management described by this DMP, and those parties involved in the creation and management of the DMP itself.
Provides a list of costs related to data management.
This follows the defintion of Dataset in the W3C DCAT specification. Dataset can be understood as a logical entity depicting data, e.g. raw data. It provides high level information about the data. The granularity of dataset depends on a specific setting. In edge cases it can be a file, but also a collection of files in different formats. See <a href=https://github.com/RDA-DMP-Common/RDA-DMP-Common-Standard/blob/master/docs/FAQ.md>FAQ</a> for more details.
This follows the defintion of Distribution in the W3C DCAT specification. Distribution points to a specific instance of a dataset. Hence, distribution contains information such as the format and size of files. A dataset can have several distributions.
Used to indicate the license under which data (each specific Distribution) will be made available. It also allows for modelling embargoes. See <a href=https://github.com/RDA-DMP-Common/RDA-DMP-Common-Standard/blob/master/docs/FAQ.md>FAQ</a> for more details.
Provides information on the system where data is stored. It can be used to provide details on a repository where data is deposited, e.g. a Core Trust Seal certified repository located in Europe that uses DOIs. It can also provide details on systems where data is stored and processed during research, e.g. a high performance computer that uses fast storage with two daily backups.
Security and Privacy
Used to indicate any specific requirements related to security and privacy of a specific dataset, e.g. to indicate that data is not anonymized.
For specifying equipment needed/used to create or process the data, e.g. a microscope, etc.
Provides a pointer to a metadata standard used to describe the data. It does not contain any actual metadata relating to the dataset.