Version 0.9
Date: 2025-12-19
Created: OSTrails FI National pilot #11
Contact: Johanna Laiho-Kauranne, Iida Lehikoinen
Contributors: Tommi Suominen, Hanna Koivula, Olli-Pekka Kotilainen, Data support from Universites and Research organisations in Finland (names will be added)
Description: This metadata profile describes the national reference data model information content and structure for maDMPs. The purpose is to advance machine actionability in DMPs. Part of the information is classified as required, and part as optional. The model builds upon the RDA maDMP standard, OSTrails Commons, Horizon Europe DMP criteria, and national guidance for DMPs implemented by the Research Council of Finland.
Status: The update of the RDA maDMP standard has been implemented. Cross-checking with the OSTrails Commons, and the DMP national guidelines is currently coded into the metadata profile (based on document linked below "OSTrails NP11 Mapping of maDMPs to national template in Finland".
Related to: RDA maDMP standard; Link: https://github.com/RDA-DMP-Common/RDA-DMP-Common-Standard
Mapping of funder's requirements: OSTrails NP11 Mapping of maDMPs to national template in Finland.pdf
Deviations from the updated RDA maDMP standard:
- alternate_identifier not used, as the identifier can use a nested structure. In addition, it is not purposeful to classify identifiers by its importance (primary, alternative).
- dataset/agent created to include creator, contributor (on dataset level rather than DMP), and other roles
- funding moved under dmp_generic from project
Metadata profile for national reference data model for maDMPs in Finland
| Class | 1. Level | 2 Level | 3 Level | 4 Level | B. Description | C. Data type | D. Cardinality | Example values | Hierarchy | Connection to research.fi datamodel (inventory of codelists used at: Tutkimustietovaranto - koodistot) | 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 | H. Self-funded light DMP | I. Consortium DMP | J. Student DMP | K. 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. |
| |||||||||||||||||
| dataset | To describe data on a general level. Describe how datasets used can be categorized. This follows the definition 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' | https://iri.suomi.fi/model/ttv/Tutkimusaineisto | 1 | 0 | 0 | 1 | 1 | 1 if can be derived from Dataset information otherwise 3 | |||||||
| 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. | rdf:LangString | 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 organized during the project mentioning conventions e.g. how files will be named, version controls used, and folder structures. | rdf:LangString | 0..n | Conventions, version control, and folder structures. | Properties in 'Dataset' | versions are given as PID-to-PID relationships with verbs | 3 | 1 | 1 | 1 | 0 | ||||||||
| dataset_id | Dataset identifier Preferred values: DOI, PID, URN, URL, handle, ark, other digital ID. A trustworthy, long-term repository will provide a persistent identifier. | Nested Data Structure | 1..n | Dataset may not exist when DMP is defined. DMP tool should provide temporary ID before dataset gets PID by some way. | Properties in 'Dataset' | All identifiers are treated equally, no preference given: Association: https://iri.suomi.fi/model/ttv/yksilointitunnus-11 target class: https://iri.suomi.fi/model/ttv/Tunniste attribute for value: https://iri.suomi.fi/model/ttv/pysyvatunniste | 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/54321/10.123456 | Properties in 'Dataset_id' | value: https://iri.suomi.fi/model/ttv/pysyvatunniste | 1 | 1 | 0 | 0 | 0 | 1 | |||||||
| type | To specify a type of an identifier for a dataset. Suggested Values: handle, doi, ark, url | Term from Controlled Vocabulary | 1 | handle | Properties in 'Dataset_id' | Also this is a controlled value set at: | 1 | 1 | 0 | 0 | 0 | 1 | |||||||
| description | Description of dataset. Explain the foreseeable research uses (and/or users) for the data. Human‑readable description of the 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. | rdf:LangString | 1 | This dataset contains systematically collected field measurements, laboratory results, and derived analytical outputs documenting environmental conditions across multiple sampling sites. It includes raw sensor logs, processed summary tables, and contextual metadata describing instruments, calibration routines, and data collection protocols. Description at general level only. Space limitation to be set, e.g. max 2000 char. Review how much description is needed by PI, Organization, Funder. | Properties in 'Dataset' | https://iri.suomi.fi/model/ttv/kuvaus-7 (rdf:langString) | 1 | 1 | 1 | 1 | 1 | 3 | |||||||
| geographical_coverage | Geographical coverage/opacity of the dataset in the form of a description. There may be a point, or range. Issued if it fits the nature of the data. | rdf:LangString | 0..1 | Europe – EU member states as of 2024. | Properties in 'Dataset' | ||||||||||||||
| issued | Date of dataset been issued. Encoded using the relevant ISO 8601 Date compliant string. | DateTime | 0..1 | 2024-10-15 | Properties in 'Dataset' | https://iri.suomi.fi/model/ttv/julkaisupaivamaara (xsd:date) | 1 | 0 | 0 | 1 | 0 | ||||||||
| 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 | ||||||||||
| keyword | Keywords for data that is opened or catalogued | Nested Data Structure | 0..n | Properties in 'Dataset' | Association id: https://iri.suomi.fi/model/ttv/avainsanat-5 in TTV this is a nested structure: name, definition, concept PID/uri (nested structure), vocabulary PID/URI.
| 1 | 0 | 0 | 1 | 0 | 1 / 3 | ||||||||
| name | Internationalized label of the concept, can also be a plain string if more machine actionable content is not available | rdf:LangString | 1..n | Ilmastonmuutokset | Properties in 'keyword' | ||||||||||||||
| definition | Concept definition. If concept URL is provided, this can also be omitted | rdf:LangString | 0..n | Merkittävä pitkän aikavälin muutos globaalissa tai paikallisessa ilmastossa. | Properties in 'keyword' | ||||||||||||||
| vocabulary_reference | Reference to the controlled vocabulary entry associated with the keyword. | Nested Data Structure | 0..n | Properties in 'keyword' | |||||||||||||||
| name | Name of the keyword in controlled vocabulary. | rdf:LangString | Ilmastonmuutokset | Properties in 'vocabulary_referenece' | |||||||||||||||
| description | Description of the keyword in controlled vocabulary. | rdf:LangString | Merkittävä pitkän aikavälin muutos globaalissa tai paikallisessa ilmastossa. | Properties in 'vocabulary_referenece' | |||||||||||||||
| topic | The broader topic or category under which this concept is classified | rdf:LangString | Ympäristönmuutokset | Properties in 'vocabulary_referenece' | |||||||||||||||
| vocabulary_reference_id | Identifier object for the vocabulary concept | Nested Data Structure | 1 | Properties in 'vocabulary_referenece' | target class: https://iri.suomi.fi/model/ttv/Tunniste | ||||||||||||||
| identifier | To indicate the value of an identifier (identifier string) | String | 1 | Properties in 'vocabulary_referenece_id' | attribute for value: https://iri.suomi.fi/model/ttv/pysyvatunniste | ||||||||||||||
| type | The identifier type for the concept | Term from Controlled Vocabulary | 1 | URI | Properties in 'vocabulary_referenece_id' | https://iri.suomi.fi/model/ttv/pysyvantunnisteentyyppi Also this value comes from a controlled value set at: | |||||||||||||
| keyword_id | Identifier for the keyword | Nested Data Structure | 0..1 | Properties in 'keyword' | |||||||||||||||
| identifier | To indicate the value of an identifier (identifier string) | String | 1 | Properties in 'keyword_id' | |||||||||||||||
| type | The identifier type for the concept | Term from Controlled Vocabulary | 1 | URI | Properties in 'keyword_id' | ||||||||||||||
| language | Language of the dataset expressed using ISO 639-3 | Term from Controlled Vocabulary | 0..n | fin | Properties in 'Dataset' | https://iri.suomi.fi/model/ttv/kielitunniste-1 uses controlled vocabulary at: http://uri.suomi.fi/codelist/research/languages (this is a custom codelist that merges ISO 639-1 with some codes from 639-5 + plus a few custom entries. | 1 | 1 | 1 | 1 | 0 | 1 / 3 | |||||||
| methodology | To describe methodology, procedures, workflows, etc. on how the dataset is created | Nested Data Structure | 0..n | Properties in 'Dataset' | n.a. | 3 | 1 | 1 | 2 | 2 | |||||||||
| description | To describe methodology, procedures, workflows, definitions of variables, units of measurement, at general level. | rdf:LangString | 1 | Data were collected through an online survey using a structured questionnaire distributed to Finnish universities and research institutes between June and August 2024. | Properties in 'methodology' | ||||||||||||||
| (siirretään parempaan kohtaan) | data_dictionary | Description outlining the structure, content, and variable definitions for a dataset or collection of data. (IRI: https://terms.codata.org/rdmt/data-dictionary ) | n.a. | ||||||||||||||||
| personal_data | To indicate whether the dataset contains personal data Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 1 | Yes 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' | n.a. | 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. | rdf:LangString | 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. | Properties in 'Dataset' | n.a. | 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. Explanation on impact of GDPR, Database Directive, sui generis etc. rights on data management | rdf:LangString | 0..n | This dataset contains personal data collected under informed consent and is processed in compliance with GDPR. Personal data are pseudonymized; access is restricted and governed by a Data Processing Agreement. Intellectual property rights remain with the research organization; data are shared under CC BY 4.0 for non-personal components. | Properties in 'Dataset' | License code is given, but his can be addressed in the License section. | 1 | 1 | 2 | 0 | |||||||||
| provenance | Describe the people, institutions, entities, and activities involved in producing, influencing, or delivering a piece of data. In particular, the provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. | rdf:LangString | 0..n | The dataset was generated through a combination of automated sensor recordings, manual field observations, and laboratory analyses. Each data file includes embedded timestamps, instrument identifiers, and processing logs documenting transformations such as cleaning, normalization, and quality assurance steps. | Properties in 'Dataset' | ||||||||||||||
| 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 | ||||||||||||||
| 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 resourceu Suggested values: DataCite relationType https://datacite-metadata-schema.readthedocs.io/en/4.5/appendices/appendix-1/relationType/ | Term from Controlled Vocabulary | 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: https://datacite-metadata-schema.readthedocs.io/en/4.5/appendices/appendix-1/relatedIdentifierType/ | Term from Controlled Vocabulary | 1 | URL Controlled vocabulary: http://uri.suomi.fi/codelist/research/PID | Properties in 'Related_identifier' | 1 | |||||||||||||
| rights | A statement that concerns all rights not addressed with license, such as copyright statements | rdf:LangString | 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' | n.a. duplication with property rights statement? | 1 | ||||||||||||
| sensitive_data | To indicate 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 | Yes 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' | n.a. | 1 | 1 | 1 | 1 | 3 | ||||||||
| title | Data set title / name | rdf:LangString | 1 | Fast Car Images | Properties in 'Dataset' | https://iri.suomi.fi/model/ttv/nimi-3 (rdf:langString) | 1 | 1 | 1 | 1/3 | |||||||||
| type | Data set type (indication interview, questionnaire, photos, video, measurement, samples, simulation, code) 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.pdf http://vocabularies.coar-repositories.org/pubby/resource_type.html | Term from Controlled Vocabulary | 0..1 | Questionnaire | Properties in 'Dataset' | n.a. | 1 | 1 | 1 | 0 | 2 / 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 specific other guidance. | Term from Controlled Vocabulary | 0..1 | Magnetism | Properties in 'Dataset' | https://iri.suomi.fi/model/ttv/tieteenala-1 the values are given in controlled vocabulary: http://uri.suomi.fi/codelist/research/Tieteenala2010 (Convertable to "Revised Field of Science and Technology (FOS) Classification in the Frascati Manual. OECD, DSTI/EAS/STP/NESTI(2006)19/FINAL".) | 2 | 1 | 1 | ||||||||||
| data_landing_page | Link / PID to landing page of data | String | 0..1 | https://example.com/ | Properties in 'Dataset' | 2 | 1 | 0 | 3 | ||||||||||
| data_sharing_issues | To indicate how legal and ethical issues related to the sharing of data (e.g. ownership, copyright, sensitivity) will be resolved | rdf:LangString | 1 | Data cannot be openly shared due to the presence of personal information and confidentiality agreements with participating institutions. Anonymized summary data will be published, while full access requires a Data Access Agreement and ethical approval. | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_sharing_contracts | To indicate whether contracts are needed prior to sharing data. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 1 | Yes | Properties in 'data_sharing_issues' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_sharing_ownership | To indicate whether the ownership of data is clear for data sharing. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 1 | No | Properties in 'data_sharing_issues' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_sharing_copyright | To indicate whether the copyright issues are clear related to data sharing. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 1 | No | Properties in 'data_sharing_issues' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_sharing_sensitivity | To indicate whether possible issues related to sharing sensitive data are cleared. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 1 | No | Properties in 'data_sharing_issues' | 2 | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_sharing_other | Describe any emerging other issues of data sharing | rdf:LangString | 0..1 | Data can only be shared after approval from the project’s steering committee. | Properties in 'data_sharing_issues' | 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 | csv | Properties in 'Dataset' | 2 | 1 | 1 | 1 | 0 | 2 | ||||||||
| format_justification | To justify the use of certain formats of datasets | rdf:LangString | 0..1 | Data are provided in CSV format because it is widely supported, human-readable, and easily processed by most statistical and programming tools. CSV ensures interoperability across platforms and long-term accessibility without requiring proprietary software. | Properties in 'Dataset' | ||||||||||||||
| 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_support_description | To indicate whether potential users need specific tools to access and (re-)use the data. To consider the sustainability of software needed for accessing the data. To indicate whether data will be shared via a repository, requests handled directly, or whether another mechanism will be used. To indicate whether additional resource will be needed to prepare data for deposit or to meet any charges from data repositories. | rdf:LangString | 0..n | Dataset includes detailed variable descriptions, provenance information, and links to related publications. Support for reuse is enhanced through standardized formats (CSV, JSON) and open licensing (CC BY 4.0). | Properties in 'Dataset' | 2 | 1 | 1 | 2 | 1 | |||||||||
| source | Data source | String | 1 | Relates to one data set, can include ready-made options, but also an open text field | Properties in 'Dataset' | 2 | 1 | 0 | 2 / 3 | ||||||||||
| utilize | Research infrastructure utilized for dataset | rdf:LangString | 0..n | University laboratory facilities for sample preparation and analysis. | Properties in 'Dataset' | ||||||||||||||
| version | Version of the dataset | String | 1 | 8.0 | Properties in 'Dataset' | ||||||||||||||
| Dataset - Dataset Lifecycle | This is extension linked to Dataset - National addition in maDMP reference data model in Finland | DMP information not relevant to TTV use cases: n.a. perhaps Metax might have some info | |||||||||||||||||
| data_lifecycle | Describe at general level data lifecycle, and how open science criteria will be applied. | Nested Data Structure | 0..1 | 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 | 2024-10-15T14:30:00Z 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 | Fairdata IDA | 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 | No | 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? | rdf:LangString | 1 | Snapshots of the distribution are archived monthly in IDA for long-term preservation. 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. | rdf:LangString | 1 | The dataset will be closed after the project ends because it contains sensitive personal data that cannot be anonymized further. Continued access would violate GDPR and institutional data protection policies. No long-term reuse is planned, and destruction is required by the consent agreements. 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_audience | To state for whom this dataset can be relevant | rdf:LangString | 0..n | Researchers in environmental sciences, policy makers working on climate adaptation, and data analysts in sustainability projects. | Properties in 'Dataset lifecycle' | ||||||||||||||
| data_collected | Provide an overview of the data included in this dataset. | rdf:LangString | 0..n | Raw sensor readings collected during field study | Properties in 'Dataset lifecycle' | 2 | 1 | 0 | 3 | ||||||||||
| data_retention | Indicate the retention period and any policies for data disposal or archiving. | rdf:LangString | 1 | The dataset will be retained for 5 years after project completion to allow for auditing and potential follow-up research. After this period, all files will be securely deleted in accordance with institutional data management policies. 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 | rdf:LangString | 0..n | Machine learning model predictions based on training data from 2023. | 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 people, To other projects, To service providers, Complex structure | Term from Controlled Vocabulary | 0..n | In DMP defined research consortium 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? | rdf:LangString | 1 | Data will be deleted 24 months after project completion using GDPR-compliant procedures. 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 | 2040-12-12T12:00:00Z 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. | rdf:LangString | 0..1 | Data will not be deleted because it serves as a long-term reference for future research and compliance with open science principles. It will be archived permanently in a secure institutional repository. | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | ||||||||||
| deletion_planned_timing | If date cannot be given, then description of the planned deletion stage and approximate timing | rdf:LangString | 0..1 | Deletion planned after two year mandatory retention period | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | 3 | ||||||||||
| description | Summarized description of the lifecycle of the dataset. 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. | rdf:LangString | 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 data will be preserved for long-term use after project completion. Organization and service provider needs this information, especially for large datasets | 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? | rdf:LangString | 1 | Compute resources will be shut down and temporary storage wiped. Final data and metadata will be archived in Fairdata IDA with a DOI for at least 10 years. 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 | Nested Data Structure | 1..n | Properties in 'Dataset lifecycle' | 2 | 1 | 2 | Special requirements for data repositories for preliminary data? | |||||||||||
| repository | Repository where data is planned to be opened | String | 1 | Zenodo | Properties in 'open_location' | ||||||||||||||
| id | Define by whom is the data opened | Nested Data Structure | 0..1 | Properties in 'open_location' | |||||||||||||||
| identifier | To indicate the value of an identifier (identifier string) | String | 1 | s0000-0000-0000-0000 | Properties in 'id' | ||||||||||||||
| type | The identifier type for the concept | Term from Controlled Vocabulary | 1 | orcid | Properties in 'id' | ||||||||||||||
| sharing_solution | How the data will be shared during the project? Define technical solutions planned to be used? | Term from Controlled Vocabulary | 1..n | Allas Choose from Service catalog | 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 | 5 | 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? | String | 1..n | https://urn.fi/urn:nbn:fi:csc-10000000100000 Relates to a dataset, extra-important if data subject to the Act on the Secondary Use of Data Add to general data life-cycle Specify by data set if needed | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 1 | 3 | |||||||||
| version_mgmt | How the data versions are managed? | rdf:LangString | 1 | Data versions will be managed using Git with semantic versioning (v1.0, v1.1). All changes tracked in a private GitLab repository. Mandatory for large data intensive projects (At CSC >50 TB) | Properties in 'Dataset lifecycle' | 2 | 1 | 1 | 3 | ||||||||||
| Dataset - AGENT - Creator/Curator/Contributor | This is extension linked to Dataset - National addition in maDMP reference data model in Finland | TTV and metax do this diffrently:
| |||||||||||||||||
| agent | To specify the creators, curators and contributors 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 | 0..n | Properties in 'Dataset' | see above | 1 | 1 | 1 | 0 | ||||||||||
| role | Role of the agent. Allowed values: Creator, Curator, Contributor, Publisher, Rights holder | Term from Controlled Vocabulary | 0..n | Creator | Properties in 'Agent' | ||||||||||||||
| affiliation_id | Identifier for an affiliation. Multiple affiliations are allowed for agents. | Nested Data Structure | 0..n | Properties in 'Agent' | 1 | 1 | 1 | 1 | 2 | ||||||||||
| identifier | To indicate the specific value of an identifier for a affiliation | String | 1 | Properties in 'Affiliation_id' | 1 | 1 | 0 | 1/3 | |||||||||||
| type | To specify a type of an identifier for a affiliation Suggested Values from Codelist | Term from Controlled Vocabulary | 1 | ROR | Properties in 'Affiliation_id' | 1 | 1 | 0 | 1/3 | ||||||||||
| organization_id | Identifier for an organization | Nested Data Structure | 1..n | Properties in 'Agent' | 1 | ||||||||||||||
| identifier | To indicate the specific value of an identifier for an organization | String | 1 | ror.org/12abcde345 | Properties in 'Organization_id' | 1 | |||||||||||||
| type | To specify a type of an identifier for an organization. Suggested Values from Codelist | Term from Controlled Vocabulary | 1 | ROR | Properties in 'Organization_id' | 1 | |||||||||||||
| researcher_id | Identifier for a researcher | Nested Data Structure | 1..n | Properties in 'Agent' | 1 | 1 | 0 | 2 | |||||||||||
| identifier | To indicate the specific value of an identifier for a creator | String | 1 | s0000-0000-0000-0000 | Properties in 'Researcher_id' | 1 | 1 | 0 | 1/3 | ||||||||||
| type | To specify a type of an identifier for a researcher. Suggested Values from Codelist | Term from Controlled Vocabulary | 1 | ORCID | Properties in 'Researcher_id' | 1 | 1 | 0 | 1/3 | ||||||||||
| E-mail of the agent | String | 1 | pouta.paivanen@someuni.fi | Properties in 'Agent' | 1 | 1 | 1 | 0 | 1/3 | ||||||||||
| name | Name of the agent | Nested Data Structure | 1 | Properties in 'Agent' | 1 | 1 | 1 | 1 | 1 (from ORCID/ROR) / or 3 | ||||||||||
| firstname | First name | String | 1 | Pouta | Properties in 'Name' | ||||||||||||||
| lastname | Last name | String | 1 | Päivänen | Properties in 'Name' | ||||||||||||||
| 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 | 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 | String | 0..1 | Properties in 'Distribution' | n.a. ttv - maybe in metax | 1 | 1 | 0 | 3 | ||||||||||
| url_available_until | Indicates how long this distribution will be/ should be available. Encoded using the relevant ISO 8601 Date and Time compliant string | DateTime | 0..1 | 2030-12-12T23:59:59Z | Properties in 'Distribution' | n.a. ttv - maybe in metax | 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 | M Note: Important as it affects what tools are available. | Properties in 'Distribution' | n.a. ttv - maybe in metax | 1 | 1 | 1 | 0 | 3 | ||||||||
| data_access | Indicates current access mode for data and data sharing. Allowed Values: Open, Shared (embargo, requires login, requires permission), Closed | Term from Controlled Vocabulary | 1 | Open | Properties in 'Distribution' | Defined in: https://iri.suomi.fi/model/ttv/saatavuusluokka which uses the controlled Vocabulary: https://koodistot.suomi.fi/codescheme;registryCode=fairdata;schemeCode=access_type | 1 | 1 | 1 | 0 | 3 | ||||||||
| description | Explain how the data will be discoverable and shared. 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. | rdf:LangString | 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. | 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. | String | 0..1 | example.com | Properties in 'Distribution' | Why?? There is the PID for that? (In ttv PID types - url is also a PID type) | 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/Term from Controlled Vocabulary | 0..n | text/csv | 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). | DateTime | 0..1 | 2025-12-31T14:27:37.123+02:00 | Properties in 'Distribution' | https://iri.suomi.fi/model/ttv/ajallinenkattavuus-alkupaivamaara | 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). | DateTime | 0..1 | 2026-01-15T09:05:02:987-05:00 | Properties in 'Distribution' | https://iri.suomi.fi/model/ttv/ajallinenkattavuus-loppupaivamaara | 2 | 1 | 0 | 1/3 | |||||||||
| publisher_id | 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' | NOTE! this is another instance of using the reified structure (see curator, creator) | 2 | 1 | 0 | 3 | ||||||||||
| identifier | To indicate the specific value of an identifier for publisher | String | 1 | s0000-0000-0000-0000 | Properties in 'publisher_id' | ||||||||||||||
| type | To specify a type of an identifier. | Term from Controlled Vocabulary | 1 | orcid | Properties in 'publisher_id' | ||||||||||||||
| research_infrastructure | Name of the used research infrastructure | rdf:LangString | 0..n | Puhti supercomputer | Properties in 'Distribution' | https://iri.suomi.fi/model/ttv/hyodyntaa-1 is an association pointing to the class "research Infrastructure with this content (but data structure is is being revised):
| 2 | 1 | 0 | 1/3 | |||||||||
| restriction_grounds | To describe any reason why data cannot be shared openly and/or restrictions. Mandatory if data set is not open | rdf:LangString | 0..n | This distribution contains identifiable voice recordings and cannot be shared openly; access is restricted to approved researchers under a data use agreement. | Properties in 'Distribution' | n.a. ttv - maybe in metax | 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 | 0..1 | 99,5 | Properties in 'Host' | n.a. ttv - maybe in metax | 1 | 1 | 0 | 3 | ||||||||||
| backup_frequency | Describe how often the backup will be performed. | rdf:LangString | 0..1 | weekly | Properties in 'Host' | n.a. ttv - maybe in metax | 1 | 1 | 1 | 0 | 3 | ||||||||
| 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. | rdf:LangString | 0..1 | cloud replication | Properties in 'Host' | n.a. ttv - maybe in metax | 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' | n.a. ttv - maybe in metax | 1 | 1 | 0 | 3 | |||||||||
| data_recovery_explanation | To explain how the data will be recovered in the event of an incident. | rdf:LangString | 0..n | The repository maintains daily backups and geo-redundant replication; in case of data loss the files can be restored from the latest snapshot within 24 hours. Integrity is verified after restoration. | Properties in 'Host' | n.a. ttv - maybe in metax | 3 | 1 | 2 | ||||||||||
| description | Description of the host | rdf:LangString | 0..1 | Use of robust host X, with managed storage with automatic backup, provided by IT support services of the home institution. | Properties in 'Host' | https://iri.suomi.fi/model/ttv/kuvaus-10 | 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' | n.a. ttv - maybe in metax | 1 | 1 | 0 | 3 | |||||||||
| host_id | Identifier of Host. | Nested data structure | 0..n | Properties in 'Host' | target class: https://iri.suomi.fi/model/ttv/Tunniste | 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' | attribute for value: https://iri.suomi.fi/model/ttv/pysyvatunniste | 1 | 1 | 2 | ||||||||||
| type | To specify a type of an identifier for a host. Suggested Values: url | Term from Controlled Vocabulary | 1 | url | Properties in 'Host_id' | https://iri.suomi.fi/model/ttv/pysyvantunnisteentyyppi Also this value comes from a controlled value set at: | 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' | n.a. ttv - maybe in metax | 1 | 1 | 2 | 3 | |||||||||
| storage_type | The type of storage required | String | 0..1 | LTO-8 tape | Properties in 'Host' | n.a. ttv - maybe in metax | 1 | 1 | 2 | 3 | |||||||||
| support_versioning | To indicate whether the host system supports versioning. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | yes | Properties in 'Host' | n.a. ttv - maybe in metax | 1 | 1 | 2 | 3 | |||||||||
| title | Title of the host | rdf:LangString | 1 | Super Repository | Properties in 'Host' | https://iri.suomi.fi/model/ttv/nimi-6 | 1 | 1 | 1 | 2 | 3 | ||||||||
| url | The URL of the system hosting a distribution of a dataset | String | 1 | example.com/host | Properties in 'Host' | 1 | 1 | 1 | 2 | 3 | |||||||||
| Dataset - Distribution - License | only a field in TTV, and relates directly to dataset, not its distribution | ||||||||||||||||||
| licence | To list all licenses applied to a specific distribution of data. | Nested Data Structure | 0..n | Properties in 'Distribution' | https://iri.suomi.fi/model/ttv/lisenssikoodi In TTV this is a reference to a Controlled Vocabulary at: http://uri.suomi.fi/codelist/fairdata/license (from here some metadata on the licence can be retrieved, only name is used in TTV.) | 1 | 1 | 0 | |||||||||||
| license_ref | Link (URI) to license document. | String | 1 | example.com/licence | 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 | DateTime | 1 | 2025-12-31T12:27:37Z | 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 | Properties in 'Dataset' | 1 | 1 | 1 | 1 | 45717 | ||||||||||
| 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). | rdf:LangString | 0..1 | The 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. | Properties in 'Metadata' | 1 | 1 | 1 | 2 | 0 | |||||||||
| language | Language of the metadata expressed using ISO 639-3 | Term from Controlled Vocabulary | 1 | eng | Properties in 'Metadata' | In TTV, we handle this field-specifically with the datatype rdf:LangString | 1 | 1 | 2 | 0 | |||||||||
| metadata_standard_id | Identifier of the Metadata Standard | Nested data structure | 1 | Properties in 'Metadata' | 1 | 1 | 1 | 0 | |||||||||||
| identifier | Identifier (string) for the metadata standard. | String | 1 | example.com/metadata-standard | Properties in 'metadata_standard_id' | 1 | 1 | 1 | 0 | ||||||||||
| type | Identifier type Allowed Values: url, other | Term from Controlled Vocabulary | 1 | URL | Properties in 'metadata_standard_id' | 1 | 1 | 1 | 0 | ||||||||||
| access | To indicate whether the documentation can be accessed. | Boolean | 1 | True | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||||
| documentation | To indicate what the documentation consists of. | rdf:LangString | 1 | Workflow, variable description, data collection procedures | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||||
| format | What is the format of the metadata? | Term from controlled vocabulary | 0..n | XML and json | Properties in 'Metadata' | 2 | 1 | 1 | 0 | ||||||||||
| generated | To indicate whether documentation is generated automatically. | Boolean | 1 | True | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||||
| location_doc | Location of the documentation. | String | 1 | example.com/documentation URL | Properties in 'Metadata' | 2 | 2 | 2 | 0 | ||||||||||
| location_metadata | Landing page of metadata (PID) | String | 0..1 | example.com/metadata | Properties in 'Metadata' | 2 | 2 | 1 | 0 | ||||||||||
| open | To indicate whether the discovery metadata is open. | Boolean | 1 | False | Properties in 'Metadata' | 2 | 2 | 0 | |||||||||||
| (Data dictionary mahdollisesti tähän) | publish_methodology | Where the methodology/workflow has been published (URL) | String | 0..1 | example.com/methodology | Properties in 'Metadata' | 2 | 2 | 0 | ||||||||||
| purpose | What is the basic purpose of metadata? | rdf:LangString | 0..1 | The purpose of the metadata is to ensure that the dataset can be accurately discovered, understood, cited, and reused by both internal and external audiences. | Properties in 'Metadata' | 2 | 2 | 0 | |||||||||||
| schema | To indicate whether the data is built according to a specific schema. | Boolean | 1 | True | Properties in 'Metadata' | 2 | 1 | 0 | |||||||||||
| vocabulary_link | Links for used vocabularies | Term from controlled vocabulary | 1..n | example.com/vocabulary | Properties in 'Metadata' | 2 | 2 | 0 | |||||||||||
| workflow | To indicate whether workflow is described. | Boolean | 1 | False 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. | ||||||||||||||||||
| technical_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) | Nested Data Structure | 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). | rdf:LangString | 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 | rdf:LangString or Term from Controlled Vocabulary | 1 | Celestron Microscope | Properties in 'Technical_resource' | 1 | 1 | 1 | 1 | ||||||||||
| technical_resource_id | Identifier of a technical resource | Nested Data Structure | 0..n | Properties in 'Technical_resource' | 1 | 3 | |||||||||||||
| id | Identifier for the technical resource | String | 1 | https://urn.fi/urn:nbn:123456789 | Properties in 'technical_resource_id' | ||||||||||||||
| type | Identifier type | Term from Controlled Vocabulary | 1 | URN | Properties in 'technical_resource_id' | ||||||||||||||
| estimate_datasize | Give a rough estimate of the size of the data produced/collected in TBs | Number | 1 | 1 | 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 | 5 | Properties in 'Technical_resource' | 2 | 1 | 2 | 3 | ||||||||||
| application_process | Applications used to process data. Allowed Values from: Controlled list CSC Service Catalogue & organization services | Term from Controlled Vocabulary | 1..n | Puhti 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 | Computing environments needed for the research. Allowed Values from: Controlled list CSC Service Catalogue & organization services | Term from Controlled Vocabulary | 1..n | Rahti Relates to data set | Properties in 'Technical_resource' | 2 | 1 | 2 | 3 | ||||||||||
| computing_capacity_CPU | Core hours for computing capacity required in CPU. | Number | 1 | 30 | Properties in 'Technical_resource' | 2 | 2 | 2 | 3 | ||||||||||
| computing_capacity_GPU | Core hours for computing capacity required in GPU. | Number | 1 | 10 | Properties in 'Technical_resource' | 2 | 2 | 2 | 3 | ||||||||||
| user_id | User id for utilizing the technical resource | Nested Data Structure | 0..n | Properties in 'Technical_resource' | 2 | ||||||||||||||
| identifier | Identifier for a user of technical resources | String | 1 | 0000-0000-0000-0000 | Properties in "User_id" | 2 | 1 | 2 | 3 | ||||||||||
| type | Identifier type | Term from Controlled Vocabulary | 1 | orcid | Properties in "User_id" | 2 | 1 | 2 | 3 | ||||||||||
| project_id | Project identifier for utilizing the resource | Nested Data Structure | 0..n | Properties in 'Technical_resource' | |||||||||||||||
| identifier | Unique project established for use of technical resource | String | 1 | CSC‑project‑2026‑A123 | Properties in 'Project_id' | 2 | 1 | 2 | 3 | ||||||||||
| type | Type defined by technical resource provider for project granted resources | Term from Controlled Vocabulary | 1 | CSC project | Properties in 'Project_id' | 2 | 1 | 2 | 3 | ||||||||||
| Contact | TTV and metax do this diffrently:
| ||||||||||||||||||
| contact | Contact person for a DMP - Derived from Contact section. 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 organization. | Nested Data Structure | 1..n | Section in 'DMP' | 1 | 1 | 1 | 2 | |||||||||||
| affiliation | Affiliations of a contact | Nested Data Structure | 0..n | Properties in 'Contact' | 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 | 1 | ROR | Properties in 'Affiliation' | 1 | 0 | 1 | 2 | 3 | |||||||||
| contact_id | Identifier for contact | Nested Data Structure | 1 | 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 | example@company.com | Properties in 'Contact' | 1 | 1 | 1 | 1 | 3 | |||||||||
| name | Name of contact person | Nested Data Structure | 1 | Properties in 'Contact' | |||||||||||||||
| firstnames | First names of the contact person / principal researcher; ((RDA maDMP Standard: Name)) | String | 1 | Matti Note: In RDA this is not separated into first name and last name; In Finnish data model this is separated | Properties in 'name' | 1 | 1 | 1 | 1 | 2 (from ORCID) / 3 | |||||||||
| lastname | Last name of the contact person / principal researcher; ((RDA maDMP Standard: Name)) | String | 1 | Meikäläinen Note: In RDA this is not separated into first name and last name; In Finnish data model this is separated | Properties in 'name' | 1 | 1 | 1 | 1 | 2 (from ORCID) / 3 | |||||||||
| Cost | n.a. DMPs are not a relevant use case for TTV | ||||||||||||||||||
| 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 | Section in 'DMP' | 1 | 1 | 1 | 0 | 2 | ||||||||||
| currency_code | Currency of costs Note: Default is EUR or could this be linked to Funder_Id? | Term from Controlled Vocabulary | 0..1 | 978 | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id) | |||||||||
| description_cost | Description of costs Note: Could this be linked to Grant ID for description of applied/granted budget? | rdf:LangString | 0..1 | Storage 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 example.com/storagecostevaluation. | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||||
| title_cost | Title of costs Note: Could this be linked to Grant ID for title of applied/granted budget? | rdf:LangString | 1 | Storage and backup | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||||
| value_cost | Value of costs Note1: Could this be linked to Grant ID for applied/granted budget? Note2: Link with DMP / cost_dmp | Number | 0..1 | 1000 | Properties in 'Cost' | 1 | 1 | 1 | 0 | 3 / 2 (from grant_id / application) | |||||||||
| DMP Generic | n.a. DMPs are not a relevant use case for TTV | ||||||||||||||||||
| created | Date and time of first version of a DMP Encoded using the relevant ISO 8601 Date and Time compliant string (System coded) | DateTime | 1 | 2025-12-31T12:27:37Z | Properties in 'DMP Generic' | 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. | rdf:LangString | 0..1 | This DMP outlines strategies for managing soil sensor data collected across multiple agricultural sites, including storage, sharing, and compliance with FAIR principles. | Properties in 'DMP Generic' | 1 | 2 | ||||||||||||
| dmp_id | Identifier for the DMP itself | Nested Data Structure | 1 | Properties in 'DMP Generic' | 1 | 1 | 1 | 1 | |||||||||||
| identifier | Identifier for a DMP | String | 1..n | https://doi.org/10.5281/zenodo.1234567 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 Allowed Values: handle, doi, ark, url, other | Term from Controlled Vocabulary | 1 | doi For some research DMP may have to be closed by a justified reason, otherwise public | Properties in 'DMP_id' | 1 | 1 | 3 | |||||||||||
| modified | Indicates DMP version. Must be set each time DMP is modified. Encoded using the relevant ISO 8601 Date and Time compliant string (System coded) | DateTime | 1 | 2025-12-31T12:27:37Z | Properties in 'DMP Generic' | 1 | 1 | 1 | 0 | 1 (system) | |||||||||
| title | Title of a DMP (Max 100 char) | rdf:LangString | 1 | Data Management Plan for AI-driven Soil Analysis (2026–2029) | Properties in 'DMP Generic' | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||
| next_review | Next review date to update DMP Encoded using the relevant ISO 8601 Date and Time compliant string | Date | 0..1 | 2026-01-31 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' | 2 | 0 | 0 | 2 | 0 | 1 | 2 / 3 | |||||||
| status | Indicates the lifecycle stage of the DMP Allowed values: First version, Intermediate version, Final version | Term from Controlled Vocabulary | 1 | First version | Properties in 'DMP Generic' | ||||||||||||||
| type | Description of what kind of DMP to do Type of DMP: Student, Academic organization own template, Academic national template, National generic, EU Horizon, RDA / International | Term from Controlled vocabulary | 1 | Student DMP 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' | 2 | 0 | 0 | 2 | 0 | 1 | 3 | |||||||
| version | Version of DMP | String | 1 | 3 | Properties in 'DMP Generic' | 1 | |||||||||||||
| Project | TTV does not currently comprehensively process projects; nor connect them to funding decisions; this is in development: https://tietomallit.suomi.fi/model/researchfi_core_project?ver=1.0.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 | rdf:LangString | 1 | 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' | Available for funding decisions: https://iri.suomi.fi/model/ttv/tiivistelma | 1 | 1 | 1 | 1 | 1 (project_id links to long description) otherwise 3 | ||||||||
| end | Project end date Encoded 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' | see funding decision | 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 | 12 Mathematics | Properties in 'Project' | https://iri.suomi.fi/model/ttv/tutkimusala uses controlled vocabulary: http://uri.suomi.fi/codelist/research/tutkimusalaluokitus | 2 | 0 | 1 | 1 | 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 | ||||||||
| project_id | Project identifier | Nested Data Structure | 1 | Compare also with RAiD: https://raid.org/ | Properties in 'Project' | 1 | 1 | 1 | 2 | 2 | |||||||||
| identifier | 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 | Term from Controlled Vocabulary | 1 | URL | Properties in 'Project_id' | 1 | 1 | ||||||||||||
| title | Name/Title of the project | rdf:LangString | 1 | Learning Analytics for Student Success in Higher Education | Properties in 'Project' | 1 | 1 | 1 | 1 | 3 | |||||||||
| start | Project start date Encoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2026-01-01 | Properties in 'Project' | 1 | 0 | 1 | 1 | 3 (Can trigger update process e.g. after 3-6 months after start) | |||||||||
| 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 the focus of the DMP | Nested Data Structure | 0..n | Public after publishing the grant. | Properties in 'DMP' |
| 1 | 1 | 1 | 1 | 2 (Derived from Funding status & Grant_id) | ||||||||
| funder_id | Funder ID of the associated project, ROR if available | Nested Data Structure | 1 | Properties in 'Funding' | funding organisation identifier expected in this context, in TTV points directly to organisation class, which has pointer to identifier class | 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 Registry number of associated project Y-tunnus / Business ID | Properties in 'Funder_id' | https://iri.suomi.fi/model/ttv/pysyvatunniste | 1 | 1 | 1 | 1 | |||||||||
| type | Identifier type Allowed Values: | Term from Controlled Vocabulary | 1 | fundref | Properties in 'Funder_id' | https://iri.suomi.fi/model/ttv/pysyvantunnisteentyyppi this value comes from a controlled value set at: | 1 | 1 | 1 | 0 | |||||||||
| funding_status | To express different phases of project lifecycle. Allowed Values: planned, applied, granted, rejected | Term from Controlled Vocabulary | 0..1 | Applied maDMP use case: automatically derived information from grant ID the project is applied/granted | Properties in 'Funding' | NOTE: this is related to a DMP, not information on the funding decision itself - no source for this! Is this useful? most of this data is not available, if it is not "granted". | 1 | 1 | 1 | 0 | 3 | ||||||||
| grant_id | Grant ID of the associated project | Nested data structure | 0..1 | Properties in 'Funding' | 1 | 1 | 1 | 1 | 2 if DOI (not currently)3 | ||||||||||
| identifier | Grant ID | String | 1 | 654321 | Properties in 'Grant_id' | 1 | 1 | 1 | 1 | ||||||||||
| type | Identifier type Allowed Values: url, other | Term from Controlled Vocabulary | 1 | other | Properties in 'Grant_id' | https://iri.suomi.fi/model/ttv/pysyvantunnisteentyyppi this value comes from a controlled value set at: | 1 | 1 | 1 | 0 | |||||||||
| decision_expected | Expected date for funding decision Encoded using the relevant ISO 8601 Date and Time compliant string | DateTime | 1 | 2026-06-12T09:00:00Z | Properties in 'Funding' | n.a. | 2 | 0 | 2 | 0 | 2: select funding 3 | ||||||||
| end | Funding (Project) end Encoded using the relevant ISO 8601 Date and Time compliant string | Date | 1 | 2028-12-31 Used if funding period is different from project_end date | Properties in 'Funding' | Note this can be an ongoing activity without a defined end - so optional in ttv (0..1) | 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' | NOTE: this is available through the funder id - this is duplication? | 2 | 0 | 1 | 0 | 2 | ||||||||
| funded | Funded parties | Nested data structures | 1 | Properties in 'Funding' | |||||||||||||||
| researcher_id | Funded researcher id | Nested Data Structure | 1..n | Properties in 'Funded' | |||||||||||||||
| identifier | To indicate the value of an identifier (identifier string) | String | 1 | 0000-0000-0000-0000 | Properties in 'Researcher_id' | ||||||||||||||
| type | The identifier type for the concept | Term from Controlled Vocabulary | 1 | orcid | Properties in 'Researcher_id' | ||||||||||||||
| organization_id | Funded organization id | Nested Data Structure | 0..n | Properties in 'Funded' | |||||||||||||||
| identifier | To indicate the value of an identifier (identifier string) | String | 1 | https://ror.org/00abcde11 | Properties in 'Organization_id' | ||||||||||||||
| type | The identifier type for the concept | Term from Controlled Vocabulary | 1 | ROR | Properties in 'Organization_id' | ||||||||||||||
| granted_funding | Call for funding | String | 1 | Funding call Y | Properties in 'Funding' | ||||||||||||||
| parent_decision_id | Funding decision for the entire research program or research consortium for the grant_id | Nested Data Structure | 0..1 | Properties in 'Funding' | |||||||||||||||
| identifier | Grant ID of parent decision | String | 1 | http://example.com/grants/776242 | Properties in 'parent_decision_id' | 1 | 1 | 1 | 1 | ||||||||||
| type | Identifier type Allowed Values: url, other | Term from Controlled Vocabulary | 1 | url | Properties in 'parent_decision_id' | https://iri.suomi.fi/model/ttv/pysyvantunnisteentyyppi this value comes from a controlled value set at: | 1 | 1 | 1 | 0 | |||||||||
| start | Funding (Project) start Encoded using the relevant ISO 8601 Date | Date | 1 | 2027-01-01 Used if funding period is different from project/start date | Properties in 'Funding' | https://iri.suomi.fi/model/ttv/alkamispaivamaara-6 | 2 | 0 | 2 | 0 | 2 | ||||||||
| submission_dl | Deadline for funding submission Encoded using the relevant ISO 8601 Date | Date | 1 | 2026-08-31 | Properties in 'Funding' | n.a. (NOTE: This information is related to he funding call, which is it's own class), there it would be: https://iri.suomi.fi/model/ttv/paattymispaivamaara-3 and https://iri.suomi.fi/model/ttv/paattymiskellonaika (with the additional note that when the call type is "continuous" there a deadline is not valid (cardinality <>1) | 2 | 0 | 2 | 0 | 2: select funding3 | ||||||||
| Project - Security, Privacy, Rights and Ethics | This whole section does not exist in TTV, But maybe there is something on this in Metax? | ||||||||||||||||||
| security_privacy | Describe how the guidelines of ethics, security and privacy are followed if ethics committee needs to be consulted or agreements are needed for conducting the research. | Nested Data Structure | 0..1 | 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 | rdf:LangString | 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' | 1 | 1 | 0 | 3 | ||||||||||
| risk_assessment_id | ID of risk assessment | Nested Data Structure | 0..1 | Properties in 'Security_privacy' | 2 | 2 | 0 | 2 | |||||||||||
| identifier | To indicate the specific value of an identifier for risk assessment | String | 1 | example.org/risk-assessment | Properties in 'risk_assessment_id' | ||||||||||||||
| type | To specify a type of an identifier for a project. Suggested Values: URI | Term from Controlled Vocabulary | 1 | URI | Properties in 'risk_assessment_id' | ||||||||||||||
| title | Title of security measures | rdf:LangString | 1 | Anonymization of Personally Identifiable Data | Properties in 'Security_privacy' | 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 can affect 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. | rdf:LangString | 0..1 | The study involves human participants; informed consent will be obtained, and GDPR compliance ensured. Ethical approval granted by the institutional review board. | Properties in 'Security_privacy' | 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 | Yes This is an important trigger because then the DMP must be very good | Properties in 'Security_privacy' | 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. | String | 0..1 | Properties in 'Security_privacy' | 1 | 1 | 1 | 0 | 3 | ||||||||||
| agreements | Other needed agreements. | rdf:LangString | 0..n | Disclosure agreement with project partners | Properties in 'Security_privacy' | 2 | 2 | 0 | 1 | 3 | |||||||||
| agreements_data_right | Agreements needed with other organisations and people related to the rights to the material. Give both the type and name of the agreement. | rdf:LangString | 0..n | Data right agreement with external laboratory. Agreement for utilizing technical devices, and external research laboratory. | Properties in 'Security_privacy' | 2 | 2 | 0 | 3 | ||||||||||
| data_use_region | To indicate where the data will be managed? (Continents) | Term from Controlled Vocabulary | 0..n | Europe, South-America | Properties in 'Security_privacy' | 2 | 1 | 0 | |||||||||||
| ipr_copyright | To indicate whether there are IPR or copyright issues in research described in a DMP. Allowed values: Yes, No, Unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'Security_privacy' | 2 | 1 | 0 | 3 | ||||||||||
| ownership_data_right_organization | Organization that 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 | https://ror.org/00abcde11 | Properties in 'Security_privacy' | 2 | 1 | 0 | 3 | ||||||||||
| ownership_data_right_person | To indicate who owns the data/rights related to the data. Give ORCID, if available otherwise give name surname first name | String | 0..n | 0000-0000-0000-0000 | Properties in 'Security_privacy' | 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 | Yes | Properties in 'Security_privacy' | 2 | 1 | 0 | 3 | ||||||||||
| Project - Security & privacy & ethics - DPIA process | |||||||||||||||||||
| dpia | Pre-assessment for DPIA | Nested Data Structure | 0..n | ||||||||||||||||
| dpia_needed | To assess whether DPIA is needed | Boolean | 0..1 | True | Properties in 'Security_privacy' | 1 | 1 | 1 | 0 | ||||||||||
| dpia_id | If DPIA exists | Nested Data Structure | 0..1 | Properties in 'DPIA' Optional addition | 2 | 1 | 1 | 0 | 3 | ||||||||||
| identifier | To indicate the specific value of an identifier for DPIA | String | 1 | https://example.org/project | Properties in 'dpia_id' Optional addition | ||||||||||||||
| type | To specify a type of an identifier for DPIA. URI/DOI | Term From Controlled Vocabulary | 1 | URI | Properties in 'dpia_id' Optional addition | ||||||||||||||
| privacy_notice_id | If privacy notice exist give link / archive number | Nested Data Structure | 0..1 | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 | ||||||||||
| identifier | To indicate the specific value of an identifier for privacy notice | String | 1 | https://example.org/project | |||||||||||||||
| type | To specify a type of an identifier for privacy notice. URL | Term From Controlled Vocabulary | 1 | URI | |||||||||||||||
| pre_dpia | To indicate whether risk assessment been filled in. (risk assessment/pre-dpia, selftest if DPIA is needed) | Booelan | 0..1 | True | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 | |||||||||
| personal_data_sp_category | Special categories of personal data that is processed. | Term from Controlled Vocabulary | 0..1 | Data of ethnic origin, data of philosophical beliefs | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | Requirement comes from the law | |||||||||
| ethnic_origin | To indicate whether data of ethnic origin is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| political_opinions | To indicate whether data of political opinions is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| religion_philosophical_beliefs | To indicate whether data of religion or philosophical beliefs is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| trade_union_membership | To indicate whether data of of trade union membership is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_concerning_health | To indicate whether data concerning health of individuals is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| sexual_orientation_or_activity | To indicate whether data of sexual orientation or activity is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| genetic_or_biometric_data | To indicate whether genetic or biometric data for identifying the persons is processed. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| other_sp_category | Describe the other special categories of data that you process in the research. | rdf:LangString | 0..1 | None | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_prosessing_basis | Basis for data processing. | rdf:LangString | 0..1 | Processing is necessary to achieve research objectives. Legal basis is informed consent. | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_prosessing_sp_category | Basis for processing special categories of personal data. | rdf:LangString | 0..1 | Explicit consent is required for handling biometric and health data to ensure compliance with GDPR. | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_transfer_outside_EU | To indicate whether personal data is transferred outside the EU Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | No | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_transfer_country | To indicate to which countries personal data is transferred. | rdf:LangString | 0..n | Germany | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| data_external_processors | To indicate whether there are external processors. Allowed Values: yes, no, unknown | Term from Controlled Vocabulary | 0..1 | Yes | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
| personal_data_minimized | To specify how the processing of personal data is minimized. | rdf:LangString | 0..1 | Pseudonymization and removal of direct identifiers | Properties in 'DPIA process' Optional addition | 2 | 1 | 1 | 0 | 3 / 1 | |||||||||
