Page History

TTV and metax do this diffrently:

1. we have an actor(can be person or organisation) 
2. then between the actor and dataset(research output) we have a class with role information (reified relationship), this role in metax can be: https://koodistot.suomi.fi/codescheme;registryCode=fairdata;schemeCode=agentrole ( Contributor, Creator, Curator, Publisher, Rights holder)
3. this enables to simplify the schema (however, at its simplest it does not allow to give different cardinalities to different roles, why is metax does this with 5 different reltionship types - which allows to define role specific cardinalities.

To specify the creators, curators and contributors etc. of the dataset.  Orcid, ROR (for functionability selection person or organization; the use list of previously given names of organizations /DMP author and contributors)

ror.org/12abcde345

agent_role_relation

To specify the role an agent has in relation to a specific object in this DMP. Each entry links one role to one object for the same agent, or if the role is not related to an object, it can be left empty, e.g. with role Creator of DMP. 

ID of an object that this agent is associated with within the DMP. This field links the agent's role to a specific object, e.g. dataset or project.

To indicate the type of the related object. 

Role of the agent related.

To indicate the contact person(s) for the DMP

ror.org/12abcde345

Currency of costs

Note: Default is EUR

Description of costs

Note: Could this be linked to Grant ID for description of applied/granted budget?

Title of costs

Note: Could this be linked to Grant ID for title of applied/granted budget?

Value of costs

Note1: Could this be linked to Grant ID for applied/granted budget?

1000

Dataset identifier. A trustworthy, long-term repository will provide a persistent identifier.

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

Also this is a controlled value set at:

http://uri.suomi.fi/codelist/research/PID 

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. 

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. 

Description of used dataset formats during the active research. 

csv

• (only focussed on datasets atm, n.a.

Ilmastonmuutokset

http://www.yso.fi/onto/yso/p5729

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.

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.

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.

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.

Type of relation between the resource and the related resource

HasMetadata

example.com/metadata-scheme

http://www.ddialliance.org/Specification/DDI-Lifecycle/3.1/XMLSchema/instance.xsd

Type of the identifier

Project id(s) of the project(s) that this dataset is associated with within this DMP.

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.

Describe the origin of the data

https://example.com/

https://iri.suomi.fi/model/ttv/nimi-3 (rdf:langString) 

Data set type 

8.0

DMP information not relevant to TTV use cases: n.a.

perhaps Metax might have some info

2024-10-15T14:30:00Z

Active data can be deleted and archived at the same time

Fairdata IDA

No

Snapshots of the distribution are archived monthly in IDA for long-term preservation.

Utilisation of prefilled information derived from backup of services used

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) ?

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

With whom will the data be shared during the project

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?

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.

2040-12-12T12:00:00Z

Could be specified that this relates to unpublished data.

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.

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

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

String

Nested Data Structure

String

https://urn.fi/urn:nbn:fi:csc-202402000273088

String

Allas

Where will the data be stored during the project?

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

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)

https://hdl.handle.net/10345/3873

Estimated byte size

M

Note: Important as it affects what tools are available.

Indicates current access mode for data and data sharing.

Open

Defined in: https://iri.suomi.fi/model/ttv/saatavuusluokka which uses the controlled Vocabulary: https://koodistot.suomi.fi/codescheme;registryCode=fairdata;schemeCode=access_type 

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.  

PID System(s) used by a host

To indicate whether the host system supports versioning.

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.)

If date is set in the future, it indicates embargo period.

True

URL

To indicate whether the discovery metadata is open.

False

Especially important in the case of large datasets, from which the data itself cannot be preserved, but is produced again if necessary

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)

https://urn.fi/urn:nbn:fi:csc-202605000319828

Roihu

Rahti

Project data magnitude for resources required to analyse and store the data.

Connected to CSC resource applications

General information about the DMP 

To specify the creators, curators and contributors etc. of the dataset.  Orcid, ROR (for functionability selection person or organization; the use list of previously given names of organizations /DMP author and contributors)

To indicate the contact person(s) for the DMP

Date and time of first version of a DMP

Encoded using the relevant ISO 8601 Date and Time compliant string (System coded)

2025-12-31T12:27:37Z

This DMP outlines strategies for managing soil sensor data collected across multiple agricultural sites, including storage, sharing, and compliance with FAIR principles.

https://doi.org/10.5281/zenodo.1234567

For some research DMP may have to be closed by a justified reason, otherwise public

Identifier type

doi

For some research DMP may have to be closed by a justified reason, otherwise public

Funding related with the focus of the DMP

eng

2025-12-31T12:27:37Z

Next review date to update DMP

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

A piece of research-related software, including its identification, purpose, access conditions, relationships to other research outputs, and plans for maintenance, documentation, and long-term archiving etc.

Indicates the lifecycle stage of the DMP

Data Management Plan for AI-driven Soil Analysis (2026–2029)

Description of what kind of DMP to do, can affect what questions are asked

Indicates whether the research project uses or produces data or if it is purely theoretical. If no data is used or produced, the dataset section does not need to be filled. 

Funding related with the focus of the DMP

Expected date for funding decision

Encoded using the relevant ISO 8601 Date and Time compliant string

2026-06-12T09:00:00Z

Funding (Project) end

Encoded using the relevant ISO 8601 Date and Time compliant string

2028-12-31

Used if funding period is different from project_end date

Note this can be an ongoing activity without a defined end - so optional in ttv (0..1)

https://iri.suomi.fi/model/ttv/paattymispaivamaara-4

501100002428

Registry number of associated project Y-tunnus / Business ID