Skip to the content.

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


Properties in 'contact'

NameDescriptionData TypeCardinalityExample Value
contact_idIdentifier for a contactNested Data Structure1
mboxE-mail address for a contactString1cc@example.com
nameName of a contact person or organisationString1Charlie Chaplin

Properties in 'contact_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a contactString1
typeTo specify a type of an identifier for a contact.
Allowed Values:
  • orcid
  • isni
  • openid
  • other
Term from Controlled Vocabulary1orcid

Properties in 'contributor'

NameDescriptionData TypeCardinalityExample Value
contributor_idIdentifier for a contributorNested Data Structure1
mboxE-mail address for a contributorString0..1john@smith.com
nameName of a contributorString1John Smith
roleContributors role(s) within the process of data management (incl. planning)String1..nData Steward

Properties in 'contributor_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a contributorString1http://orcid.org/0000-0000-0000-0000
typeTo specify a type of an identifier for a contributor.
Allowed Values:
  • orcid
  • isni
  • openid
  • other
Term from Controlled Vocabulary1orcid

Properties in 'cost'

NameDescriptionData TypeCardinalityExample Value
currency_codeAllowed values defined by ISO 4217.Term from Controlled Vocabulary0..1EUR
descriptionTo provide additional details about a cost, including specifying which activities or resources it relates to, such as making data FAIR, ensuring data accessibility, or enhancing its reusability.String0..1Storage and backup costs are calculated based on a 12-month storage period, daily incremental and weekly full backups, and a frequency of 4 restores per month, as outlined in the evaluation table at www.example-storagecostevaluation.com.
titleTitle of a costString1Storage and backup
valueCost value in the specified currencyNumber0..11000

Properties in 'dataset'

NameDescriptionData TypeCardinalityExample Value
data_quality_assuranceTo describe any quality assurance processes applied to a dataset, such as, to ensure its accuracy, reliability, consistency, and usability for its intended purposes. This includes systematic practices, procedures, and policies designed to maintain high data quality throughout its lifecycle.String0..nWe calibrate measuring equipment daily, run repeat samples to monitor consistency in measurements and results, and cross-check collected data with at least two colleagues for accuracy.
dataset_idIdentifier for a datasetNested Data Structure1
descriptionDescription is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file.String0..1The dataset includes detailed measurements of temperature, humidity, and soil moisture levels collected at various time intervals (every 30 minutes) across multiple locations. The dataset will also include metadata such as GPS coordinates, sensor calibration data, and environmental conditions. The primary objective of this dataset is to analyze the correlation between these variables and their impact on plant growth patterns over a 6-month period.
distributionTo provide technical information on a specific instance of data.Nested Data Structure0..n
is_reusedIndication if the dataset is reused, i.e., not produced in project(s) covered by this DMP.Boolean0..1true
issuedTo indicate a date when a dataset was published or released. Encoded using the relevant ISO 8601 Date compliant stringDate0..12019-06-30
keywordKeywordString0..nkeyword 1, keyword 2
languageLanguage of the dataset expressed using ISO 639-3Term from Controlled Vocabulary0..1eng
metadataTo describe metadata standards used. Nested Data Structure0..n
personal_dataTo indicate whether a dataset contains personal data. Personal data refers to any data that can identify an individual (e.g. name, birthdate, address, voice recordings, etc.).
Allowed Values:
  • yes
  • no
  • unknown
Term from Controlled Vocabulary1unknown
preservation_statementTo outline a plan for how and why a dataset will be preserved for long-term access, including for example storage redundancy, integrity checks (checksums, fixity checks), format migration, and a sustainability plan ensuring institutional commitment and funding.String0..1All research data will be stored in the university's secure data repository, backed up daily to ensure redundancy and prevent data loss. The dataset will be preserved in a standardized format (e.g. CSV, JSON) and will include detailed metadata for clarity. It will be accessible to the public via the university’s open-access platform three months after the completion of the project, with ongoing access ensured for a minimum of 5 years. Regular checks will be performed every 6 months to confirm the integrity and readability of the data.
security_and_privacyTo list all security and privacy measures applied to a dataset to protect sensitive information, for example encryption, anonymization, data masking, and compliance with data protection regulations (e.g. GDPR or HIPAA). It can also be used to express any security measures required for handling the dataset, e.g. only physical access, etc. Nested Data Structure0..n
sensitive_dataTo indicate whether a dataset contains sensitive data. Sensitive data refers to information that could pose risks to individuals or organizations for example financial information, medical records, passwords and social security numbers.
Allowed Values:
  • yes
  • no
  • unknown
