-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathUNIS_dmp.tex
146 lines (105 loc) · 9.62 KB
/
UNIS_dmp.tex
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
\documentclass[a4paper,english, 11pt]{article}
\usepackage[a4paper,inner=2.5cm,outer=2.5cm,top=2.5cm,bottom=2.5cm,pdftex]{geometry}
\usepackage{graphicx}
\usepackage{titling}
\usepackage[colorlinks = true,
linkcolor = blue,
urlcolor = blue,
citecolor = blue,
anchorcolor = blue]{hyperref}
\usepackage{enumerate}
\usepackage{fancyhdr}
\usepackage{lastpage}
\usepackage{booktabs} % For better table formatting
\pagestyle{fancy}
\hypersetup{colorlinks=true,linkcolor=blue, linktocpage}
\newcommand{\emailme}{\href{mailto:[email protected]}{[email protected]}}
% header
\pagestyle{fancy}
\fancyhf{}
\fancyhfoffset[L]{1cm} % left extra length
\fancyhfoffset[R]{1cm} % right extra length
\rhead{\today}
\lhead{\bfseries UNIS data management plan}
% footer
\rfoot{page \thepage\ of \pageref*{LastPage}}
% title
\title{UNIS data management plan}
%\date{\today\\v1.0}
\date{August 18, 2023 \\v1.0}
%\author{Luke Marsden (\emailme)}
\pretitle{%
\begin{center}
\LARGE
\includegraphics[width=9cm]{unis_logo.png}\\[\bigskipamount]
}
\posttitle{\end{center}}
\begin{document}
\maketitle
\begin{table}[b]
\centering
\caption{Revision history}
\begin{tabular}{cccc}
\toprule
Version & Date & Comment & Responsible \\
\midrule
1 & 2023-08-18 & Approved by the LG & Luke Marsden \\
0.2 & 2023-07-20 & Sent to the LG for approval & Luke Marsden \\
0.1 & 2023-06-05 & Initial draft & Luke Marsden \\
\bottomrule
\end{tabular}
\end{table}
\newpage
\tableofcontents
\newpage
\section{Admin details}
\label{s:admin}
Data management plan of the University Centre in Svalbard (UNIS). UNIS is funded primarily by Kunnskapsdepartementet (KD), with other income sources including overhead income and infrastructure rental.
This document was approved by the UNIS leadership group (LG) on 18. August 2023 and will be reviewed annually by the LG and data managers at UNIS.
\section{Data summary}
\label{s:data}
Situated in Longyearbyen, Svalbard, students and staff at UNIS have easy access to a phenomenal natural laboratory in the high Arctic.
They have the opportunity to collect important data that can be of interest to those who are less conveniently situated.
This data management plan is applicable only to internal UNIS activities. This involves student courses and internally funded research and projects. These data are owned by UNIS, and it is primarily the responsibility of UNIS to ensure that suitable data are published by staff and students who work for UNIS.
UNIS would like to encourage those involved in external projects involving UNIS to develop their own data management plans specific to their projects. This can be more specific to the timeline of the project and the data collected. However, one can refer to the UNIS data management plan within their own data management plans where suitable.
\subsection{Types and formats of data generated/collected}
\label{ss:datatypes}
UNIS comprises 4 scientific departments - arctic geology, arctic geophysics, arctic technology and arctic biology. Staff and students at UNIS collect a wide range of data within these disciplines.
Concerning which file formats to use when publishing data, UNIS follows the detailed recommendations outlined in the \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SDMS_Interoperability_Guidelines.pdf}{SDMS Interoperability Guidelines} - section `File Formats'.
In brief, self explaining file formats (e.g. NetCDF, Darwin Core Archive) will be used. NetCDF itself is not self describing, so the Climate and Forecast Convention will be used as a semantic and structural standard. Adding the \href{https://wiki.esipfed.org/Attribute_Convention_for_Data_Discovery_1-3}{NetCDF Attribute Convention for Dataset Discovery} as global attributes embeds full discovery
metadata (e.g. originator/PI, constraints etc.) in the file. SIOS and therefore UNIS recommends using the requirements list at the \href{https://adc.met.no/node/4}{Arctic Data Centre} as a minimum. Additional global attributes can be added as desired.
When it is not possible to encode data as NetCDF-CF or Darwin Core Archive, data can be published in a non-proprietary file format that is easy to consume for users (without specific software) accompanied by a detailed product manual (in PDF format).
Please refer to the \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SDMS_Interoperability_Guidelines.pdf}{SDMS Interoperability Guidelines} for more details and explanations.
\section{FAIR data}
\label{s:fair}
UNIS is committed to publishing data that are Findable, Accessible, Interoperable and Reusable (FAIR). UNIS follows the recommendations of the \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SIOS_Data_Management_Plan.pdf}{SIOS Data Management Plan} (section 3) on how to make data FAIR. Exceptions, additions and specifications are listed below in similarly named subsections to in the SIOS data management plan.
\subsection{Making data findable, including provisions for metadata}
\label{ss:findable}
All UNIS data will be made available via the SIOS data access portal (\url{https://sios-svalbard.org/metsis/search}), as discussed in \href{s:resources}{Allocation of resources}.
\subsection{Making data openly accessible [fair data]}
\label{ss:accessible}
The basic principle is free and open access data as soon as possible.
In some cases, embargo periods can exist to delay the publishing of data. This may vary from dataset to dataset, depending on the time required from dataset to dataset. Embargo periods should be requested on a case by case basis to the UNIS leadership group with some exceptions:
\begin{itemize}
\item Masters students are entitled to a maximum embargo period of 2 years before they are published, but must be published before the student finishes their Masters project.
\item PhD students are entitled to a maximum embargo period of 4 years before they are published, but must be published before the student finishes their PhD project.
\item Whether data from undergraduate student courses should be published and when should be determined on a case by case basis.
\end{itemize}
In all of the cases above, everyone is encouraged to publish their data as soon as technically possible regardless.
\section{Allocation of resources}
\label{s:resources}
Currently, there is no overview of the total costs for making UNIS data FAIR.
All data relevant to Svalbard should be made available via the SIOS data access portal (\url{https://sios-svalbard.org/metsis/search}). Priority should therefore be given to publish to data centres that contribute to the SIOS data access portal. These are listed in the section `Allocation of resources' of the \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SIOS_Data_Management_Plan.pdf}{SIOS Data Management Plan}.
Of these data centres, Norwegian data centres should be prioritised. NIRD (the National Infrastructure for Research Data) host a data centre funded by the Research Council of Norway (NIRD Research Data Archive - \url{https://archive.norstore.no/}). This is not attached to any individual research institution and therefore may be particularly suitable for many UNIS datasets. However, other data centres that contribute to SIOS can be used if collaborating with employees of other research institutions or if a data centre offers preferable functionality(s).
UNIS endorses the work done by the Norwegian Scientific Data Network (NorDataNet - \url{https://www.nordatanet.no/en}) to make it easier for people to publish FAIR data. It is possible to publish CF-NetCDF files to NIRD Research Data Archive through NorDataNet. Using this method, the global attributes used in the CF-NetCDF file are used to populate the discovery metadata on the landing page of the dataset. One therefore does not have to enter this information manually. NorDataNet also provides access to tools for validating CF-NetCDF files, converting ASCII files to CF-NetCDF, spreadsheet templates for CF-NetCDF and Darwin Core Archives and guidelines on what metadata should be included.
Data published to a data centre that does not contribute to the SIOS data access portal must be linked manually using a metadata collection form hosted by SIOS (\url{https://sios-svalbard.org/metadata-collection-form}).
\section{Data security}
\label{s:security}
As mentioned in section \ref{s:resources}, UNIS data should be published in data centres that contribute to the SIOS data access portal. Therefore, as mentioned in the `Data security' section of the \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SIOS_Data_Management_Plan.pdf}{SIOS Data Management Plan}, the security of published UNIS datasets relies on the security implemented by these data centres.
\section{Ethical aspects}
\label{s:ethics}
Ethical aspects are handled according to the UNIS Data Policy. Generally, UNIS is not handling sensitive research data, but UNIS follows the principle of ``as open as possible, as closed as necessary''. All data will be classified in two main categories; i) non-sensitive, and ii) sensitive (personal data and/or data that can be used for an unintended purpose).
\section{Other}
\label{s:other}
The UNIS data management plan is, as mentioned above, based on the existing \href{https://sios-svalbard.org/sites/sios-svalbard.org/files/common/SIOS_Data_Management_Plan.pdf}{SIOS Data Management Plan}. It has been modified to suit the needs of UNIS. Wherever possible, this document refers to the SIOS data management plan instead of duplicating text. Therefore, the recommendations provided in the UNIS data management plan will evolve as the SIOS data management plan evolves.
\end{document}