-
Notifications
You must be signed in to change notification settings - Fork 38
/
epm-view-table.xml
556 lines (553 loc) · 38.1 KB
/
epm-view-table.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
<?xml version="1.0" encoding="UTF-8"?>
<rdmo xmlns:dc="http://purl.org/dc/elements/1.1/" created="2023-11-13T15:38:38.629760+01:00">
<view dc:uri="https://dmp.metrology-rdm.eu/terms/views/epm-table">
<uri_prefix>https://dmp.metrology-rdm.eu/terms</uri_prefix>
<key>epm-table</key>
<dc:comment>work in progress</dc:comment>
<title lang="en">European Partnerhip on Metrology</title>
<help lang="en">View (export template) for the funding framework program "European Partnership on Metrology", based on "Horizon Europe" (2021-2027), funded by the European Commission via EURAMET</help>
<title lang="de">Europäische Partnerschaft für Metrologie</title>
<help lang="de">Ansicht (Exportvorlage) für das Förderprogramm "European Partnership on Metrology" angelehnt an "Horizon Europe" (2021-2027), durch die Europäische Kommission über EURAMET gefördert</help>
<catalogs/>
<template>{% load view_tags %}
{% get_set 'project/partner/id' as partners %}
{% get_set 'project/funder/id' as funders %}
{% get_set 'project/dataset/id' as datasets %}
{% get_set 'project/other_research_output' as other_outputs %}
{% get_values 'project/dataset/preservation/repository' as repositories %}
{% get_value 'project/dmp/dmp_version' as dmp_version %}
{% check_condition 'dmp_initial' as dmp_initial %}
{% check_condition 'dmp_not_initial' as dmp_not_initial %}
{% check_condition 'dmp_midterm' as dmp_midterm %}
{% check_condition 'dmp_final' as dmp_final %}
{% check_condition 'repository_zenodo' as repository_zenodo %}
{% check_condition 'repository_ptb_oar' as repository_ptb_oar %}
<head>
<div style="height:200;">
<b>{% render_value 'project/funder/grant_nr' %} &#8212; {% render_value 'project/acronym' %}</b>
<img src="https://www.euramet.org/fileadmin/Public/assets/logo.png" alt="Logo EURAMET" width="200" style="float:right;">
</div>
<br />
<hr noshade color=rgb(0, 157, 129) width=100% size=20>
<br />
<div id="Title" style="color:white;background-color:black;text-align:center;line-height:21mm;font-size:2.5em;"><b>DATA MANAGEMENT PLAN</b></div>
<br />
<div>
<span style="float:left;width:30%;">Grant agreement number </span>{% render_value 'project/funder/grant_nr' %}<br /><br />
<span style="float:left;width:30%;">Project short name / acronym</span>{% render_value 'project/acronym' %} <br /><br />
<span style="float:left;width:30%;">Project full title </span>{% render_value 'project/title' %} <br /><br />
<span style="float:left;width:30%;">Data management plan version</span>
1<sup>st</sup> (begin) {% if dmp_initial %}&#9745;{% else %}&#9744;{% endif %}&emsp;
2<sup>nd</sup> (midterm) {% if dmp_midterm %}&#9745;{% else %}&#9744;{% endif %}&emsp;
3<sup>rd</sup> (end) {% if dmp_final %}&#9745;{% else %}&#9744;{% endif %}<br /><br />
</div>
</head>
<body>
<div id="0"><h1>Data management plan</h1></div>
<div id="1"><h2>Data Summary</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q01">
<td>1 Will you re-use any existing data and what will you re-use them for?<br />
State the reasons if re-use of any existing data has been considered but discarded.</td>
<td>
{% if dmp_initial %}
This project will re-use:
<ul>{% render_value_list 'project/dataset/provenance/content' %}</ul>
These data will be used for this purpose:
<ul>{% render_value_list 'project/dataset/usage_description' set_index='*' %}</ul>
{% else %}
This project re-used the following publicly available datasets:<br />
{% for dataset in datasets %}
<b>Dataset {{ dataset.value }}:</b>
{% render_value_list dataset 'project/dataset/provenance/content' %}<br />
These data will be used for this purpose:
{% render_value_list dataset 'project/dataset/usage_description' %}<br />
{% endfor %}
No existing data have been considered for re-use and then discarded.
{% endif %}
</td>
</tr>
<tr id="Q02">
<td>2 What types and formats of data will the project generate or re-use?</td>
<td>The project {% if dmp_initial %}will collect{% else %}collected{% endif %} data of the following types and formats:
<ul>{% render_value_list 'project/dataset/format' set_index='*' %}</ul>
</td>
</tr>
<tr id="Q03">
<td>3 What is the purpose of the data generation or re-use and its relation to the objectives of the project?</td>
<td>
<p><u>Purpose of the data generation or re-use</u></p>
The data generated and re-used {% if dmp_initial %}will be{% else %}were{% endif %}
from {% render_value_inline_list 'project/dataset/creation_methods' %}.
They {% if dmp_initial %}will be{% else %}were{% endif %} used in meeting the project’s objectives and in conference and peer-reviewed publications.
<p><u>Data generated in relation to the objectives of the project</u></p>
<p>
{% if dmp_initial %}
Data will be generated for the following aims:
{% render_value_inline_list 'project/dataset/usage_objectives' set_index='*' %}
{% else %}
{% for dataset in datasets %}
{% check_condition dataset_created as dataset_created %}
{% if dataset_created %}
<b>Dataset {{ dataset.value }}:</b>
{% render_value_list dataset 'project/dataset/usage_objectives' %}
{% endif %}
{% endfor %}
{% endif %}
</p>
<p><u>Data re-used in relation to the objectives of the project</u></p>
<p>
{% if dmp_initial %}
Data will be re-used for the following aims:
{% render_value_inline_list 'project/dataset/usage_description' set_index='*' %}
{% else %}
{% for dataset in datasets %}
{% check_condition dataset_reused as dataset_reused %}
{% if dataset_reused %}
<b>Dataset {{ dataset.value }}:</b>
{% render_value_list dataset 'project/dataset/usage_description' %}
{% endif %}
{% endfor %}
{% endif %}
</p>
</td>
</tr>
<tr id="Q04">
<td>4 What is the expected size of the data that you intend to generate or re-use?</td>
<td>The overall size of the generated data is {% render_value 'project/dataset/size/volume' %}.</td>
</tr>
<tr id="Q05">
<td>5 What is the origin/provenance of the data, either generated or re-used?</td>
<td>
<p><u>Data generated in the project</u></p>
<p>
The data generated {% if dmp_initial %}will be{% else %}were{% endif %} from {% render_value_inline_list 'project/dataset/creation_methods' %}.
The data collected from domestic properties will remain confidential and will not be included in the repository.
{% if dmp_not_initial %}
The project generated [[N]] datasets. The provenance of the data generated is specified below:
{% for dataset in datasets %}
{% check_condition dataset_created as dataset_created %}
{% if dataset_created %}
<b>Dataset {{ dataset.value }}:</b>
{% render_set_value dataset 'project/dataset/creation_methods' %}<br />
{% endif %}
{% endfor %}
{% endif %}
</p>
<p><u>Re-used data</u></p>
<p>
The existing data originate from several sources, which include: {% render_value_inline_list 'project/dataset/provenance/content' %}.
{% if dmp_not_initial %}
The project re-used [[N]] datasets which originated from the following external sources (from outside of this project):
{% for dataset in datasets %}
{% check_condition dataset_reused as dataset_reused %}
{% if dataset_reused %}
<b>Dataset {{ dataset.value }}:</b>
{% render_set_value dataset 'project/dataset/provenance/content' %}<br />
The data were created by
{% render_set_value dataset 'project/dataset/creator/name' %}
and can be found at the following address:
{% render_set_value dataset 'project/dataset/uri' %}
{% endif %}
{% endfor %}
{% endif %}
</p>
</td>
</tr>
<tr id="Q06">
<td>6 To whom might your data be useful ('data utility'), outside your project?</td>
<td>The data might be useful to:
<ul>{% render_value_list 'project/dataset/reuse_scenario' %}</ul></td>
</tr>
</tbody></table>
</div>
<div id="2"><h2>FAIR data</h2></div>
<div id="2.1"><h3>Making data findable, including provisions for metadata</h3>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q07">
<td>7 Will the data be identified by a persistent identifier?</td>
<td>Yes, each of the project's deposited datasets {% if dmp_initial %}will be{% else %}is{% endif %} identified by:
<ul>{% render_value_list 'project/dataset/pids/system' %}</ul></td>
</tr>
<tr id="Q08">
<td>8 Will rich metadata be provided to allow discovery? What metadata will be created? What disciplinary or general standards will be followed?<br />
In case metadata standards do not exist in your discipline, please outline what type of metadata will be created and how.</td>
<td>The metadata created for all of the project's datasets {% if dmp_initial %}will fulfil{% else %}fulfilled{% endif %}
the Grant Agreement’s requirement for a minimum set of metadata about:
{% render_value_inline_list 'project/dataset/metadata' %}.</td>
</tr>
<tr id="Q09">
<td>9 Will search keywords be provided in the metadata to optimise the possibility for discovery and then potential re-use?</td>
<td>Yes, the following search keywords {% if dmp_initial %}will be{% else %}were{% endif %} provided in the metadata
to optimise the discovery and potential re-use of the deposited datasets:
{% render_value_inline_list 'project/dataset/metadata/search_keywords' %}.</td>
</tr>
<tr id="Q10">
<td>10 Will metadata be offered in such a way that it can be harvested and indexed?</td>
<td>{% render_value_inline_list 'project/dataset/metadata/harvesting' %}</td>
</tr>
</tbody></table>
</div>
<div id="2.2"><h3>Making data accessible</h3>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="2.2a"><td><b>Repository:</b></td></tr>
<tr id="Q11">
<td>11 Will the data be deposited in a trusted repository?</td>
<td>The data and associated metadata, documentation and code
{% if dmp_initial %}will be deposited{% else %}were made accessible by deposition{% endif %}
in the following trusted open access repository:
{% render_value_inline_list 'project/dataset/preservation/repository' %}
{% if repository_zenodo %}({{ "https://zenodo.org"|urlize }})
{% elif repository_ptb_oar %}{{ "https://oar.ptb.de"|urlize }}{% endif %}</td>
</tr>
<tr id="Q12">
<td>12 Have you explored appropriate arrangements with the identified repository where your data will be deposited?</td>
<td>{% render_value_inline_list 'project/dataset/preservation/repository_arrangements' %}.</td>
</tr>
<tr id="Q13">
<td>13 Does the repository ensure that the data are assigned an identifier? Will the repository resolve the identifier to a digital object?</td>
<td>The chosen repository {% if dmp_initial %}will assign{% else %}assigned{% endif %} the following identifier(s)
to each of the project’s deposited datasets: {% render_value_inline_list 'project/dataset/pids/system' %}.
The repository
{% if 'project/dataset/pids/resolver' %}{% if dmp_initial %}will resolve{% else %}resolves{% endif %}
{% else %}{% if dmp_initial %}will not resolve{% else %}does not resolve{% endif %}
{% endif %} resolve the identifier to a digital object.</td>
</tr>
<tr id="2.2b"><td><b>Data:</b></td></tr>
<tr id="Q14">
<td>14 Will all data be made openly available? If certain datasets cannot be shared (or need to be shared under restricted access conditions), explain why, clearly separating legal and contractual reasons from intentional restrictions.
<small>Note that in multi-beneficiary projects it is also possible for specific beneficiaries to keep their data closed, if opening their data goes against their legitimate interests or other constraints as per the Grant Agreement.</small>
</td>
<td>
<p>All data needed to validate the results presented in scientific publications will be made openly available as the default
unless there is a specific reason not to publish the data.</p>
<p><u>Datasets which cannot be shared</u><br />
Other data {% if dmp_initial %}may{% else %}were{% endif %} be made available on a case-by-case basis if relevant for third parties.<br />
The following data {% if dmp_initial %}will not be{% else %}were not{% endif %} made publicly available:</p>
<ul>{% render_value_list 'project/dataset/sharing/explanation' %}</ul>
The level of data made available {% if dmp_initial %}will also be{% else %}was also{% endif %} considered.
For example, pre-processed data {% if dmp_initial %}will not be{% else %}were not{% endif %} provided {% if dmp_initial %}unless there is a{% else %}as there was no{% endif %} a clear reason for doing so.
</td>
</tr>
<tr id="Q15">
<td>15 If an embargo is applied to give time to publish or seek protection of the intellectual property (e.g. patents), specify why and how long this will apply, bearing in mind that research data should be made available as soon as possible.</td>
<td>
{% if dmp_initial %}
The data used in scientific publications, posters and oral communications {% if dmp_initial %}will be{% else %}were{% endif %} made available for re-use as soon as is reasonably possible.<br />
Some of the data are {% if dmp_initial %}expected to be{% endif %} subject to an embargo period of {% render_value 'project/dataset/preservation/embargo_length' %} months
for the following purpose(s): {% render_value_inline_list 'project/dataset/preservation/embargo_period' %}.
{% else %}
{% for dataset in datasets %}
.....
{% endfor %}
{% endif %}
</td>
</tr>
<tr id="Q16">
<td>16 Will the data be accessible through a free and standardised access protocol?</td>
<td>{% render_value_inline_list 'project/dataset/preservation/access_protocol' %}.</td>
</tr>
<tr id="Q17">
<td>17 If there are restrictions on use, how will access be provided to the data, both during and after the end of the project?</td>
<td>{% render_value_inline_list 'project/dataset/sharing/restrictions_explanation' %}.</td>
</tr>
<tr id="Q18">
<td>18 How will the identity of the person accessing the data be ascertained?</td>
<td>{% render_value_inline_list 'project/dataset/preservation/access_authentication' %}.</td>
</tr>
<tr id="Q19">
<td>19 Is there a need for a data access committee (e.g. to evaluate/approve access requests to personal/sensitive data)?</td>
<td>{% render_value_inline_list 'project/legal_aspects/official_approval/data_access_committee' %}</td>
</tr>
<tr id="2.2c"><td><b>Metadata:</b></td></tr>
<tr id="Q20">
<td>20 Will metadata be made openly available and licenced under a public domain dedication CC0, as per the Grant Agreement? If not, please clarify why. Will metadata contain information to enable the user to access the data?</td>
<td>{% render_value_inline_list 'project/dataset/metadata/license_for_metadata' %}.
{% render_value_inline_list 'project/dataset/metadata/access_info' %}.</td>
</tr>
<tr id="Q21">
<td>21 How long will the data remain available and findable?
Will metadata be guaranteed to remain available after data are no longer available?</td>
<td>The data will remain available and findable for the lifetime of the chosen repository
or, at least, for {% render_value 'project/dataset/preservation/duration' %}.<br />
If data are withdrawn from the repository, the DOI and the URL of the original object are retained.
In case of closure of the repository, best efforts will be made by the repository to integrate all content into suitable alternative institutional and/or subject based repositories.</td>
</tr>
<tr id="Q22">
<td>22 Will documentation or reference about any software be needed to access or read the data be included?<br />
Will it be possible to include the relevant software (e.g. in open source code)?</td>
<td><ul>{% render_value_list 'project/dataset/software_documentation' %}</ul>
{% if dmp_not_initial %}
{% for dataset in datasets %}
{% endfor %}
{% endif %}
</td>
</tr>
</tbody></table>
</div>
<div id="2.3"><h3>Making data interoperable</h3>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q23">
<td>23 What data and metadata vocabularies, standards, formats or methodologies will you follow to make your data interoperable to allow data exchange and re-use within and across disciplines? Will you follow community-endorsed interoperability best practices? Which ones?</td>
<td>The datasets use the trusted repository's basic metadata scheme for bibliographic metadata,
which is compliant with the recommended standards used by DataCite ({{ "https://search.datacite.org/"|urlize }}),
BASE search ({{ "https://www.basesearch.net/"|urlize }}) and OpenAIRE ({{ "https://www.openaire.eu/search"|urlize }}).<br />
For individual datasets, we are using the following discipline-specific vocabularies, standards,
formats, and methodologies:
<ol>{% render_value_list 'project/dataset/metadata/standards' set_index='*' %}</ol>.
</td>
</tr>
<tr id="Q24">
<td>24 In case it is unavoidable that you use uncommon or generate project specific ontologies or vocabularies,
will you provide mappings to more commonly used ontologies?
Will you openly publish the generated ontologies or vocabularies to allow their reuse, refinement or extension?</td>
<td>{% render_value_inline_list 'project/dataset/metadata/mappings' %}.</td>
</tr>
<tr id="Q25">
<td>25 Will your data include qualified references <a href="#Note1">[1]</a> to other data
(e.g. other data from your project, or datasets from previous research)?</td>
<td>{% render_value_inline_list 'project/dataset/metadata/references_to_other_data' %}.</td>
</tr>
</tbody></table>
<div id="Note1" style="font-size:7pt;">
[1] A qualified reference is a cross-reference that explains its intent. For example, "X is regulator of Y" is a much more qualified reference than "X is associated with Y", or "X see also Y".
The goal therefore is to create as many meaningful links as possible between (meta)data resources to enrich the contextual knowledge about the data.
(Source: {{ "https://www.go-fair.org/fair-principles/i3-metadata-include-qualified-references-metadata/"|urlize }})
</div>
</div>
<div id="2.4"><h3>Increase data re-use</h3>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q26">
<td>26 How will you provide documentation needed to validate data analysis and facilitate data re-use<br/>(e.g. readme files with information on methodology, codebooks, data cleaning, analyses, variable definitions, units of measurement, etc.)?</td>
<td>
{% render_value_inline_list 'project/dataset/documentation/where' %}.<br />
Data documentation includes: {% render_value_inline_list 'project/dataset/documentation' %}.
</td>
</tr>
<tr id="Q27">
<td>27 Will your data be made freely available in the public domain to permit the widest re-use possible? Will your data be licensed using standard reuse licenses, in line with the obligations set out in the Grant Agreement?</td>
<td>The data {% if dmp_initial %}will either be{% else %}were{% endif %} licensed
under the {% render_value_inline_list 'project/dataset/sharing/conditions' %}
or a license with equivalent rights as set out in the Grant Agreement.
Users will be required to acknowledge the consortium and the source of the data in any resulting publications.
{% if dmp_not_initial %}
{% for dataset in datasets %}
.....
{% endfor %}
{% endif %}
</td>
</tr>
<tr id="Q28">
<td>28 Will the data produced in the project be useable by third parties, in particular after the end of the project?</td>
<td>{% render_value_inline_list 'project/dataset/sharing/third-parties' %}.
{% if dmp_not_initial %}<br />
Some of the project’s datasets are subject to restrictions on re use:
{% for dataset in datasets %}
.....
{% endfor %}
{% endif %}
</td>
</tr>
<tr id="Q29">
<td>29 Will the provenance of the data be thoroughly documented using the appropriate standards?</td>
<td>{% render_value_inline_list 'project/dataset/provenance/standards' %}.</td>
</tr>
<tr id="Q30">
<td>30 Describe all relevant data quality assurance processes.</td>
<td>Data quality is assured through the following procedures:
<ul>{% render_value_list 'project/dataset/quality_assurance' %}</ul>
</td>
</tr>
<tr id="Q31">
<td>31 Further to the FAIR principles, DMPs should also address research outputs other than data, and should carefully consider
aspects related to the allocation of resources, data security and ethical aspects.</td>
<td>
<p><u>Allocation of resources</u></p>
<p>The estimated costs to make the data and other research outputs FAIR
are {% render_value 'project/costs/metadata/personnel' %} (personnel costs)
and {% render_value 'project/costs/metadata/non_personnel' %} (non-personnel costs)
(see <a href="#Q34">Question 34</a>).
{% render_value_inline_list 'project/costs/preservation/cover_how' %}.<br />
{% render_value_inline_list 'project/dataset/curation/responsible_person/name' %}
{% if dmp_initial %}will also have {% else %}had also {% endif %}
overall responsibility for managing other research outputs
(see <a href="#Q36">Question 36</a>). Where feasible, long-term preservation
{% if dmp_initial %}will be {% else %}was {% endif %}ensured
by depositing the other research outputs in repositories.
{% render_value 'project/preservation/responsible_person/name' %}
{% render_value 'project/preservation/selection_criteria' %}
which other research outputs will be deposited and for how long.</p>
<p><u>Security of other research outputs</u></p>
<p>The following practices are adopted for security and data quality: {% render_value_inline_list 'project/other_research_output/quality_assurance' %}.</p>
<p><u>Ethical aspects</u></p>
<p>
The following sensitive outputs are used in the project: {% render_value_inline_list 'project/other_research_output/sensitive_data_description' %}.<br />
{% render_value 'project/dataset/sensitive_data/documentation' %}.<br />
The project will not share other research outputs with identifiable personal information.
Sensitive information relating to the other research outputs will be collected, separated as soon as possible and kept secure.
</p>
<p>Please also see the information provided in <a href="3">section 1.3</a> below.</p>
</td>
</tr>
</tbody></table>
</div>
<div id="3"><h2>Other research outputs</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q32">
<td>32 In addition to the management of data, beneficiaries should also consider and plan for the management
of other research outputs that may be generated or re-used throughout their projects.<br />
<small>Such outputs can be either digital (e.g. software, workflows, protocols, models, etc.)
or physical (e.g. new materials, antibodies, reagents, samples, etc.).</small></td>
<td>
{% for other_output in other_outputs %}
<b>{{ other_output.value }}:</b>
During the project, they will be stored in {% render_set_value_inline_list other_output 'project/other_research_output/storage_type' %}<br />
After the project, they will be stored in {% render_set_value_inline_list other_output 'project/other_research_output/preservation_repository' %}
and shared under the following conditions: {% render_set_value_inline_list other_output 'project/other_research_output/sharing_conditions' %}<br />
{% if dmp_not_initial %}
{% render_value_inline_list other_output 'project/other_research_output/title' %}<br />
{% endif %}
{{ other_output.preservation_repository.value }}<br />
{{ other_output.sharing_conditions.value }}
{% endfor %}
{% if dmp_not_initial %}
The project generates and re-uses the following types of other research outputs: {% render_value_inline_list 'project/other_research_output/plan' %}
{% for other_output in other_outputs %}
.....
{% endfor %}
{% endif %}
This project {% if dmp_initial %}will only re-use {% else %}only re-used {% endif %}
existing data and will not re-use any other research outputs.
</td>
</tr>
<tr id="Q33">
<td>33 Beneficiaries should consider which of the questions pertaining to FAIR data above
can apply to the management of other research outputs, and should strive to provide sufficient detail
on how their research outputs will be managed and shared, or made available for re-use, in line with the FAIR principles.</td>
<td>As far as possible, the FAIR data approaches specified above
({% render_value_inline_list 'project/other_research_output/fair' %})
will be applied to the management of this project’s other research outputs.
This commitment will be met by {% render_value_inline_list 'project/other_research_output/quality_assurance' %}
in line with the requirements of the project’s consortium agreement
(see the answer to <a href="#Q32">Question 32</a> for further details).
</td>
</tr>
</tbody></table>
</div>
<div id="4"><h2>Allocation of resources</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q34">
<td>34 What will the costs be for making data or other research outputs FAIR in your project (e.g. direct and indirect costs related to storage, archiving, re-use, security, etc.)?</td>
<td>The estimated costs to make the data and other research outputs FAIR (findable, accessible, interoperable and reusable)
are {% render_value 'project/costs/metadata/personnel' %} (personnel costs)
and {% render_value 'project/costs/metadata/non_personnel' %} (non-personnel costs).
These costs have been kept to a minimum by using a free repository
and by making only relevant data and other outputs FAIR.</td>
</tr>
<tr id="Q35">
<td>35 How will these be covered?<br />
<small>Note that costs related to research data/output management are eligible as part of the European Partnership on Metrology grant (if compliant with the Grant Agreement conditions).</small>
</td>
<td>{% render_value_inline_list 'project/costs/preservation/cover_how' %}.</td>
</tr>
<tr id="Q36">
<td>36 Who will be responsible for data management in your project?</td>
<td>{% render_value_inline_list 'project/dataset/curation/responsible_person/name' %}
{% if dmp_initial %}will also have{% else %}had{% endif %} overall responsibility for research data management.
They are responsible for coordinating updates to the data management plan and for organising data backup and storage, data archiving and for depositing the data within the repositories.</td>
</tr>
<tr id="Q37">
<td>37 How will long term preservation be ensured? Discuss the necessary resources to accomplish this (costs and potential value, who decides and how, what data will be kept and for how long).</td>
<td>
Long-term preservation will be ensured by depositing the data within repositories.
There are no costs associated with the presevation of the data in these repositories.
<br />
{% render_value 'project/dataset/preservation/longterm_value' %}<br />
{% render_value_inline_list 'project/dataset/curation/responsible_person/name' %}
will decide on what data will be kept and how long. The data selection will take place
{% render_value 'project/preservation/selection_criteria' %}.
</td>
</tr>
</tbody></table>
</div>
<div id="5"><h2>Data security</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q38">
<td>38 What provisions are or will be in place for data security (including data recovery
as well as secure storage/archiving and transfer of sensitive data)?</td>
<td>
<p><u>Data recovery and secure storage</u></p>
<p>During the project, data are stored on {% render_value_inline_list 'project/dataset/storage/type' %}.<br />
After the end of the project, deposition in the chosen repository will provide additional security,
as it has multiple replicas on a distributed file system which is backed up on a nightly basis.</p>
<p><u>Transfer of sensitive data</u></p>
<ul>{% render_value_list 'project/dataset/data_security/transfer' %}</ul>
</td>
</tr>
<tr id="Q39">
<td>39 Will the data be safely stored in trusted repositories for long-term preservation and curation?</td>
<td>Yes, the data will be safely stored on the chosen open access repository.
{% render_value_inline_list 'project/dataset/preservation/repository_information' %}.</td>
</tr>
</tbody></table>
</div>
<div id="6"><h2>Ethical aspects</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q40">
<td>40 Are there, or could there be, any ethics or legal issues that can have an impact on data sharing?<br />
<small>These can also be discussed in the context of the ethics review. If relevant,
include references to ethics report(s) and the ethics section in the Annex 1.</small>
</td>
<td>
There are issues that might impact on data sharing:
<ul>{% render_value_list 'project/dataset/sensitive_data/other/description' %}</ul>
{% render_value 'project/dataset/sensitive_data/documentation' %}.
</td>
</tr>
<tr id="Q41">
<td>41 Will informed consent for data sharing and long-term preservation be included in questionnaires dealing with personal data?</td>
<td>Informed consent will be requested {% render_value_inline_list 'project/dataset/sensitive_data/personal_data/consent/extent' %}.<br />
{% render_value_inline_list 'project/dataset/data_security/transfer' %}.</td>
</tr>
</tbody></table>
</div>
<div id="7"><h2>Other issues</h2>
<table border="1"><colgroup><col width="30%"><col width="70%"></colgroup><thead><tr><th><b>Questions</b></th><th><b>Answers</b></th></tr></thead><tbody>
<tr id="Q42">
<td>42 Do you, or will you, make use of other national/funder/sectorial/departmental procedures for data management?
If yes, which ones? (Please list and briefly describe them.)</td>
<td>Research data management is compliant with:
<ul>{% render_value_list 'project/additional_rdm_policy/requirements' %}</ul>
</td>
</tr>
</tbody></table>
</div>
{% if dmp_not_initial %}
<div id="Annex"><h2>Annex: overview of the datasets</h2>
<p>The project has generated 38 datasets so far. These have been grouped
by topic / method / format / type as described below.
The answers to the questions in the DMP relate to the here defined groups.</p>
<ul>
{% for dataset in datasets %}
<li>Dataset / group {{ dataset.value }}: {{ dataset.description.value }}</li>
{% endfor %}
</ul>
</div>
{% endif %}
<div><h1>Open Science: research data management</h1>
<table border="1">
<colgroup><col width="50%"><col width="10%"><col width="40%"></colgroup><thead>
<tr><th><b>Statement</b></th><th><b>Put an &#10005; in the box to confirm</b></th><th><b>Or, list any exceptions to this</b></th></tr></thead><tbody>
<tr>
<td>All participants have adhered to the requirements of the project’s GA and CA with respect to open science: research data management (GA Article 17 and its Annex 5) for this reporting period</td>
<td style="text-align:center;">&#9744;</td>
<td></td>
</tr>
</tbody></table>
</div>
<div id="lastPage" style="page-break-before:always;">
<img src="https://enterprise.ptb.de/metrology-rdm/fileadmin/documents/metrology-rdm/images/document_control_page.png" alt="Document control page" width="100%">
</div>
</body></template>
</view>
</rdmo>