Term from Controlled Vocabulary1unknown
technical_resourceList all technical resources (e.g. tools or software) required for any stage of a dataset lifecycle (e.g. microscopes, sensors, Jupyter Notebook, Galaxy workflows, measuring devices)Nested Data Structure0..n
titleTitle is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file.String1Fast car images
typeIf appropriate, type according to: DataCite and/or COAR dictionary. Otherwise use the common name for the type, e.g. raw data, software, survey, etc. https://schema.datacite.org/meta/kernel-4.1/doc/DataCite-MetadataKernel_v4.1.pdf http://vocabularies.coar-repositories.org/pubby/resource_type.htmlString0..1image

Properties in 'dataset_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a dataset String1https://hdl.handle.net/11353/10.923628
typeTo specify a type of an identifier for a dataset.
Allowed Values:
  • handle
  • doi
  • ark
  • url
  • other
Term from Controlled Vocabulary1handle

Properties in 'distribution'

NameDescriptionData TypeCardinalityExample Value
access_urlA URL of the resource that gives access to a distribution of the dataset. e.g. landing page.URL0..1http://some.repo...
available_untilIndicates how long this distribution will be/ should be available. Encoded using the relevant ISO 8601 Date compliant stringDate0..12030-06-30
byte_sizeSize of a distribution in bytesNumber0..1690000
data_accessIndicates access mode for data.
Allowed Values:
  • open
  • shared
  • closed
Term from Controlled Vocabulary1open
descriptionDescription is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file.String0..1 This dataset contains measurements from a single research location at the University of California's Arboretum in Davis, California, collected every 30 minutes over a 6-month period from January 2024 until June 2024. Each file includes time-stamped data for temperature, humidity, and soil moisture, listed by date and time. The data is organized in CSV format, with each row representing a specific time point, including the location (UC Arboretum), timestamp, and the corresponding environmental variables.
download_urlThe URL of the downloadable file in a given format. E.g. CSV file or RDF file.URL0..1http://some.repo.../download/...
formatFormat according to: https://www.iana.org/assignments/media-types/media-types.xhtml if appropriate, otherwise use the common name for this formatString0..nimage/tiff
hostTo provide information on a system where data is stored. This can be all types of systems used within the whole data management lifecycle, i.e. temporary storage on networked hard drives, as well as, repository systems where data is shared with others.Nested Data Structure0..1
licenseTo list all licenses applied to a specific distribution of data.Nested Data Structure0..n
titleTitle is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file.String1Full resolution images

Properties in 'dmp'

NameDescriptionData TypeCardinalityExample Value
contactContact person for a DMPNested Data Structure1
contributorTo list people that play role in data management related to this DMP, e.g. resoponsible for performing actions described in this DMP.Nested Data Structure0..n
costTo list costs related to data management. Providing multiple instances of a 'Cost' allows to break down costs into details. Providing one 'Cost' instance allows to provide one aggregated sum.Nested Data Structure0..n
createdDate and time of the first version of a DMP. Must not be changed in subsequent DMPs. Encoded using the relevant ISO 8601 Date and Time (with timezone) compliant stringDateTime12019-03-13T13:13:00Z
datasetTo describe data on a non-technical level.Nested Data Structure1..n
descriptionAny text related to this DMP, optionally describing the project. It can include important information that doesn't fit elsewhere.String0..1This DMP is for our new project
dmp_idIdentifier for the DMP itselfNested Data Structure1
ethical_issues_descriptionTo describe considerations that require compliance with laws and regulations (e.g. GDPR, animal welfare) due to the involvement of humans, animals, or sensitive information. This includes ensuring informed consent from participants, protecting privacy and confidentiality, and adhering to applicable legal and ethical standards throughout the research.String0..1There are ethical issues, because...
ethical_issues_existTo indicate whether there are ethical issues related to data that this DMP describes.
Allowed Values:
  • yes
  • no
  • unknown
Term from Controlled Vocabulary1yes
ethical_issues_reportTo indicate where a report/document that details all identified ethical issues (might be for example emit from a meeting with an ethical committee)URL0..1http://report.location
languageLanguage of the DMP expressed using ISO 639-3Term from Controlled Vocabulary1eng
modifiedMust be set each time DMP is modified. Indicates a DMP version. Encoded using the relevant ISO 8601 Date and Time (with timezone) compliant stringDateTime12020-03-14T10:53:49Z
projectTo list all project(s) for which the data and work are described in this DMPNested Data Structure0..n
titleTitle of a DMPString1DMP for our new project

Properties in 'dmp_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a DMPString1https://doi.org/10.1371/journal.pcbi.1006750
typeTo specify a type of an identifier for a DMP.
Allowed Values:
  • handle
  • doi
  • ark
  • url
  • other
Term from Controlled Vocabulary1doi

Properties in 'funder_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a funder. It is recommended to use CrossRef Funder Registry.String1501100002428
typeTo specify a type of identifier for a funder.
Allowed Values:
  • fundref
  • url
  • other
Term from Controlled Vocabulary1fundref

Properties in 'funding'

