- Poll for the importance of maDMP principles
Groups:
- maDMP standard - Contact, contributor & cost
- maDMP standard - Project, Funding, DMP, Data (Facilitator Juuso Marttila, University of Jyväskylä )
- maDMP standard - Distribution, Licence, Host, DMP, Data (Facilitator Soile Manninen, University of Helsinki)
- maDMP standard - Security & Privacy, Technical resource & Metadata (Facilitator Anna Rohunen, University of Oulu & Johanna Laiho-Kauranne, CSC) - This group will be in English
- maDMP standard - Environment & Biodiversity - Data, (Facilitator Miika Alonen, CSC)
Work:
15:00-15:05 General info on group work
15:05-15:45 RDA DMP Standard assessment in small groups
- Instructions for the group
- Each group facilitator opens the concept board and shares it for the group via screen
Concept board workspace: https://app.conceptboard.eu/board/289e-y68k-3yxh-6mzs-bc24 - Each group assesses the metadata elements assigned to the group
- Work is done first by discussing the instructions with the group
- Each group facilitator opens the concept board and shares it for the group via screen
- Group work:
- Examine the Entity of the RDA DMP Standard in the concept board. Discuss whether the elements need further clarification (can be given 5 minutes)
- Then examine the information model for research project in Finland: (can be given 20 minutes)
- What other information should be included?
- Is something vital missing in the RDA DMP Standard?
- Is something unnecessary and could be left out?
- What information should be structural?
- What information could/should be linked with other information systems?
- What information could/should be harvested from other information systems?
- Existing standards, ontologies to be utilised?
- Add also open comments to standard description to concept board:
- What other information should be included?
- Joint discussion about this principle and what are key processes that its update could trigger in machine-actionable DMP? 5 minutes
- Joint discussion about the entity of standard and are there elements missing or unnecessary? (5 minutes or time allowing)
15:45-16:00 Facilitators report to general discussion
Additional reference and prior reading:
https://github.com/RDA-DMP-Common/RDA-DMP-Common-Standard
https://oblassers.github.io/dmap-mockups/
- What other information should be included?
- What should be included in minimum data model?
- What information should be structural?
- What information could/should be linked with other information systems?
- What information could/should be harvested from other information systems?
- Existing standards, ontologies to be utilised?
Table below is copied to concept board https://app.conceptboard.com/board/289e-y68k-3yxh-6mzs-bc24# and divided for small groups chaired by Soile Manninen (HY), Juuso Marttila (JY), Anna Rohunen (OY) & Miika Alonen (CSC)
RDA maDMP standard for OSTrails FI Pilot comments towards national maDMP template | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Contact | contact_id | Identifier for a contact person | |||
mbox | E-mail address | cc@example.com | |||
name | Name of the contact person | Charlie Chaplin | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Contact_id | identifier | ||||
type | Identifier type | orcid | |||
Allowed Values: | |||||
orcid | |||||
isni | |||||
openid | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Cost | currency_code | Allowed values defined by ISO 4217. | EUR | ||
description | Description | Costs for maintaining.... | |||
title | Title | Storage and backup | |||
value | Value | 1000 | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Data | data_quality_assurance | Data Quality Assurance | We use file naming convention... | ||
dataset_id | Dataset ID | ||||
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. | Field observation | |||
distribution | To provide technical information on a specific instance of data. | ||||
issued | Issued. Encoded using the relevant ISO 8601 Date and Time compliant string | 30.6.2019 | |||
keyword | Keyword | keyword 1, keyword 2 | |||
language | Language of the dataset expressed using ISO 639-3 | eng | |||
metadata | To describe metadata standards used. | ||||
personal_data | unknown | ||||
Allowed Values: | |||||
yes | |||||
no | |||||
unknown | |||||
preservation_statement | Preservation Statement | Must be preserved to enable... | |||
security_and_privacy | To list all issues and requirements related to security and privacy | ||||
sensitive_data | unknown | ||||
Allowed Values: | |||||
yes | |||||
no | |||||
unknown | |||||
technical_resource | To list all technical resources needed to implement a DMP | ||||
title | 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. | Fast car images | |||
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 | image | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Dataset_id | identifier | Identifier for a dataset | https://hdl.handle.net/11353/10.923628 | ||
type | Identifier type | handle | |||
Allowed Values: | |||||
handle | |||||
doi | |||||
ark | |||||
url | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Distribution | access_url | A URL of the resource that gives access to a distribution of the dataset. e.g. landing page. | http://some.repo... | ||
available_until | Indicates how long this distribution will be/ should be available. Encoded using the relevant ISO 8601 Date and Time compliant string | 30.6.2030 | |||
byte_size | Byte Size | 690000 | |||
data_access | Indicates access mode for data. | open | |||
Allowed Values: | |||||
open | |||||
shared | |||||
closed | |||||
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. | Best quality data before resizing | |||
download_url | The URL of the downloadable file in a given format. E.g. CSV file or RDF file. | http://some.repo.../download/... | |||
format | Format according to: https://www.iana.org/assignments/media-types/media-types.xhtml if appropriate, otherwise use the common name for this format | image/tiff | |||
host | To provide information on quality of service provided by infrastructure (e.g. repository) where data is stored | ||||
license | To list all licenses applied to a specific distribution of data. | ||||
title | 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. | Full resolution images | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
DMP | contact | Contact person for a DMP | |||
contributor | To list people that play role in data management related to this DMP, e.g. resoponsible for performing actions described in this DMP. | ||||
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. | ||||
created | Date and time of the first version of a DMP. Must not be changed in subsequent DMPs. Encoded using the relevant ISO 8601 Date and Time compliant string | 2019-03-13T13:13:00 | |||
dataset | To describe data on a non-technical level. | ||||
description | To provide any free-form text information on a DMP | This DMP is for our new project | |||
dmp_id | Identifier for the DMP itself | ||||
ethical_issues_description | To describe ethical issues directly in a DMP | There are ethical issues, because... | |||
ethical_issues_exist | To indicate whether there are ethical issues related to data that this DMP describes. | yes | |||
Allowed Values: | |||||
yes | |||||
no | |||||
unknown | |||||
ethical_issues_report | To indicate where a protocol from a meeting with an ethical commitee can be found | http://report.location | |||
language | Language of the DMP expressed using ISO 639-3 | eng | |||
modified | Must be set each time DMP is modified. Indicates DMP version. Encoded using the relevant ISO 8601 Date and Time compliant string | 2020-03-14T10:53:49 | |||
project | Project related to a DMP | ||||
title | Title of a DMP | DMP for our new project | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
DMP_id | identifier | Identifier for a DMP | https://doi.org/10.1371/journal.pcbi.1006750 | ||
type | Identifier type | doi | |||
Allowed Values: | |||||
handle | |||||
doi | |||||
ark | |||||
url | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Funder_id | identifier | Funder ID, recommended to use CrossRef Funder Registry. See: https://www.crossref.org/services/funder-registry/ | 5,011E+11 | ||
type | Identifier type | fundref | |||
Allowed Values: | |||||
fundref | |||||
url | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Funding | funder_id | Funder ID of the associated project | |||
funding_status | To express different phases of project lifecycle. | granted | |||
Allowed Values: | |||||
planned | |||||
applied | |||||
granted | |||||
rejected | |||||
grant_id | Grant ID of the associated project | 1234567 | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Grant_id | identifier | Grant ID | 776242 | ||
type | Identifier type | other | |||
Allowed Values: | |||||
url | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Host | availability | Availability | 99,5 | ||
backup__frequency | Backup Frequency | weekly | |||
backup_type | Backup Type | tapes | |||
certified_with | Repository certified to a recognised standard | coretrustseal | |||
Allowed Values: | |||||
din31644 | |||||
dini-zertifikat | |||||
dsa | |||||
iso16363 | |||||
iso16919 | |||||
trac | |||||
wds | |||||
coretrustseal | |||||
description | Description | Repository hosted by... | |||
geo_location | Physical location of the data expressed using ISO 3166-1 country code. | AT | |||
pid_system | PID System | doi | |||
Allowed Values: | |||||
ark | |||||
arxiv | |||||
bibcode | |||||
doi | |||||
ean13 | |||||
eissn | |||||
handle | |||||
igsn | |||||
isbn | |||||
issn | |||||
istc | |||||
lissn | |||||
lsid | |||||
pmid | |||||
purl | |||||
upc | |||||
url | |||||
urn | |||||
other | |||||
storage_type | The type of storage required | ||||
support_versioning | yes | ||||
Allowed Values: | |||||
yes | |||||
no | |||||
unknown | |||||
title | Title | Super Repository | |||
url | The URL of the system hosting a distribution of a dataset | https://zenodo.org | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Licence | license_ref | Link to license document. | https://creativecommons.org/licenses/by/4.0/ | ||
start_date | If date is set in the future, it indicates embargo period. Encoded using the relevant ISO 8601 Date and Time compliant string | 30.6.2019 | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Metadata | description | Description | provides taxonomy for... | ||
language | Language of the metadata expressed using ISO 639-3 | eng | |||
metadata_standard_id | Metadata Standard ID | ||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Metadata_standard_id | identifier | Identifier for the metadata standard used. | http://www.dublincore.org/specifications/dublin-core/dcmi-terms/ | ||
type | Identifier type | url | |||
Allowed Values: | |||||
url | |||||
other | |||||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Project | description | Project description | Project develops novel... | ||
end | Project end date. Encoded using the relevant ISO 8601 Date and Time compliant string | 31.3.2020 | |||
funding | Funding related with a project | ||||
start | Project start date. Encoded using the relevant ISO 8601 Date and Time compliant string | 1.4.2019 | |||
title | Project title | Our New Project | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Security_and_privacy | description | Description | Server with data must be kept in a locked room | ||
title | Title | Physical access control | |||
Element | Name | Description | Could this be structural? | Standards, ontologies to be used | Example Value - You may write over meaningful examples |
Technical_resource | description | Description of the technical resource | Device needed to collect field data... | ||
name | Name of the technical resource | 123/45/43/AT | |||
Revised from original source: Tomasz Miksa, Paul Walk, Peter Neish. RDA DMP Common Standard for Machine-actionable Data Management Plans. http://doi.org/10.15497/rda00039 |
3. Defining national use cases
- Researcher
- PI Researcher
- Research performing organization (RPO)
- Rector of RPO
- Research funding organisation (RFO)
- Internal data stewards, data support and IT
- External research service providers
Examples of use cases identified from the kick-off:
- Facilitating researchers' everyday work and the automatic flow of information between systems.
- Enabling automatic actual tracking. Also clarifying ownership, licensing, etc are needed. A lot of useful metadata for description; hopefully GDPR won't get in the way.
- A tool that guides and guides the researcher more strongly. The best thing would be if sufficient guidance is embedded into the tool. The researcher would be able to answer questions without leaving the tool, for example. E.g. when needed to visit the university's website for more information.
- A tool that allows DMP data to be utilized more extensively within organizations.
- Opportunities to make more efficient use of the data content of DMPs at the organizational level, e.g. timely support and service provision for researchers or the implementation of statutory and Privacy by Design processes.