Skip to content

Commit ee0c51c

Browse files
committed
reformulate a little more
1 parent ebe81b3 commit ee0c51c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

paper.tex

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -401,8 +401,8 @@ \subsection{Module 5: Create a Network of Institutional Partners}%
401401
While software development does often require different solutions to data management, collaboration between an RSE unit and an \textbf{RDM unit} will be very close in practice.
402402
Both RSE and RDM units provide research-oriented services that are supporting digital research.
403403
They also need to collaborate directly because research software both consumes and produces research data.
404-
Requests for support on digital research often touch both aspects, RSE and RDM\@.
405-
Thus, often a close collaboration between RSE and RDM 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.
404+
Requests for support on digital research therefore often touch both aspects, RSE and RDM\@.
405+
Thus, a close collaboration between RSE and RDM 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.
406406
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.
407407

408408
Some research institutions might host a dedicated \textbf{HPC group}, maybe even independent of the computing centre.

0 commit comments

Comments
 (0)