Project details
| Question in resource application | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| Project name* | dmp_generic/project/title | 1 (project 0..n) |
| project title |
Project description*
| dmp_generic/project/description dmp_generic/project/start dmp_generic/project/end | 1 (project 0..n) 1 (project 0..n) 0..1 (project 0..n) |
| project abstract |
| Primary field of science | dmp_generic/project/field_of_science | 0..n (project 0..n) |
| closest: Faculty or research unit of the project leader |
| Secondary field of science | dmp_generic/project/field_of_science | 0..n (project 0..n) |
| - |
| We process personal data in this project* (Yes/No) | dmp_generic/dataset/personal_data | 1 (dataset 1..n) |
| The research uses data originating from humans: → yes → selected "information belonging to special categories of personal data or otherwise sensitive information" |
Funding decision (these are used to find the funding decision)
| Question | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| Funded person ORCID | dmp_generic/funding/funded/researcher_id/identifier | 1..n (funding 0..n) |
| |
| Funder name | dmp_generic/funding/funder | 1 (funding 0..n) | ||
| Funded organization ID | dmp_generic/funding/funded/organization_id/identifier | 0..n (funding 0..n) | ||
| Funding start year from | dmp_generic/funding/start | 1 (funding 0..n) |
| |
| Funder project number? | - | - | - | Funding decision number |
Selected resource packages
| Question in resource application | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| Publications* | dmp_generic/dataset/related_identifier/identifier | 0..n (dataset 1..n) |
| - |
| Keywords* | dmp_generic/dataset/keyword | 0..n (dataset 1..n) |
| - |
Computing (CPU, GPU, Cloud) Billing Units:
| Question in resource application | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| Which software are you planning to use?* | dataset/technical_resource/name | 1 (technical_resource 0..n) |
| - |
| Have you run the software on our systems or some other systems before?* | - |
| not in maDMP data model | - |
| What kind of computing do you plan to do? E.g. simulations, jobs, analyses, services?* | - | not in maDMP data model | - | |
| Have you confirmed the efficiency of the computing? E.g. simulation benchmark, scaling tests, alternative approach?* | - | not in maDMP data model | - | |
| What results will you produce with these applied resources?* | - | not in maDMP data model | - |
Storage Billing Units:
| Question in resource application | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| What data are you storing? | dataset/description | 1 |
| - |
| Who is responsible for managing the data? | dmp_gengeric/agent with role curator | 0..n |
| Who will be responsible for controlling access to data OR The rights to use the research material used in the project are granted by (multiple choice) |
| Who owns the data? | dmp_generic/security_privacy/ownership_data_right_organization dmp_generic/security_privacy/ownership_data_right_person possibly agent with role rights holder with connection(s) to dataset(s) | 1 0..n 0..n |
| - |
| Choose storage systems you plan to use* (multiple choice) | dataset/dataset_lifecycle/storage_location | 1 (dataset_lifecycle 0..1) |
| if CSC services selected: A detailed description of the storage solutions and the backup implementation |
| How do you plan to use each storage system?* | not in maDMP data model |
| - | |
| If your approach generates a lot of files, how do you optimized managing files and regular cleansing cycles?* | dataset/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. dataset/data_lifecycle/data_retention: Indicate the retention period and any policies for data disposal or archiving. | 0..1 1 (dataset_lifecycle 0..1) |
| |
| How will you manage your data after active data processing or computing phase? | dataset/data_lifecycle/description | 0..1 |
| for each listed dataset: dataset will be: opened/archived, and planned storage period in years (1 to 3 years, 3 to 5 years, 5 to 15 years, Over 15 years) |
What is your exit strategy from CSC environment when your CSC project ends? → ohjeistetaan että CSCn palvelut ei pitkäaikaissäilytykseen aktiivisen vaiheen jälkeen | dataset/dataset_lifecycle/exit_plan | 1 (dataset_lifecycle 0..1) |
| - |
| Datasets* (multiple can be added) | dataset/title dataset/dataset_id | 1 1..n |
| Dataset name or brief description (only for datasets that are planned to be opened or archived) |
| Data management plan URL | dmp_generic/dmp_id | 1..n |
| - |
missing: size of the data to be stored
Lumi Resources (Lumi application)
| Question in resource application | maDMP fields | Cardinality in maDMP | Notes/comments | UH DMP Template equivalence |
|---|---|---|---|---|
| CPU core hours* (thousands) | dmp_generic/dataset/technical_resource/computing_capacity_CPU |
| - | |
| GPU hours* (thousands) | dmp_generic/dataset/technical_resource/computing_capacity_GPU |
| - | |
| Storage TiB hours* (thousands) | dmp_generic/dataset/technical_resource/estimate_datasize |
| - | |
| QPU minutes* (thousands) | - | not in maDMP data model | - |