Skip to content

Commit 13979e3

Browse files
committed
rewrite FDM-RDM group interplay
1 parent 2bb212d commit 13979e3

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

paper.tex

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -356,8 +356,10 @@ \subsection{Create a Network of Institutional Partners}
356356

357357
Topics of RSE and RDM do have noticeable similarities.
358358
Thus, while software often does require different solutions than data, collaboration between an RSE department and an FDM department will in practice be really close.
359-
In contrast to most other organisations mentioned within this section,
360-
the requirements on their respective members and members of an RSE group are so similar that organisations might consider focus on one merged RSE \& FDM department.
359+
The main reasons for that are that both provide services that are inherently research-oriented and that both deal with the digital side of research.
360+
Requests by researchers in that direction often touch both aspects, RSE and RDM.
361+
Thus, often a close collaboration between RSE and FDM groups helps everyone: both RSE and RDM groups by being able to offer a more comprehensive service than when working alone, as well as the researcher, who benefits from receiving this single coordinated service, instead of dealing with two independent entities.
362+
The question whether RSE and RDM should be located in two separate groups or should be combined in one common group is intentionally left open, as the answer depends on local, pre-existing circumstances.
361363

362364
\subsection{RSE Infrastructure Provisioning}
363365
\label{sec:infrastructure}

0 commit comments

Comments
 (0)