NameDescriptionData TypeCardinalityExample Value
funder_idIdentifier of a funderNested Data Structure1
funding_statusTo express different phases of project lifecycle.
Allowed Values:
  • planned
  • applied
  • granted
  • rejected
Term from Controlled Vocabulary0..1granted
grant_idIdentifier of a grantNested Data Structure0..11234567

Properties in 'grant_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a grantString1776242
typeTo specify a type of an identifier for a grant.
Allowed Values:
  • url
  • other
Term from Controlled Vocabulary1other

Properties in 'host'

NameDescriptionData TypeCardinalityExample Value
availabilityAvailability of a host (preferably as a percentage)String0..199,5
backup_frequencyFrequency of backups provided by a hostString0..1weekly
backup_typeLocation and/or type of the backup provided by a hostString0..1tapes
certified_withTo indicate host trustworthiness via a standard repository certificate.
Allowed Values:
  • din31644
  • dini-zertifikat
  • dsa
  • iso16363
  • iso16919
  • trac
  • wds
  • coretrustseal
Term from Controlled Vocabulary0..1coretrustseal
descriptionDescriptionString0..1Repository hosted by...
geo_locationPhysical location of a server (where the distribution is actually stored) expressed using ISO 3166-1 country code.Term from Controlled Vocabulary0..1AT
pid_systemPID System used by a host.
Allowed Values:
  • ark
  • arxiv
  • bibcode
  • doi
  • ean13
  • eissn
  • handle
  • igsn
  • isbn
  • issn
  • istc
  • lissn
  • lsid
  • pmid
  • purl
  • upc
  • url
  • urn
  • other
Term from Controlled Vocabulary0..ndoi
storage_typeTo indicate whether a host supports versioning of data distributions. String0..1LTO-8 tape
support_versioning
Allowed Values:
  • yes
  • no
  • unknown
Term from Controlled Vocabulary0..1yes
titleTitleString1Super Repository
urlA URL of an infrastructure hosting a distribution of a datasetURL1https://zenodo.org

Properties in 'license'

NameDescriptionData TypeCardinalityExample Value
license_refLink to license document.URL1https://creativecommons.org/licenses/by/4.0/
start_dateIf date is set in the future, it indicates embargo period. Encoded using the relevant ISO 8601 Date compliant stringDate12019-06-30

Properties in 'metadata'

NameDescriptionData TypeCardinalityExample Value
descriptionTo provide any details on the choice of the metadata standardString0..1The ISO 19115 Metadata Standard is applied to describe each geospatial dataset. Metadata includes the satellite's sensor type (e.g. Landsat 8 OLI), acquisition date, spatial resolution (30m), and cloud cover percentage.
languageLanguage of a metadata expressed using ISO 639-3Term from Controlled Vocabulary1eng
metadata_standard_idIdentifier of Metadata StandardNested Data Structure1

Properties in 'metadata_standard_id'

NameDescriptionData TypeCardinalityExample Value
identifierTo indicate the specific value of an identifier for a metadata standardString1http://www.dublincore.org/specifications/dublin-core/dcmi-terms/
typeTo specify a type of an identifier for a metadata standard.
Allowed Values:
  • url
  • other
Term from Controlled Vocabulary1url

Properties in 'project'

NameDescriptionData TypeCardinalityExample Value
descriptionProject abstract providing an overview of the project's goals and scopeString0..1This project aims to analyze the impact of urbanization on local biodiversity by collecting and assessing environmental data from multiple urban centers. Using remote sensing, field observations, and statistical modeling, the study will identify key factors influencing species diversity and habitat loss. The findings will support sustainable urban planning initiatives and inform conservation strategies.
endProject end date. Encoded using the relevant ISO 8601 Date compliant stringDate0..12020-03-31
fundingFunding related with a projectNested Data Structure0..n
startProject start date. Encoded using the relevant ISO 8601 Date compliant stringDate0..12019-04-01
titleProject titleString1Our New Project

Properties in 'security_and_privacy'

NameDescriptionData TypeCardinalityExample Value
descriptionDescribe a security and privacy measure applied to a dataset to protect sensitive informationString0..1The dataset undergoes anonymization by applying data masking techniques. Names, addresses, and phone numbers are replaced with pseudonyms or randomly generated identifiers. Specific details, such as exact birthdates, are generalized into age ranges.
titleTitle a measure applied to a datasetString1Anonymization of Personally Identifiable Data

Properties in 'technical_resource'

NameDescriptionData TypeCardinalityExample Value
descriptionDescribe a technical resource (e.g. tools or software) required for any stage of a dataset lifecycle (e.g. microscopes, sensors, Jupyter Notebook, Galaxy workflows, measuring devices)String0..1The Celestron 44102 Inverted Biological Microscope was used to examine biological samples, such as cells and microorganisms, with high-resolution optics.
nameName a resource applied to a datasetString1Celestron Microscope

Cite as

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