The Finnish metadata application profile for maDMP is presented in the figure above. The entire graph is the DMP, and in contrast to the RDA maDMP standard vizualization, the "DMP" section is named as DMP_generic as it contains general information of the DMP, which are not part of any sub-sections: contact, contributor, cost, dataset or project. Change to the previous version of the RDA standard is also that the distribution is under the dataset. The Finnish maDMP metadata application profile also differs so that the security, policy, ethis, rights and risks are described at project level. However, if the organisation makes the decision, they can implement the reference data model and describe this section or parts of it under the dataset, at dataset level.
Metadata profile for national reference data model for maDMPs in Finland is presented in Table 2 below this page.
The mapping to requirements of Science Europe, DMP Evaluation Rubric, and Research Council of Finland has been done as part of the OSTrails project. Link to mapping
Mapping indicates which fields of the reference data model are required by the funder. These fields are marked as mandatory in the national reference data model.
Metadata Related columns are still being updated i.e. work in progress.
Please note that RCF emphasizes that DMP should be maximum 3 pages; overlaps with research plan or publication plan needs to be avoided.
Group discussions started the discussion of the content of the metadata application profile to specific needs of Consortia DMP, self-funded and student maDMP's. It was suggested that the student maDMP could be built upon the data models used in Universities of applied sciences. National recommendation of self-funded DMPs requires more consultation from universities and research organisations. For the Consortia DMPs experience from large scale Consortia projects was shared on how the solutions of Consortia DMPs have been made, either defining the DMP specifically for the needs, or utilizing e.g. FAIR Wizard or ARGOS. It was discussed that there is a need from the DMPOnline to make technical development for DMPTuuli so that it would support Consortia DMPs. In the data model itself, the new RDA maDMP standard contains fields e.g. related identifier, which can be used as for this purpose as well, with appropriate fine-tuning. It was agreed in the all hands that this will be worked further.
Structural DMP template and integrations with DMPTuuli - presentation by Jari Friman Tampere University. Link to presentation
DMPTuuli has been adjusted maDMP ready by updating the terms of use to allow transfering DMP content information to institutional services. DMPTuuli has also two APIs: one for transferring the DMP metadata, and the other one for transferring the DMP content.
The use case of the maDMP and MyCSC API interphase was presented and discussed. University of Tampere and University of Oulu were interested to pilot this, and there has been also discussions with University of Helsinki and University of Jyväskylä.
The usage of the digital objects has been increased also in the RDA maDMP standard. One example of further usage is the MSCR which is very promising for digitalizing the researchers resource applications from the CSC. See the figure below described by Tommi.
Table 2. Metadata profile for national reference data model for maDMPs in Finland (version 8.12.2025)
Latest version to be updated is here: https://wiki.eduuni.fi/x/2WzrJw
| 1. Level | 2 Level | 3 Level | 4 Level | B. Description | C. Data type | D.Cardinality | Example values | Hierarchy | E. RDA maDMP standard 1=RDA; 2=National, 3=OSTrails Commons | F. DCS Mapping 1=Required; 0=No | F. RCF Mapping 1=Required; 0=No | G-1. National DMP requirement 1=Required; 2=Optional; 0=No | G-2 National CSC requirement for LARGE projects 1=Required; 2=Optional; 0=No | Self-funded light DMP | Consortium DMP | Student DMP | H. Interoperability from data source 1=automate;2=DO;3=manual |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dataset | #_Nested Data Structure if many datasets are used. Relationships to 1..* datasets are defined at DMP level. DMP has "dataset" association that can relate to many datasets. Each data set can have multiple files/distributions. | ||||||||||||||||
| To describe data on a general level. Describe how datasets used can be categorised. 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 FAQ for more details. | Nested Data Structure | 1..n | At least one dataset should be defined. See "Dataset" in the table. | Section in 'DMP' | 1 | 0 | 0 | 1 | 1 | 1 if can be derived from Dataset information otherwise 3 | |||||||
| alternate_identifier | To indicate the specific value of an identifier for an affiliation | String | 1 | 03yrm5c26 | Properties in 'Dataset' | 1 | 0 | 0 | 0 | 0 | |||||||
| type | To specify a type of an identifier for an affiliation. Suggested Values: ror, grid, isni | String | 1 | ror | Properties in 'Alternate_identifier' | 1 | 0 | 0 | 0 | 0 | |||||||
| data_quality_assurance | To 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. This may also include processes such as calibration, repeated samples or measurements,standardised data capture,data entry validation, peer review of data, or representation with controlled vocabularies. | String | 0..n | We 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. | Properties in 'Dataset' | 1 | 1 | 0 | 1 | 0 | 3 | ||||||
| data_organization | To indicate how the data will be organised during the project mentioning | String | 0..n | Conventions, version control, and folder structures. | Properties in 'Dataset' | 3 | 1 | 1 | 1 | 0 | |||||||
| dataset_id | Dataset ID Preferred values:DOI, PID, URN, URL, handle, ark, other digital ID. A trustworthy, long-term repository will provide a persistent identifier. | String | 1 | Dataset may not exist when DMP is defined. DMP tool should provide temporary ID before dataset gets PID by some way. | Properties in 'Dataset' | 1 | 1 | 0 | 2 | 0 | 1 | 2 | |||||
| identifier | To indicate the specific value of an identifier for a dataset | String | 1 | https://hdl.handle.net/11353/10.923628 | Properties in 'Dataset_id' | 1 | 1 | 0 | 0 | 0 | 1 | ||||||
| type | To specify a type of an identifier for a dataset. Suggested Values: handle, doi, ark, url | String | 1 | pid | Properties in 'Dataset_id' | 1 | 1 | 0 | 0 | 0 | 1 | ||||||
| description | Description of dataset. Description 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. Explain the foreseeable research uses (and/or users) for the data. | String | 1 | Description at general level only. Space limitatation to be set, e.g. max 2000 char. Review how much description is needed by PI, Organization, Funder. | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 1 | 3 | ||||||
| issued | Date of dataset been issued. Encoded using the relevant ISO 8601 Date and Time compliant string. | Date | 0..1 | Properties in 'Dataset' | 1 | 0 | 0 | 1 | 0 | ||||||||
| title_dataset | Title 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. | String | 1 | Properties in 'Host' within 'Distribution' | 1 | 0 | 0 | 1 | 0 | 3 | |||||||
| is_reused | Indication if the dataset is reused, i.e., not produced in project(s) covered by this DMP. | Boolean | 0..1 | TRUE | Properties in 'Dataset' | 1 | 1 | 0 | |||||||||
| date_issued | To indicate a date when a dataset was published or released. Encoded using the relevant ISO 8601 Date compliant string | Date | 1 | Properties in 'Dataset' | 1 | 0 | 0 | 2 | 0 | ||||||||
| keyword | Keywords for data that is opened or catalogued | String | 0..n | Terms from controlled vocabulory | Properties in 'Dataset' | 1 | 0 | 0 | 1 | 0 | 1 / 3 | ||||||
| language | Language of the dataset expressed using ISO 639-3 | Term from Controlled Vocabulary | 0..n | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 0 | 1 / 3 | |||||||
| methodology | To describe other documentation needed to enable re-use. | String | 0..n | Information on the methodology used to collect the data, analytical and procedural information, definitions of variables, units of measurement, at general level. | Properties in 'Dataset' | 3 | 1 | 1 | 2 | 2 | |||||||
| personal_data | Whether the dataset contains personal data Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Associated with a single dataset, is this personal data the data of the data providers or of the target data? What is the role of individuals? Yes or No / Yes or No.FI restriction: It is assumed that "Unknown" is not an option here after submission to Funder, and researcher must be able to judge whether data contains personal data or consult about it.Type of personal data will be in its own section.Can trigger automatic data protection processes. | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 1 | 1 | 3 | |||||
| preservation_statement | To outline a plan for how and why a dataset will be preserved for long-term access, including a sustainability plan ensuring institutional commitment and funding. To indicate what data must be retained or destroyed for funders requirements, contractual, legal, or regulatory purposes. Indicate where the data will be deposited. If no established repository is proposed, to demonstrate that the data can be curated effectively beyond the lifetime of the grant. To demonstrate that the repositories policies and procedures (including any metadata standards, and costs involved) have been checked. | String | 0..n | All 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. Specification can also be given for example storage redundancy, integrity checks (checksums, fixity checks), and format migration. | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 1 | |||||||
| property_rights_explanation | To explain if when dealing with personal data, data protection laws are complied with. Indication whether intellectual property rights are affected, and if so, specification of which and how will they be dealt with. | String | 0..n | Explanation on impact of GDPR, Database Directive, sui generis rights on data management | Properties in 'Dataset' | 1 | 1 | 2 | 0 | ||||||||
| related_identifier | To provide references to related resources, such as publications, datasets or software, that are associated with the dataset. This helps to establish connections between different research outputs and enhances the discoverability and context of the dataset. | Nested Data Structure | 0..n | Properties in 'Dataset' | 1 | ||||||||||||
| restriction_explanation | To explain, if there are any restrictions on the re-use of third-party data. | String | 0..n | Properties in 'Dataset' | 3 | 1 | 0 | 2 | 0 | ||||||||
| rights | A statement that concerns all rights not addressed with license, such as copyright statements | String | 0..1 | This dataset incorporates third-party materials that are subject to additional rights and restrictions. Users must obtain permission from the original rights holders before reuse. | Properties in 'Dataset' | 1 | |||||||||||
| sensitive_data | Whether there are legal restrictions that apply to using this data, e.g. military use, commercial restrictions, endangered species Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Related to the dataset, how can we ensure that this is not asked except when it is likely?Yes or No / Yes or No or UnknownDual use and import controls?FI restriction: This should be yes/no after submission to Funder. In dataset we need to know if there is sensitive/confidential information or not. That triggers then more questions in security & privacy section. | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 3 | |||||||
| title | Data set title / name Title 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. | String | 1 | There can be many data sets, the information is related to one entity. A so-called metax entity, i.e. one must be able to express a wide variety of entities that then have attributes.Example "Fast car images" | Properties in 'Dataset' | 1 | 1 | 1 | 1/3 | ||||||||
| type | If 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.pdfhttp://vocabularies.coar-repositories.org/pubby/resource_type.html Data set type (indication interview, questionnaire, photos, video, measurement, samples, simulation, code) | Controlled vocabulary | 0..1 | Properties in 'Dataset' | 1 | 1 | 1 | 0 | 2 / 3 | ||||||||
| category | Describe categories of dataset | Term from Controlled Vocabulary | 0..n | Categories need to be defined Controlled vocabulory by Scientific field | Properties in 'Dataset' | 2 | 2 | 0 | 3 | ||||||||
| data_field_of_science | Specify the discipline of the data. Different repositories/repositories use different classifications of disciplines. Recommended to use the UNESCO science classification if no speficic other guidance. | Term from Controlled Vocabulary | 0..1 | Properties in 'Dataset' | 2 | 1 | 1 | ||||||||||
| data_landing_page | Give the link / PID to landing page of data | link / PID | 0..1 | Properties in 'Dataset' | 2 | 1 | 0 | 3 | |||||||||
| data_sharing_issues | How legal and ethical issues related to the sharing of data (e.g. ownership, copyright, sensitivity) will be resolved | String | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| data_sharing_contracts | Are contracts needed prior to sharing data? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| data_sharing_ownership | Is the ownership of data clear for data sharing? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| data_sharing_copyright | Are the copyright issues clear related to data sharing? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| data_sharing_sensitivity | Are possible issues related to sharing sensitive data cleared? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| data_sharing_other | Describe any emerging other issues of data sharing | String | 0..1 | Properties in 'Dataset' | 2 | 1 | 1 | 0 | 3 | ||||||||
| format | Description of used dataset formats during the active research. For example database, csv, xml, json.(Format of the dataset to be used. - Format of the datasets to be published / distributed after project is different) | Term from Controlled Vocabulary | 0..1 | Relates to one data set How does this relate to other outputs than datasets like code? Or code that is close related to data usability, e.g. link or PID?Format vs. Type? What is the difference.File format should be in distribution, not here. | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 2 | ||||||
| method_quality_assurance | Method describing how the quality assurance has been conducted | Term from Controlled Vocabulary | 1 | Example: TAU list as an example.There is a need to develop a list related to disciplines | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||
| reuse | Is previously collected data reused in this project (Whether the data is collected, created or comes from elsewhere) Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | |||||||
| resuse_support_description | Indicate whether potential users need specific tools to access and (re-)use the data. Consider the sustainability of software needed for accessing the data. Indicate whether data will be shared via a repository, requests handled directly, or whether another mechanism will be used? Indicate whether additional resource will be needed to prepare data for deposit or to meet any charges from data repositories. Explain how much is needed and how such costs will be covered. | String | 0..n | Properties in 'Dataset' | 2 | 1 | 1 | 2 | 1 | ||||||||
| source | Data source | String | 1 | Example "pid"Relates to one data set, can include ready-made options, but also an open text fieldReferencing can be really confusing. You can use data obtained from Twitter. Or dataset that somebody else compiled from Twitter... What do you reference here? Or do you make derivate dataset based on already existing dataset that is compiled from twitter? | Properties in 'Dataset' | 2 | 1 | 0 | 2 / 3 | ||||||||
| Dataset - Dataset Lifecycle | This is extension linked to Dataset - National addition in maDMP reference data model in Finland | ||||||||||||||||
| data_lifecycle | Describe at general level data lifecycle at a general level, and how open science criteria will be applied. | String | 0..1 | Data will be shared in active phase using Allas, after the project data will be shared via Fairdata IDA, and data paper will be published. The aim is to support reuse of the data. | Properties in 'Dataset' | 0 | 2 | 1 | 1 | 3 | |||||||
| archiving_date | When to archive? Encoded using the relevant ISO 8601 Date and Time compliant string | DateTime | 0..1 | Active data can be deleted and archived at the same time | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | ||||||||
| archiving_location | Where to archive? Allowed Values from: CSC Service Catalogue & organization's own archiving services | Term from Controlled Vocabulary | 0..1 | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 2 | 3 | ||||||||
| archiving_services | Are archiving services or long term preservation for data needed? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 1 | Relates to data set, and how to determine the value of data?Is this long-term storage, e.g. 20 in Zenodo, archiving in institutional archive or something else? | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | ||||||||
| backup | How data will be backed up during the project? To be planned by the researcher or organization specific solutions? | String | 1 | Utilisation of prefilled information derived from backup of services used | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | ||||||||
| closure_justification | If the project does not collect or produce any data fully or partially suitable for reuse, justify why the data cannot be made available even partially. | String | 1 | This is mandatory if data is closed. Should there be dataset level field for dataset publication (open / closed) ? | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | ||||||||
| data_collected | Summarise data collected for this project | String | 0..n | Properties in 'Dataset lifecycle' | 2 | 1 | 0 | 3 | |||||||||
| data_retention | How data retentions are managed? | String | 1 | Mandatory for large data intensive projects (At CSC >50 TB)Data retention plan is needed for managing the size of the project | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 1 | 3 | |||||||
| data_produced | Summarise data produced as an outcome of the project | String | 0..n | Properties in 'Dataset lifecycle' | 2 | 1 | 0 | 3 | |||||||||
| data_users | With whom will the data be shared during the project? Allowed Values:Open,In DMP defined research consortium,In home organization, To specified peopleTo other projectsTo service providersComplex structure | Term from Controlled Vocabulary | 0..n | Refers to the technical solutions, will a DPA be needed? Is joint controller agreement, NDAs etc. already elsewhere? Or does this refer to the consortium projects? | Properties in 'Dataset lifecycle' | 2 | 1 | 0 | 3 | ||||||||
| deletion | How is data deleted/destroyed? | String | 1 | Could be specified that this relates to unpublished data. Or data that are mentioned to be shared e.g. for 5 or 10 years, etc. | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | ||||||||
| deletion_date | When is data deleted/destroyed? Encoded using the relevant ISO 8601 Date and Time compliant string | DateTime | 0..1 | Could be specified that this relates to unpublished data. | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | ||||||||
| deletion_no | If data will not be deleted in the end of the project from active storage, give an explanation as to why. | String | 0..1 | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | |||||||||
| deletion_plannedtiming | If date cannot be given, then description of the planned deletion stage and approximate timing | String | 0..1 | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | |||||||||
| description | Summarise description of all datasets created in project if many, and after the project at general level, and how they are managed.Description is also 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. | String | 0..1 | Funder and CSC needs this information | Properties in 'Dataset lifecycle' | 2 | 1 | 0 | 3 | ||||||||
| exit_plan | What is the exit plan from computational and storage services in the end of the project? | String | 1 | Exit plan is needed to ensure that research data with value for re-use is saved within the available resources | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 1 | 1 | 3 | ||||||
| open_location | Where will the data be opened? Define the repositories and archives, and by whom | String | 1 | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | Special requirements for data repositories for preliminary data? | |||||||||
| shareage_solution | How the data will be shared during the project? Define technical solutions planned to be used? | Term from Controlled VocabularyChoose from Service catalog | 1..n | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | |||||||||
| storage_length | How long the data is stored for the original research purpose. Give the time estimate in years | Number | 1 | Example: "5 years"Relates to dataset, original purpose | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 1 | 3 | |||||||
| storage_location | Where will the data be stored during the project? | URN from CSC Service Catalogue & list presented by organization, if something else, what? | 1..n | Relates to a dataset, extra-important if data subject to the Act on the Secondary Use of DataAdd to general data life-cycleSpecify by data set if needed | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 1 | 3 | |||||||
| version_mgmt | How the data versions are managed? | String | 1 | Mandatory for large data intensive projects (At CSC >50 TB) | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | ||||||||
| Dataset - Creator | This is extension linked to Dataset - National addition in maDMP reference data model in Finland | ||||||||||||||||
| creator | To specify the creators of the dataset. Orcid, ROR (for functionability selection person or organization; the use list of previously given names of organizations /DMP author and contributors) | Nested data structure | 1..n | ORCID | Properties in 'Dataset' | 1 | 1 | 1 | 0 | ||||||||
| affiliation_id | Identifier for an affiliation ((ROR of organization of contact)) | String (e.g. ROR) | 0..1 | ROR | Properties in 'Creator' | 1 | 1 | 1 | 1 | 2 | |||||||
| creator_id | Properties in 'Creator' | 1 | 1 | 0 | 2 | ||||||||||||
| identifier | To indicate the specific value of an identifier for a creator | String | 1 | s0000-0000-0000-0000 | Properties in 'Creator_id' | 1 | 1 | 0 | 1/3 | ||||||||
| type | To specify a type of an identifier for a creator. Suggested Values: orcid, isni, openid, other | String (e.g. orcid) | 1 | orcid | Properties in 'Creator_id' | 1 | 1 | 0 | 1/3 | ||||||||
| email_creator | E-mail of the creator | String | Properties in 'Creator' | 1 | 1 | 1 | 0 | 1/3 | |||||||||
| name | Name of an affiliation ((Organization of contact)) | String | 0..1 | Some University | Properties in 'Creator' | 1 | 1 | 1 | 1 | 1 (from ORCID/ROR) / or 3 | |||||||
| Dataset - 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. | ||||||||||||||||
| distribution | Technical information on a specific instance of dataset | Nested Data Structure | 0..n | This might need more clarification, as it relates to resources/infra needed. | Properties in 'Dataset' | 1 | 1 | 2 | 3 | ||||||||
| access_url | A URL of the resource that gives access to a distribution of the dataset. e.g. landing page. | PID URL | 0..1 | In case of DMP you should use these to describe active use of the data. Others should be in life-cycle. | Properties in 'Distribution' | 1 | 1 | 0 | 3 | ||||||||
| available_until_url | Indicates how long this distribution will be/ should be available. Encoded using the relevant ISO 8601 Date and Time compliant string | DateTime | 0..1 | Properties in 'Distribution' | 1 | 1 | 1 | 0 | 3 | ||||||||
| byte_size | Estimated byte size :S: < 10 TB, M: 10-50 TB , L: 50-100TB, XL: 100-200 TB, XXL: > 200 TB | Term From Controlled Vocabulary | 1 | E.g. S < 10 TB, 10 <= M < 50 TB, 50 < L <= 100 TB, 100 < XL <= 200 TB, 200 < XXLImportant as it affects what all tools are available.Number or Size Category: S, M, L, XL, XXL | Properties in 'Distribution' | 1 | 1 | 1 | 0 | 3 | |||||||
| data_access | Indicates access mode for data and data sharing. Allowed Values:open,shared (embargo,requires login, requires permission), closed | Term from Controlled Vocabulary | 1 | Example: "Open"This can change during the study. First I use it 3 years as closed, then I open it. Should here be what I want to do after the active use or what happens right now? → Should be the current publication status of the distribution. Dataset lifecycle documents the plan for the dataset.National extensions needed with SD & Kielipankki. | Properties in 'Distribution' | 1 | 1 | 1 | 0 | 3 | |||||||
| description | Description 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. Explain how the data will be discoverable and shared. | String | 1 | Data will be deposited in a trustworthy data repository, indexed in a catalogue, use of a secure data service, direct handling of data requests, or by using another mechanism.. | Properties in 'Distribution' | 1 | 1 | 1 | 0 | 3 | |||||||
| download_url | The URL of the downloadable file in a given format. E.g. CSV file or RDF file. | PIDURL | 0..1 | Properties in 'Distribution' | 1 | 1 | 0 | 3 | |||||||||
| format | Format according to: https://www.iana.org/assignments/media-types/media-types.xhtml if appropriate, otherwise use the common name for this format | String | 0..n | Properties in 'Distribution' | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_start_time | The start time covered by the dataset for observations (e.g., the time during which observations were made). In datetime format (yyyy-MM-dd'T'HH.mm.ss.SSSXXX). | String | 0..1 | Properties in 'Distribution' | 2 | 1 | 0 | 1/3 | |||||||||
| data_end_time | The end time covered by the dataset for observations (e.g., the time during which observations were made). In datetime format (yyyy-MM-dd'T'HH.mm.ss.SSSXXX). | String | 0..1 | Properties in 'Distribution' | 2 | 1 | 0 | 1/3 | |||||||||
| publisher | Publisher of dataset, ROR, Orcid (for functionability selection organization or person; the use list of previously given names of organizations /DMP author and contributors) | Nested data structure | 1 | Properties in 'Distribution' | 2 | 1 | 0 | 3 | |||||||||
| research_infrastructure | Name the used infrastructure | String | 0..n | Should this be on some other level in the DMP? | Properties in 'Distribution' | 2 | 1 | 0 | 1/3 | ||||||||
| restriction_grounds | Mandatory if data set is not open | String | 0..n | Properties in 'Distribution' | 2 | 1 | 0 | 1 | |||||||||
| Dataset - Distribution - Host | |||||||||||||||||
| host | To 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. To provide information on service provided by infrastructure (e.g. repository) where data is stored. Service URN | Nested data structure | 0..1 | Properties in 'Distribution' | 1 | 1 | 0 | 3 | |||||||||
| availability | Availability | String | 0..1 | 99,5 | Properties in 'Host' | 1 | 1 | 0 | 3 | ||||||||
| backup_frequency | Backup Frequency - Describe how often the backup will be performed. | String | 0..1 | weekly | Properties in 'Host' | 1 | 1 | 1 | 0 | 3 | |||||||
| backup_type | Backup Type - Describe where the data will be stored and backed up during research activities. It is recommended to store data in least at two separate locations. | String | 0..1 | tapes | Properties in 'Host' | 1 | 1 | 1 | 0 | 3 | |||||||
| certified_with | Repository certified to a recognised standard Allowed Values:din31644,dini-zertifikat,dsa,iso16363,iso16919,trac,wds,coretrustseal | Term from Controlled Vocabulary | 0..1 | coretrustseal | Properties in 'Host' | 1 | 1 | 0 | 3 | ||||||||
| data_recovery_explanation | If you are using other resources than in your own organization or CSC service provision, explain how the data will be recovered in the event of an incident. | String | 0..n | Research organization level | Properties in 'Host' | 3 | 1 | 2 | |||||||||
| description | Description | String | 0..1 | Repository hosted by... | Properties in 'Host' | 1 | 1 | 0 | 3 | ||||||||
| geo_location | Physical location of the data expressed using ISO 3166-1 country code. | Term from Controlled Vocabulary | 0..1 | AT | Properties in 'Host' | 1 | 1 | 0 | 3 | ||||||||
| host_id | Identifier of Host. | Nested data structure | 0..n | Use of robust host X, with managed storage with automatic backup, provided by IT support services of the home institution. Following the X instructions, data is not stored on laptops, stand-alone hard drives, or external storage devices such as USB sticks. | Properties in 'Host' | 1 | 1 | 1 | 2 | ||||||||
| identifier | To indicate the specific value of an identifier for a host | String | 1 | https://example.org/repo | Properties in 'Host_id' | 1 | 1 | 2 | |||||||||
| type | To specify a type of an identifier for a host. Suggested Values: url | String | 1 | url | Properties in 'Host_id' | 1 | 1 | 2 | |||||||||
| pid_system | PID System Allowed Values: ark, arxiv, bibcode, doi, ean13, eissn, handle, igsn, isbn, issn, istc, lissn, lsid, pmid, purl, upc, url, urn, other | Term from Controlled Vocabulary | 0..n | doi | Properties in 'Host' | 1 | 1 | 2 | 3 | ||||||||
| storage_type | The type of storage required | String | 0..1 | LTO-8 tape | Properties in 'Host' | 1 | 1 | 2 | 3 | ||||||||
| support_versioning | Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | yes | Properties in 'Host' | 1 | 1 | 2 | 3 | ||||||||
| title | Title | String | 1 | Super Repository | Properties in 'Host' | 1 | 1 | 1 | 2 | 3 | |||||||
| url | The URL of the system hosting a distribution of a dataset | URI | 1 | https://www.fairdata.fi/en/ida/ | Properties in 'Host' | 1 | 1 | 1 | 2 | 3 | |||||||
| Dataset - Distribution - License | |||||||||||||||||
| licence | To list all licenses applied to a specific distribution of data. | Nested Data Structure | 0..n | Properties in 'Distribution' | 1 | 1 | 0 | ||||||||||
| license_ref | Link to license document. | URI | 1 | Dataset-specific - What kind of license is granted for the use of data https://creativecommons.org/licenses/by/4.0/ | Properties in 'Licence' | 1 | 1 | 0 | 3 | ||||||||
| start_date | If date is set in the future, it indicates embargo period.Encoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2026.09.01 | Properties in 'Licence' | 1 | 1 | 0 | 3 | ||||||||
| Dataset - Metadata | |||||||||||||||||
| metadata | To describe metadata standards used. Use community metadata standards where these are in place. Indicate which metadata will be provided to help others identify and discover the data. | Nested Data Structure | 0..n | Indicate which metadata standards (for example DDI, TEI, EML, MARC, CMDI) will be used. | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 45717 | |||||||
| description | Description - Consider how this information will be captured and where it will be recorded (for example in a database with links to each item, a ’readme’ text file, file headers, code books, or lab notebooks). | String | 0..1 | provides taxonomy for... | Properties in 'Metadata' | 1 | 1 | 1 | 2 | 0 | |||||||
| language | Language of the metadata expressed using ISO 639-3 | Term from Controlled Vocabulary | 1 | Properties in 'Metadata' | 1 | 1 | 2 | 0 | |||||||||
| metadata_standard_id | Metadata Standard ID | Nested data structure | 1 | http://www.dublincore.org/specifications/dublin-core/dcmi-terms/ | Properties in 'Metadata' | 1 | 1 | 1 | 0 | ||||||||
| identifier | Identifier for the metadata standard used. | String | 1 | http://www.dublincore.org/specifications/dublin-core/dcmi-terms/ | Properties in 'Metadata' | 1 | 1 | 1 | 0 | ||||||||
| type | Identifier type Allowed Values:url,other | Term from Controlled Vocabulary | 1 | Properties in 'Metadata' | 1 | 1 | 1 | 0 | |||||||||
| access | Can the the documentation be accessed? Allowed Values:yes,no | Term from Controlled Vocabulary | 1 | Properties of FI national added 'Metadata' | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||
| documentation | What does the documentation consist of? | String | 1 | Workflow, variable description, … ? | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||
| format | What is the format of the metadata? | Term from controlled vocabulory | 0..n | Properties in 'Metadata' | 2 | 1 | 1 | 0 | |||||||||
| generated | Is documentation generated automatically? Allowed Values:yes,no | Term from Controlled Vocabulary | 1 | Properties in 'Metadata' | 2 | 2 | 2 | 0 | |||||||||
| location_doc | Where is the documentation? | String/URL | 1 | Properties in 'Metadata' | 2 | 2 | 2 | 0 | |||||||||
| location_metadata | Landing page of metadata | PID | 0..1 | Properties in 'Metadata' | 2 | 2 | 1 | 0 | |||||||||
| open | Is the discovery metadata open? Allowed Values:yes,no | Term from Controlled Vocabulary | 1 | Properties in 'Metadata' | 2 | 2 | 0 | ||||||||||
| publish_methodology | Where the methodology/workflow has been published | String /URL | 0..1 | registration of research? | Properties in 'Metadata' | 2 | 2 | 0 | |||||||||
| purpose | What is the basic purpose of metadata? | String | 0..1 | Qvain, own CRIS, something else? | Properties in 'Metadata' | 2 | 2 | 0 | |||||||||
| schema | Is the data built according to a specific schema? Allowed Values:yes,no | Term from Controlled Vocabulary | 1 | Relates to dataset. Ideally, metadata from existing datasets could be imported directly from e.g. Zenodo. Also, metadata could be brought in for any datasets published in the project. Infoflow might be easiest this way around rather than from DMP API to repository. | Properties in 'Metadata' | 2 | 1 | 0 | |||||||||
| vocabulary_link | Which vocabularies are used? | Term from controlled vocabulory | 1 | Properties in 'Metadata' | 2 | 2 | 0 | ||||||||||
| workflow | Is the workflow described? Allowed Values:yes,no | Term from Controlled Vocabulary | 1 | Especially important in the case of large datasets, from which the data itself cannot be preserved, but is produced again if necessary | Properties in 'Metadata' | 2 | 1 | 0 | |||||||||
| Dataset - Technical resource | #_Nested Data Structure if many technical resources are used from different providers. IDs relate to user id of technical service providers. | ||||||||||||||||
| tecchnical_resource | List 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) | String / Term from Controllod Vocabulory | 0..n | Properties in 'Dataset' | |||||||||||||
| description | To list all technical resources needed. Describe 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). | String | 0..n | The Celestron 44102 Inverted Biological Microscope was used to examine biological samples, such as cells and microorganisms, with high-resolution optics. | Properties in 'Technical_resource' | 1 | 1 | 1 | 3 / 2 (from organisational or national list) | ||||||||
| name | Name a technical resource applied to a dataset | String / Term from Controllod Vocabulory | 1 | Celestron Microscope | Properties in 'Technical_resource' | 1 | 1 | 1 | 1 | ||||||||
| technical_resource_id | Identifier of a technical resource | Nested Data Structure | 0..n | https://urn.fi/urn:nbn:fi:csc-202402000273088 | Properties in 'Technical_resource' | 1 | 3 | ||||||||||
| estimate_datasize | Give a rough estimate of the size of the data produced/collected in TBs | Number | 1 | Estimate for the resources applied for the project | Properties in 'Technical_resource' | 2 | 1 | 1 | 3 | ||||||||
| data_resource_estimate | Project data magnitude for resources required to analyse and store the data | Number | 1 | Estimate for the resources applied for the project | Properties in 'Technical_resource' | 2 | 1 | 2 | 3 | ||||||||
| application_process | What applications are used to process data? Allowed Values from:Controlled list CSC Service Catalogue & organization services | Term from Controlled Vocabulary | 1..n | Affects the choice of storage environment (e.g. whether the video is only available for viewing or whether it needs to be available at the file level in an analysis program) | Properties in 'Technical_resource' | 2 | 1 | 2 | 3 | ||||||||
| computing_environments | Which computing environments are needed for research? Allowed Values from:Controlled list CSC Service Catalogue & organization services | Term from Controlled Vocabulary | 1..n | Relates to data set | Properties in 'Technical_resource' | 2 | 1 | 2 | 3 | ||||||||
| computing_capacity_CPU | How much core hours for computing capacity is required in CPU? | Number | 1 | Estimated value | Properties in 'Technical_resource' | 2 | 2 | 2 | 3 | ||||||||
| computing_capacity_GPU | How much core hours for computing capacity is required in GPU? | Number | 1 | Estimated value | Properties in 'Technical_resource' | 2 | 2 | 2 | 3 | ||||||||
| user_id | User id for utilizing the technical resource | String | 0..n | Properties in 'Technical_resource' | 2 | ||||||||||||
| identifier | Identifier for a user of technical resources | String | 0..n | CSC project | Properties in "User_id" | 2 | 1 | 2 | 3 | ||||||||
| type | Identifier type defined by technical resource provider | String | 0..n | CSC project | Properties in "User_id" | 2 | 1 | 2 | 3 | ||||||||
| project_id | Project identificator for utlizing the resource | String | 0..n | Properties in 'Technical_resource' | |||||||||||||
| identifier | Unique project established for use of technical resource | String | 0..n | CSC project | Properties in 'Project_id' | 2 | 1 | 2 | 3 | ||||||||
| type | Type defined by technical resource provider for project granted resources | String | 0..n | CSC project | Properties in 'Project_id' | 2 | 1 | 2 | 3 | ||||||||
| Contact | |||||||||||||||||
| Contact person for a DMP - - Derived from Contact section | Nested Data Structure | 1..n | 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. | Section in 'DMP' | 1 | 1 | 1 | 2 | |||||||||
| contact_id | Identifier for contact | String | 1 | ORCID of Contact person for a DMP / Principal (responsible) researcher | Properties in 'Contact' | 1 | 1 | 1 | 1 | 1 | |||||||
| identifier | To indicate the specific value of an identifier for a contact | String | 1 | 0000-0000-0000-0000 | Properties in 'Contact_id' | 1 | 1 | 1 | 2 | ||||||||
| type | Identifier type Allowed Values:orcid,isni,openid,other | Term from Controlled Vocabulary | orcid | Properties in 'Contact_id' | 1 | 1 | 1 | 2 | |||||||||
| mbox | E-mail address | String | 1 | from orcid, if possible or manual | Properties in 'Contact' | 1 | 1 | 1 | 1 | 3 | |||||||
| firstnames | First names of the contact person / principal researcher; ((RDA maDMP Standard: Name)) | String | 1 | from orcid or manualNote: In RDA this is not separated into first name and last name; In Finnish data model this is separated | Properties in 'Contact' | 1 | 1 | 1 | 1 | 2 (from ORCID) / 3 | |||||||
| lastname | Last name of the contact person / principal researcher; ((RDA maDMP Standard: Name)) | String | 1 | from orcid or manualNote: In RDA this is not separated into first name and last name; In Finnish data model this is separated | Properties in 'Contact' | 1 | 1 | 1 | 1 | 2 (from ORCID) / 3 | |||||||
| Contributor | |||||||||||||||||
| To list people that play role in data management related to this DMP, e.g. resoponsible for performing actions described in this DMP. | Nested Data Structure | 0..n | ORCIDs, Local user Ids in local solutions. #_Nested Data Structure used if there are many contributors (and data controllers). 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. | Section in 'DMP' | 1 | 1 | 2 | 2 | |||||||||
| affiliation | Affiliations of a contact | Nested Data Structure | 0..n | Some University | Properties in 'Contributor' | 1 | 1 | 1 | 1 | 2 (from ORCID/ROR) / or 3 | |||||||
| affiliation_id | Identifier for an affiliation | String | 1 | https://ror.org/123abcd45 | Properties in 'Affiliation' | 1 | 1 | 1 | 1 | 3 | |||||||
| type | Identifier type Allowed Values: ROR, other | Term from Controlled Vocabulary (ROR, Other) | 1 | ROR | Properties in 'Affiliation' | 1 | 0 | 1 | 2 | 3 | |||||||
| contributor_id | Contributor id e.g. ORCID | Nested data structure | 1..n | Needs to be defined - or where could be derived? From funding decision? | Properties in 'Contributor' | 1 | 1 | 1 | 2 | 2: Digital authentication e.g. by e-mail Contributor will add their ORCID or from Funding application 3: Has risk of errors for ORCID | |||||||
| identifier | Term from Controlled Vocabulary | String | 1 | 0000-0000-0000-0000 | Properties in 'Contributor_id' | 1 | 1 | 1 | 2 | 3 | |||||||
| type | Identifier type Allowed Values:orcid,isni,openid,other | Term from Controlled Vocabulary | orcid | Properties in 'Contributor_id' | 1 | 1 | 1 | 2 | 3 | ||||||||
| mbox | E-mail address | String | 0..n | Properties in 'Contributor' | 1 | 0 | 1 | 2 | 2 / 3 (depending if person has allowed sharing) | ||||||||
| firstname | First name of the contact person / principal researcher; | String | 1 | from orcid or manualIn RDA this is not separated into first name and last name - Do we need the separate fields in Finland? | Properties in 'Contributor' | 1 | 0 | 1 | 1 | 2 (from ORCID) / 3 | |||||||
| lastname | Last name of the contact person / principal researcher; | String | 1 | from orcid or manualIn RDA this is not separated into first name and last name - Do we need the separate fields in Finland? | Properties in 'Contributor' | 1 | 0 | 1 | 1 | 2 (from ORCID) / 3 | |||||||
| role | Role of the contributor: Allowed Values: Access controller (Rights holder), Data manager, Principle investigator (Project leader), Work package leader, Creator of data set (Data collector), Publisher of data set, Curator of data set (Data curator), Contributor of data set, Responsible of DMP, Other (Need to check national level requirements) | Term from Controlled Vocabulary contributor types of DataCite Metadata Schema. | 1..n | Data controller is required for research data services Use case for AI search from funding proposal by roles | Properties in 'Contributor' | 1 | 1 | 1 | 1 (only if PI, Researcher or Data management) | 2 / 3 | |||||||
| related_identifier | To provide references to related resources, such as projects, programmes, consortiums, that are associated with the research this DMP describes. This helps to establish connections between different research projects and enhances the context of the research. | Nested Data Structure | 0..n | Properties in 'DMP Generic information' | 2 | 0 | 0 | 1 | 0 | ||||||||
| identifier | Value of the identifier | String | 1 | https://example.com/ | Properties in 'Related_identifier' | 2 | 0 | 0 | 1 | 0 | |||||||
| type | Type of the identifier, ROR, Grant decision, Consortium agreement | String | 1 | Research consortium agreement for … | Properties in 'Related_identifier' | 2 | 0 | 0 | 1 | 0 | |||||||
| Cost | |||||||||||||||||
| To 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. (Sum from costs given in cost section). Explain how the necessary resources (for example time) to prepare the data for sharing/ preservation (data curation) have been costed in. Carefully consider and justify any resources needed to deliver the data. These may include storage costs, hardware, staff time, costs of preparing data for deposit, and repository charges. | Nested Data Structure | 0..n | Provides a list of costs related to data management. | Section in 'DMP' | 1 | 1 | 1 | 0 | 2 | ||||||||
| currency_code | Currency of costs Allowed Values defined by ISO 4217. Note: Default is EUR or could this be linked to Funder_Id? | Term from Controlled Vocabulory | 0..1 | "978" for eur | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id) | |||||||
| description_cost | Description of costsNote: Could this be linked to Grant ID for description of applied/granted budget? | String | 0..1 | from Grant id when funded | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||
| title_cost | Title of costsNote: Could this be linked to Grant ID for title of applied/granted budget? | String | 1 | from Grant id when funded | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||
| value_cost | Value of costsNote1: Could this be linked to Grant ID for applied/granted budget?Note2: Link with DMP / cost_dmp | Number | 0..1 | from Grant id when funded | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||
| DMP Generic | 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. | ||||||||||||||||
| alternate_identifier | To provide alternative or secondary identifiers for a DMP, which can be used to reference or cite the dataset in different contexts or systems. Alternative identifiers can include other PIDs from DMP storage systems, internal database IDs, or other unique codes assigned to the DMP by various organizations or services. | Nested Data Structure | 0..n | Properties in 'DMP Generic information' | 1 | 2 | 2 | ||||||||||
| created | Date and time of first version of a DMPEncoded using the relevant ISO 8601 Date and Time compliant string (System coded) | DateTime | 1 | 2025-05-28 System recorded | Properties in 'DMP Generic information' | 1 | 1 | 0 | 1 (system) | ||||||||
| description | Any text related to this DMP, optionally describing the project. It can include important information that doesn't fit elsewhere. | String | 0..1 | This DMP is for our new project - Check if this comes from Tiede & tutkimus porttaali | Properties in 'DMP Generic information' | 1 | 2 | ||||||||||
| dmp_id | Identifier for the DMP itself | Nested Data Structure | 1 | Request id for DMP Where does this originate from, especially if using different tools/systems for DMPs? | Properties in 'DMP Generic information' | 1 | 1 | 1 | 1 | ||||||||
| identifier | Identifier for a DMP | String | 1 | For some research DMP may have to be closed by a justified reason, otherwise public | Properties in 'DMP_id' | 1 | 1 | 3 | |||||||||
| type | Identifier type | Term from Controlled Vocabulary | 1 | doiFor some research DMP may have to be closed by a justified reason, otherwise public Allowed Values:handle,doi,ark,url,other | Properties in 'DMP_id' | 1 | 1 | 3 | |||||||||
| modified | Must be set each time DMP is modified. Indicates DMP version. Encoded using the relevant ISO 8601 Date and Time compliant string (System coded) | DateTime | 1 | 2025-05-28 System recorded | Properties in 'DMP Generic information' | 1 | 1 | 1 | 0 | 1 (system) | |||||||
| related_identifier | To provide references to related resources, such as publications, datasets or software, that are associated with the dataset. This helps to establish connections between different research outputs and enhances the discoverability and context of the dataset. | Nested Data Structure | 0..n | Properties in 'DMP Generic information' | 1 | ||||||||||||
| identifier | Value of the identifier | String | 1 | https://example.com/ | Properties in 'Related_identifier' | 1 | |||||||||||
| metadata_scheme | Name of the related metadata schema (if applicable) | String | 0..1 | DDI-L | Properties in 'Related_identifier' | 1 | |||||||||||
| relation_type | Type of relation between the resource and the related resource, suggested values from DataCite relationType | String | 1 | HasMetadata | Properties in 'Related_identifier' | 1 | |||||||||||
| resource_type | Type of the related resource, suggested values from DataCiteresourceTypeGeneral | String | 0..1 | Model | Properties in 'Related_identifier' | 1 | |||||||||||
| scheme_type | Type of the related metadata scheme linked with scheme URI (if applicable) | String | 0..1 | XSD | Properties in 'Related_identifier' | 1 | |||||||||||
| scheme_uri | Link to the scheme of the identifier (if applicable) | URI | 0..1 | http://www.ddialliance.org/Specification/DDI-Lifecycle/3.1/XMLSchema/instance.xsd | Properties in 'Related_identifier' | 1 | |||||||||||
| type | Type of the identifier, suggested values from DataCite relatedIdentifierType | String | 1 | url | Properties in 'Related_identifier' | 1 | |||||||||||
| title | Title of a DMP | String | 1 | Max 100 char | Properties in 'DMP Generic information' | 1 | 1 | 1 | 1 | 1 | 3 | ||||||
| next_review | Next review date to update DMPEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 0..1 | Research project benefits of timing the update of DMP, and Data Support can better plan the assistance. Suggested to be added for making dmp alive and updated e.g. for reporting purposes | Properties in 'DMP Generic information' | 2 | 0 | 0 | 2 | 0 | 1 | 2 / 3 | |||||
| type | A description on what kind of DMP to do | Term from Controlled vocabulary | 1 | Type of DMP:Student, Academic organization own template, Academic national template,National generic,EU Horizon,RDA / International, Input formula should be later updated or extended to a richer format. Input profiles: for example: (Define national typology for recommended use of DMPs (light, detailed), key issues personal data, confidentiality of information, resource intensity, number of actors (outsiders)) | Properties in 'DMP Generic information' | 2 | 0 | 0 | 2 | 0 | 1 | 3 | |||||
| version | Version of DMP | Number | 1 | automatic versioning / descriptiom | Properties in 'DMP Generic information' | 1 | |||||||||||
| Project | |||||||||||||||||
| To list all project(s) for which the data and work are described in this DMP | Nested Data Structure | 0..n | Section in 'DMP' | 1 | 1 | ||||||||||||
| description | Project short description | String | 1 | Example:This 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. | Properties in 'Project' | 1 | 1 | 1 | 1 | 1 (project_id links to long description) otherwise 3 | |||||||
| end | Project end dateEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 0..1 | 2028-12-31; If DMP is used for continuous process no end date is required, but this needs to be specified in description. Alternatively end date can be used to the end of funding period of long-term-plans. | Properties in 'Project' | 1 | 0 | 1 | 1 | 3 (Can trigger update process & reporting stage) | |||||||
| field_of_science | Scientific discipline of project. Recommended to use the UNESCO science classification | Term from Controlled Vocabulary | 0..n | 3 if need to be added by researcher 2 if Analytics / AI can be used to suggest based on ORCID, Project_ID or Description to identify UNESCO science classification. Keywords and freeword allow mapping to ontologies and hence smart searches (whereas controlled vocabularies and taxonomies tend force users to use whatever is close if there is no appropriate term available) UNESCO science classificationpore-in via main categories | Properties in 'Project' | 2 | 0 | 1 | 1 | 2 / 3 | |||||||
| project_id | Project identifier | Nested Data Structure | 1 | Compare also with RAiD: https://raid.org/ | Properties in 'Project' | 1 | 1 | 1 | 2 | 2 | |||||||
| indentifier | To indicate the specific value of an identifier for a project | String | 1 | https://example.org/project | Properties in 'Project_id' | 1 | 1 | ||||||||||
| type | To specify a type of an identifier for a project. Suggested Values: doi, raid, url | String | 1 | url | Properties in 'Project_id' | 1 | 1 | ||||||||||
| title | Name/Title of the project | String | 1 | If project information is not yet available anywhere, how much should be produced here? Is it possible to have multiple DMPs for one project or a maDMP without a funder or project? | Properties in 'Project' | 1 | 1 | 1 | 1 | 3 | |||||||
| start | Project start dateEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2026-01-01Encoded using relevant ISO Date and time compliant string | Properties in 'Project' | 1 | 0 | 1 | 1 | 3 (Can trigger update process e.g. after 3-6 months after start) | |||||||
| Project - Funding | #_Nested Data Structure if many funding sources for a large research program unless defined that DMP relates to single grant decision | ||||||||||||||||
| funding | Funding related with a project | Nested Data Structure | 0..n | Public after publishing the grant. | Properties in 'Project' | 1 | 1 | 1 | 1 | 2 (Derived from Funding status & Grant_id) | |||||||
| funder_id | Funder ID of the associated project, ROR if available | String | 1 | Registry number of associated project Y-tunnus / Business ID Nested structure used if there are many of these. Field is empty if none. From TTV | Properties in 'Funding' | 1 | 1 | 1 | 1 | 2: ROR API via search option3 | |||||||
| identifier | Funder ID, recommended to use CrossRef Funder Registry. See: https://www.crossref.org/services/funder-registry/ | String | 1 | 501100002428 | Properties in 'Funder_id' | 1 | 1 | 1 | 1 | ||||||||
| type | Identifier type Allowed Values:fundref,url,other | Term from Controlled Vocabulary | 1 | fundref | Properties in 'Funder_id' | 1 | 1 | 1 | 0 | ||||||||
| funding_status | To express different phases of project lifecycle. Allowed Values:planned,applied,granted,rejected | Term from Controlled Vocabulory | 0..1 | from Funding idmaDMP use case: automatically derived information from grant ID the project is applied/granted | Properties in 'Funding' | 1 | 1 | 1 | 0 | 3 | |||||||
| grant_id | Grant ID of the associated project | Nested data structure | 0..1 | 654321 | Properties in 'Funding' | 1 | 1 | 1 | 1 | 2 if DOI (not currently)3 | |||||||
| identifier | Grant ID | String | 1 | http://example.com/grants/776242 | Properties in 'Funder_id' | 1 | 1 | 1 | 1 | ||||||||
| type | Identifier type Allowed Values:url,other | Term from Controlled Vocabulary | 1 | url | Properties in 'Funder_id' | 1 | 1 | 1 | 0 | ||||||||
| decision_expected | Expected date for funding decisionEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2026-06-12 | Properties in 'Funding' | 2 | 0 | 2 | 0 | 2: select funding 3 | |||||||
| end | Funding (Project) endEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2028-12-31Used if funding period is different from project.end date | Properties in 'Funding' | 2 | 0 | 2 | 0 | 2 | |||||||
| funder | Name of the funding organization, official name of the funder as given in their registry or their website | String | 1 | Research Council of Finland | Properties in 'Funding' | 2 | 0 | 1 | 0 | 2 | |||||||
| start | Funding (Project) startEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2027-01-01Used if funding period is different from project.start date | Properties in 'Funding' | 2 | 0 | 2 | 0 | 2 | |||||||
| submission_dl | Deadline for funding submissionEncoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2026-08-31 | Properties in 'Funding' | 2 | 0 | 2 | 0 | 2: select funding3 | |||||||
| Project - Security, Privacy, Rights and Ethics | |||||||||||||||||
| security_privacy | To list all issues and requirements related to security and privacy,including which institutional data protection policies are in place. | String | 0..1 | Max 2000 char. Summary of issues | Properties in 'Project' | 1 | 1 | 1 | 0 | 3 (from organisational list) | |||||||
| description | Describe a security and privacy measure applied to a dataset to protect sensitive information | String | 0..1 | Example: "Server with data must be kept in a locked room" | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 0 | 3 | ||||||||
| id | ID of risk assessment | URI/PID | 0..1 | The 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. | Properties in 'Security_privacy_rights_ethics' | 2 | 2 | 0 | 2 | ||||||||
| title | Title of security measures | String | 1 | Example: "Anonymization of Personally Identifiable Data"; "Physical access control" | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 0 | 3 | ||||||||
| ethical_issues_description | To 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. Consider whether ethical issues canaffect how data are stored and transferred, who can see or use them, and how long they are kept. Demonstrate awareness of these aspects and respective planning. | String | 0..1 | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 1 | 0 | 3 | ||||||||
| ethical_issues_exist | To indicate whether there are ethical issues related to data that this DMP describes. Allowed Values:yes,no,unknown | Term from Controlled vocabulary | 1 | This is an important trigger because then the DMP must be very good Allowed Values:yes,no,unknown | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 1 | 0 | 3 | |||||||
| ethical_issues_report | To indicate where a report/document that details all identified ethical issues (might be for example emit from a meeting with an ethical committee). Follow the national and international codes of conducts and institutional ethical guidelines, and check if ethical review (for example by an ethics committee) is required for data collection in the research project. | URL | 0..1 | Add linkComment: Date when the decision was made | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 1 | 0 | 3 | |||||||
| agreements | What other agreements are needed? | String | 0..n | Disclosure agreement with project partners | Properties in 'Security_privacy_rights_ethics' | 2 | 2 | 0 | 1 | 3 | |||||||
| agreements_data_right | What agreements are needed with other organisations and people related to the rights to the material? Give both the type and name of the agreement. | String | 0..n | Data right agreement with data provider, e.g. with Findata. Agreement for utilising technical devices, and external research laboratory. | Properties in 'Security_privacy_rights_ethics' | 2 | 2 | 0 | 3 | ||||||||
| data_use_region | Will data be managed In Europe, Outside Europe | String | 0..n | yes, South-America | Properties in 'Security_privacy_rights_ethics' | 2 | 1 | 0 | |||||||||
| ipr_copyright | Is there IPR or copyright issues in research described in a DMP | Term from Controlled Vocabulary | 0..1 | yes, no, unknown | Properties in 'Security_privacy_rights_ethics' | 2 | 1 | 0 | 3 | ||||||||
| ownership_data_right_organization | Which organization owns the data/ rights related to the data? Give ROR if available, otherwise name of the official name of the organization as given in their website | String | 1 | ROR - add source list here | Properties in 'Security_privacy_rights_ethics' | 2 | 1 | 0 | 3 | ||||||||
| ownership_data_right_person | Who owns the data/rights related to the data? Give ORCID, if available otherwise give name surname first name | String | 0..n | Person or organization? Dataset-specific? The organisation can be a research organisation, a customer organisation or an organisation that otherwise only owns the data (e.g. an archive) | Properties in 'Security_privacy_rights_ethics' | 2 | 1 | 0 | 3 | ||||||||
| research_permit | Rights related to data: Whether permission is required to collect data in research dataset | Term from Controlled vocabulary | 1 | Actual research permit | Properties in 'Security_privacy_rights_ethics' | 2 | 1 | 0 | 3 | ||||||||
| Project - Security & privacy & ethics - DPIA process | |||||||||||||||||
| dpia | To whether DPIA is needed | Boolean | 0..1 | 1 | Properties in 'Security_privacy_rights_ethics' | 1 | 1 | 1 | 0 | ||||||||
| dpia_id | If DPIA exist give URI / DOI | URI | 0..1 | Properties in 'DPIA' Optional addtion | 2 | 1 | 1 | 0 | 3 | ||||||||
| privacy_notice_id | If privacy notice exist give link / archive number | String | 0..1 | Use case maDMP could transfer the number / link of the privacy notice to data protection team when it is been done to indicate the status. | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 | |||||||
| pre_dpia | Has risk assessment been filled in?(risk assessment/pre-dpia, selftest if DPIA is needed)yes,no | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 | ||||||||
| personal_data_sp_category | What special categories of personal data do you process | String | 0..1 | Categories of special categories of personal data | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | Requirement comes from the law | |||||||
| ethnic_origin | Do you process data of ethnic origin? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| political_opinions | Do you process data of political opinions? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| religion_philosophical beliefs | Do you process data of religion or philosophical beliefs? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| trade_union_membership | Do you process data of trade_union_membership? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_concerning_health | Do you process data of data_concerning health of individuals? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| sexual_orientation_or_activity | Do you process data of sexual orientation or activity? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| genetic_or_biometric_data | Do you process genetic or biometric data for identifying the persons? Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| other_sp_category | Describe the other special categories of data that you process in the research? | String | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_prosessing_basis | Basis for data processing | String | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_prosessing_sp_category | Basis for processing special categories of personal data | String | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_transfer_outside_EU | Whether personal data is transferred outside the EU Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_transfer_country | To which countries personal data is transferred | String | 0..n | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| data_external_processors | Are there external processors Allowed Values:yes,no,unknown | Term from Controlled Vocabulary | 0..1 | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | ||||||||
| personal_data_minimized | How is the processing of personal data minimized? | String | 0..1 | Anonymization, pseudonymization, removal of direct identifiers | Properties in 'DPIA process' Optional addtion | 2 | 1 | 1 | 0 | 3 / 1 | |||||||