You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: paper.tex
+21-21Lines changed: 21 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ \section{Introduction}
55
55
These actions are very diverse and so are the environments they are performed in.
56
56
This position paper focuses on groups of research software engineers that provide their services for an entire research organisation or at least a substrancial part of it.
57
57
58
-
We advocate the establishment and support of dedicated, central RSE groups in German research organizations, with clearly defined tasks, contact points, and, in particular, sustained funding, for the benefit of all researchers in their organisation.
58
+
We advocate the establishment and support of dedicated, central RSE groups in German research organisations, with clearly defined tasks, contact points, and, in particular, sustained funding, for the benefit of all researchers in their organisation.
59
59
We provide an overview of the various task these teams have and discuss potential realization strategies, learning from already existing examples of such an RSE unit.
60
60
61
61
Before we motivate the topic of this position paper further, we first introduce the terminology used throught this work.
@@ -83,11 +83,11 @@ \section{Introduction}
83
83
role as an alternative to a traditional research role because they enjoy and wish to focus
84
84
on the development of research software.\\
85
85
\textbf{Researchers:}\\
86
-
We refer by researchers to all others involved in research or in research supporting organizations such as \eg{} libraries,
86
+
We refer by researchers to all others involved in research or in research supporting organisations such as \eg{} libraries,
87
87
hence those that are at most sporadically performing RSE actions.
88
88
89
89
Furthermore, we will use the general term \textbf{RSE Hub} for the central RSE team throughout this paper.
90
-
These RSE Hubs can take the form of, e.g., full RSE units, smaller RSE groups, Open Source Program Office (OSPOs), virtually across multiple units or combined under one single leader, depending on the evironment of the particular research organization under consideration.
90
+
These RSE Hubs can take the form of, e.g., full RSE units, smaller RSE groups, Open Source Program Office (OSPOs), virtually across multiple units or combined under one single leader, depending on the evironment of the particular research organisation under consideration.
91
91
All of these implementations are considered here, taking into account the large variety of research environments in Germany.
92
92
93
93
\section{Motivation}
@@ -97,8 +97,8 @@ \section{Motivation}
97
97
\textit{Better Software, Better Research}\\(Mission statement of the UK Software Sustainability Institute)
98
98
\end{quotation}
99
99
100
-
In this chapter, we motivate dedicated RSE groups in German research organizations.
101
-
Several stakeholder perspectives are discussed and supported by (inter)national examples, including that of RSEs within RSE groups, RSEs embedded in research groups, Researchers in need of RSE resources, organizational management and that of funders.
100
+
In this chapter, we motivate dedicated RSE groups in German research organisations.
101
+
Several stakeholder perspectives are discussed and supported by (inter)national examples, including that of RSEs within RSE groups, RSEs embedded in research groups, Researchers in need of RSE resources, organisational management and that of funders.
102
102
103
103
We will draw parallels to research data here, because both, data and software, play a fundamental role in all of the research.
104
104
Over the past decades, Research Data Management (RDM) has evolved into a topic of national interest with NFDI consortia for all disciplines and a research data law.
@@ -108,7 +108,7 @@ \section{Motivation}
108
108
Due to the similar nature of both, data and software, and their importance in today's digital research, it is reasonable to expect a similar trajectory in the development of research software as a topic.
109
109
%such output has become more important over the last two decades. Since research software can be considered valuable research output as well, we expect a similar trajectory for software.
110
110
%gh training researchers, the reusability through data repositories and to avoid duplication of effort.
111
-
%For over a decade, research funders and organizations made a significant effort to establish RDM and teams around it, for example the Utrecht University Research Data Management Support~\autocite{UtrechtRDM}, University of Stuttgart FoKUS team~\autocite{Boehlke2024} or TUBS.researchdata~\autocite{Grunwald2022} at TU Braunschweig.
111
+
%For over a decade, research funders and organisations made a significant effort to establish RDM and teams around it, for example the Utrecht University Research Data Management Support~\autocite{UtrechtRDM}, University of Stuttgart FoKUS team~\autocite{Boehlke2024} or TUBS.researchdata~\autocite{Grunwald2022} at TU Braunschweig.
112
112
%We assume that research software will follow a similar trajectory.
113
113
%\footnote{For arguments when research software is unlike data, see \autocite{Lamprecht2020}.}
114
114
@@ -119,7 +119,7 @@ \section{Motivation}
119
119
\subsection{Tasks}
120
120
121
121
One of the services a centralized RSE unit likely will provide is training to improve the often low-quality code developed by beginners~\autocite{Ostlund2023}.
122
-
Examples of organizational training efforts are the Helmholtz HIFIS group [https://events.hifis.net/category/4/], the Scientific Software Center in Heidelberg [https://www.ssc.uni-heidelberg.de/en], the Competence Center Digital Research in Jena (zedif: [https://www.zedif.uni-jena.de/en/]), and the SURESOFT workshops series in Braunschweig~\autocite{SURESOFTLink, Blech2022}.
122
+
Examples of organisational training efforts are the Helmholtz HIFIS group [https://events.hifis.net/category/4/], the Scientific Software Center in Heidelberg [https://www.ssc.uni-heidelberg.de/en], the Competence Center Digital Research in Jena (zedif: [https://www.zedif.uni-jena.de/en/]), and the SURESOFT workshops series in Braunschweig~\autocite{SURESOFTLink, Blech2022}.
123
123
Another national pioneer is the Göttingen State and University Library which set up a group of RSEs offering – besides training – services like data modeling and visualization, digital editions, portal development and more.
124
124
They reported a remarkable increase in software quality, better grant applications, less brain drain and overall employee satisfaction levels~\autocite{schimavoigt2023}.
125
125
The demand for such services appears to be ever-increasing.
@@ -137,7 +137,7 @@ \subsection{Structure}
137
137
This is comparable to commercial/industry R\&D departments, where key software architects and developers establish a knowledge hub and consult with as many projects as necessary [REF].
138
138
Subject matter experts like software architects, database administrators and other tooling specialists are organized centrally and share their knowledge by consulting with decentralized projects.
139
139
It makes economically sense to organise such personel as cost-effective as possible since not every project can afford or needs such RSE FTEs.
140
-
Most academic research organizations have established centralized tooling, e.g.\ storage or High-Performance-Computing\ (HPC), but only a few consider software development and consultancy a relevant service yet.
140
+
Most academic research organisations have established centralized tooling, e.g.\ storage or High-Performance-Computing\ (HPC), but only a few consider software development and consultancy a relevant service yet.
141
141
RSE units act as knowledge hubs in a network of academic developers within an organisation~\autocite{Elsholz2006}.
142
142
This enables the embedded experts to maintain in-depth knowledge and to assess current trends and developments, both in research as well as technology.
143
143
@@ -159,18 +159,18 @@ \subsection{Structure}
159
159
160
160
The Carpentries~\autocite{Carpentries} exemplify a similar success story [REF SuccessStory Carpentries https://carpentries.org/testimonials/].
161
161
Requests or suggestions for even more training show the need for such services.
162
-
RSE services which benefit all disciplines/departments may represent a unique selling point for organizations competing for the brightest minds.
162
+
RSE services which benefit all disciplines/departments may represent a unique selling point for organisations competing for the brightest minds.
163
163
See the examples from leading universities above.
164
164
165
-
Given that RDM training or coordination is a centralized effort in most organizations, the time has come to implement a similar structure for research software services.
165
+
Given that RDM training or coordination is a centralized effort in most organisations, the time has come to implement a similar structure for research software services.
166
166
Such a group may extend or include RDM or collaborate with such service teams.
167
167
See the Vision and Realization sections below for more details.
168
168
169
169
\subsection{International Comparison and Current Developments}
170
170
171
171
172
172
Selected research institutions in the UK have pioneered the deployment of RSEs into research projects~\autocite{Crouch2013}.
173
-
The successful establishment of such staff is a role model for similar academic organizations worldwide.
173
+
The successful establishment of such staff is a role model for similar academic organisations worldwide.
174
174
A range of already-existing RSE units can be seen in this map: https://society-rse.org/community/rse-groups/
175
175
176
176
In the UK, for example, almost all grant applications include software development in their budget.
@@ -215,7 +215,7 @@ \subsection{Towards a Thriving Future}
215
215
216
216
High-quality software is likely to be published, cited, and reused.
217
217
Better software is assumed to have a much longer life cycle and may be more evolvable or extensible due to better code quality and architectural decisions that ease reuse.
218
-
This will benefit researchers, organizations, funders, and society.
218
+
This will benefit researchers, organisations, funders, and society.
219
219
220
220
%Necessary software management activities like (git-based) version control are assumed to improve collaboration among researchers.
221
221
@@ -225,15 +225,15 @@ \subsection{Towards a Thriving Future}
225
225
% move to vision
226
226
%Software development and management training efforts included in the "studium generale" (or similar education strategies) will further the knowledge of students and early career researchers.
227
227
228
-
%In contrast, organizations lacking such RSE knowledge need to purchase professional support - in the industry often realized via consulting.
228
+
%In contrast, organisations lacking such RSE knowledge need to purchase professional support - in the industry often realized via consulting.
229
229
%Academic research hardly has the resources to compete for effective consulting.
230
230
%Academic research is assumed to aim for sovereignty and independence of third-party providers.
231
231
232
232
\section{Vision}%
233
233
\label{sec:vision}
234
234
In the following, we describe our vision of central RSE units at research institutions in Germany.
235
235
As these institutions include universities, other colleges, as well as large associations like Max-Planck, Helmholtz, Fraunhofer or Leibniz,
236
-
they show a wide variety in organizational structure as well as internal scientific diversity.
236
+
they show a wide variety in organisational structure as well as internal scientific diversity.
237
237
Thus, there can be no single optimal concept of such an RSE unit for all research institutions in Germany.
238
238
We instead describe modular components that can be mixed and matched based on the respective local environment.
239
239
@@ -247,7 +247,7 @@ \subsection{Module 1: Foster a Network of RSEs}%
247
247
\label{sec:network}
248
248
249
249
One of the core responsibilities of an RSE unit is to act as a coordinator of RSE activities within the institution.
250
-
At virtually every academic institution there are employees that assume at least part-time the role of an RSE, with tasks within only a part of that organization.
250
+
At virtually every academic institution there are employees that assume at least part-time the role of an RSE, with tasks within only a part of that organisation.
251
251
These RSEs typically work isolated from similar RSEs in different groups, within the same institution.
252
252
A central RSE unit provides a condensation core and connects RSEs in spokes with each other and with the ones at the hub.
253
253
@@ -364,9 +364,9 @@ \subsection{Module 5: Create a Network of Institutional Partners}%
364
364
However, their coverage of RSE-related needs of researchers is often limited and their main responsibilities, even as diverse as they are across institutions, typically lie elsewhere.
365
365
While this is one of the main arguments for the creation of dedicated RSE units, it also shows the necessity for an RSE unit to closely interact with its respective partners.
366
366
367
-
In the following, we describe groups or units that can typically be found within academic organizations,
367
+
In the following, we describe groups or units that can typically be found within academic organisations,
368
368
what usually their focus is and how we envision collaborations with an RSE unit.
369
-
However, note that as research organizations can differ widely from one another, so can the tasks and even existence of the entities below.
369
+
However, note that as research organisations can differ widely from one another, so can the tasks and even existence of the entities below.
370
370
Arguments and conclusions below have to be adapted to specific circumstances when applying them to specific environments.
371
371
372
372
All research institutions in Germany do have a \textbf{computing center} of one form or another.
\item It seems natural to allocate ordinary budget positions for RSEs.
508
508
However, particularly at German universities, it is usually impossible to create completely new budget positions and the only feasible way is to rededicate an existing position after its corresponding holder has left.
509
509
Depending on the local circumstances at an institution, this can be a cumbersome and time-consuming process for each such position.
510
-
\item Funding organizations additionally allocate a portion of the direct project funds as overhead, which is typically divided between the institution and the applicant.
510
+
\item Funding organisations additionally allocate a portion of the direct project funds as overhead, which is typically divided between the institution and the applicant.
511
511
We propose using a small percentage of the overhead agglomorated at the institution to permanently finance central RSE positions.
512
512
Assuming a third-party funding income of EUR 50 million annually and a 20\% overhead, EUR 100,000 in permanent funding requirements for one person-year would only account for 1\% of this overhead.
513
513
\item In project applications involving the development of research software, corresponding person-months should be applied for to finance RSE tasks.
514
514
In this way, an applicant can book a fixed number of working hours from the RSE pool and pay for the costs accordingly.
515
515
This model has been successfully implemented at several UK universities.
516
516
In order to scale, it needs to be supported by an institutional policy.
517
517
Large scale collaborative projects can often apply for dedicated technical support positions that align well with the idea of RSE units.
518
-
\item Funding organizations are increasingly recognizing the need for sustainable research software
518
+
\item Funding organisations are increasingly recognizing the need for sustainable research software
519
519
development and are setting up correspondingly designated funding programmes.
520
520
The DFG has already organized three calls for proposals in 2016\footnote{\href{https://www.dfg.de/resource/blob/172674/1bcb181a6451fdac9d94421776b52798/161026-dfg-ausschreibung-forschungssoftware-de-data.pdf}{Nachhaltigkeit von Forschungssoftware}}, 2019\footnote{\href{https://www.dfg.de/de/aktuelles/neuigkeiten-themen/info-wissenschaft/2019/info-wissenschaft-19-44}{Qualitätssicherung von Forschungssoftware durch ihre nachhaltige Nutzbarmachung}}, and 2022\footnote{\href{https://www.dfg.de/en/news/news-topics/announcements-proposals/2022/info-wissenschaft-22-85}{Research Software – Quality Assured and Re-usable}}.
521
521
It is to be expected that even more programs will be launched in the future.
% However, it might be difficult to realize the required reallocation of resources.
534
534
% Another possibility is the pooling of RSE funds from different research departments, which brings its own administrative burden, and is probably not generating long-term positions.
535
535
% To generate these RSE funds it is required to obtain them from external funders like the DFG, a strategy that can be supported by an institutional policy to ask for these.
536
-
% This mixed funding scheme brings us to organizational topics that facilitate the money generation.
536
+
% This mixed funding scheme brings us to organisational topics that facilitate the money generation.
537
537
% From the side of the funding agencies this can be supported by requiring a digital support strategy from proposals similar to RDM plans.
538
538
% If this strategy/policy is followed institution-wide, we believe that a consistent stream of income can be generated that enhances the bare-level support that is generated by the fixed funding from the central budget.
Decision makers at an institution usually require a concept upon which they will decide about the installation of an RSE unit.
566
566
Such a concept should specify the idea of the RSE unit, its responsibilities and offerings as a subset of the nine modules presented in \autoref{sec:vision}, and the resulting benefits for the institution and its researchers.
567
567
568
-
A rather difficult and crucial question can be the localization of the RSE unit within the organizational structure of the institution.
568
+
A rather difficult and crucial question can be the localization of the RSE unit within the organisational structure of the institution.
569
569
A canonical place would be a new subunit of an institutional body close to software,
570
570
training services and computing such as the institution's IT department, the computing center or the library.
571
571
Since most institutions already have an RDM unit, it seems natural to add the RSE unit as a parallel structure.
0 commit comments