Skip to content

Commit 4bbf0d8

Browse files
Apply suggestions from code review
1 parent ee0c51c commit 4bbf0d8

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

paper.tex

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -397,10 +397,8 @@ \subsection{Module 5: Create a Network of Institutional Partners}%
397397
With the dedicated help of RSEs, research software can be enabled to be added to the organisational bibliography, facilitating internal reporting.
398398
At the same time, through collaboration with the library, the RSE group can address the first two letters of FAIR:\@ Findability and Accessibility.
399399

400-
Topics of RSE and RDM have noticeable similarities.
401-
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.
402-
Both RSE and RDM units provide research-oriented services that are supporting digital research.
403-
They also need to collaborate directly because research software both consumes and produces research data.
400+
Both RSE and RDM units provide research-oriented services that are supporting digital research, covering different aspects of the research cycle.
401+
They need to collaborate directly because research software both consumes and produces research data.
404402
Requests for support on digital research therefore often touch both aspects, RSE and RDM\@.
405403
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.
406404
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.

0 commit comments

Comments
 (0)