RDA DMP Common Standard for machine-actionable Data Management Plans

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. It 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. DMP 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. Project 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. Funding For specifying details on funded projects, e.g. NSF of EC funded projects. Contact 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. Contributor 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. Cost Provides a list of costs related to data management. Dataset 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. Distribution The term "distribution" used here is as defined by the very widely used W3C DCAT metadata application profile. It is used to mean a particular instance of a dataset that has been, or is intended to be, made available in some fashion. It is important to separates the logical notion of a "dataset" from its distributions, of which there may be several, especially to attach more specific metadata properties such as "size" and "license". The lifecycle of the DMP has no particular bearing on this, and a "distribution" may be defined even if the DMP is never actually realised. License 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. Host 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. Technical Resource For specifying equipment needed/used to create or process the data, e.g. a microscope, etc. Metadata Provides a pointer to a metadata standard used to describe the data. It does not contain any actual metadata relating to the dataset.

Structure dmp contact contact_id identifier type mbox name contributor contributor_id identifier type mbox name role cost currency_code description title value created dataset data_quality_assurance dataset_id identifier type description distribution access_url available_until byte_size data_access description download_url format host availability backup__frequency backup_type certified_with description geo_location pid_system storage_type support_versioning title url license license_ref start_date title issued keyword language metadata description language metadata_standard_id identifier type personal_data preservation_statement security_and_privacy description title sensitive_data technical_resource description name title type description dmp_id identifier type ethical_issues_description ethical_issues_exist ethical_issues_report language modified project description end funding funder_id identifier type funding_status grant_id identifier type start title title

Properties in 'contact'

Properties in 'contact_id'

Properties in 'contributor'

Properties in 'contributor_id'

Properties in 'cost'

Properties in 'dataset'

Properties in 'dataset_id'

Properties in 'distribution'

Properties in 'dmp'

Properties in 'dmp_id'

Properties in 'funder_id'

Properties in 'funding'

Properties in 'grant_id'

Properties in 'host'

Properties in 'license'

Properties in 'metadata'

Properties in 'metadata_standard_id'

Properties in 'project'

Properties in 'security_and_privacy'

Properties in 'technical_resource'

Cite as

Tomasz Miksa, Paul Walk, Peter Neish. RDA DMP Common Standard for Machine-actionable Data Management Plans. http://doi.org/10.15497/rda00039