Merge pull request #59 from DE-RSE/refs

Add various references

Author: dokempf

paper.tex

@@ -96,7 +96,7 @@ \section{Motivation}
 
 \subsection{Tasks}
 
-One of the services a centralized RSE department likely will provide is training to improve the often low-quality code developed by beginners [REF low-quality].
+One of the services a centralized RSE department likely will provide is training to improve the often low-quality code developed by beginners ~\autocite{Ostlund2023}.
 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}.
 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. They reported a remarkable increase in software quality, better grant applications, less brain drain and overall employee satisfaction levels~\autocite{schimavoigt2023}.
 The demand for such services appears to be ever-increasing.
@@ -151,8 +151,10 @@ \subsection{International Comparison and Current Developments}
 This allocated money can then be utilized to delegate/dispatch a central RSE person or group into a research project for a few weeks or months as necessary.
 
 We welcome that the latest DFG grant application templates require discussion of both, data \textbf{and} software management (in line with their GWP guidelines~\autocite{dfg_gsp}).
-%We also see the first grant applications [REF welcome trust? or others] requiring Software Management Plans (SMP).
+%We also see the first grant applications [REF wellcome trust (seems to require an OutputMP that includes software, but only how/when it will be published, not how it will be created/maintained)? or others] requiring Software Management Plans (SMP).
 In addition, dedicated Data Management Plans (DMP) have become mandatory in several funding calls (e.g., ...) and we expect to see a similar development for SMPs in the future. (There have been funding calls in the UK that required a SMP. [no ref?]) 
+% See https://www.forschungsdaten.org/index.php/Data_Management_Pl%C3%A4ne#Anforderungen_von_F%C3%B6rderorganisationen
+% See https://www.researchdata.uni-jena.de/information/datenmanagementplan
 
 Policies for research software management and guidelines involving responsible research practices detailing software handling are the precursors for a research software engineering environment.
 See for example position papers by the Helmholtz Open Science Office~\autocite{Helmholtz2019a,Helmholtz2019b},
@@ -241,16 +243,17 @@ \subsection{Module 1: Foster a Network of RSEs}
 \subsection{Module 2: Consultation Services}
 \label{sec:consultation}
 
-With the majority of researchers being self-taught programmers [REF], there is a huge demand for expertise on how to develop better research software.
-Here, "better" can refer to a number of quality metrics such as correctness, reproducibility, maintainability, extendability, usability, portability, interoperability, performance or scalability [REF].
+With the majority of researchers being self-taught programmers~\autocite{Carver2013}, there is a huge demand for expertise on how to develop better research software.
+Here, "better" can refer to a number of quality metrics such as correctness, reproducibility, maintainability, extendability, usability, portability, interoperability, performance or scalability~\autocite[Chapter 16]{Schulmeyer2008}.
+
 In order to raise the quality standards for research that is based on research software, it is of great importance for research institutions to provide access to such expertise with a low entry barrier.
 The hub is a natural place to provide this central service.
 There exists a number of scenarios where RSE consultation services differ strongly in scale and format.
 We mention a few of these in the following.
 
 "One Off" consultations on any research software related aspect that are open to researchers of all career levels are
 a great introduction to the hub's RSE services and are offered by almost all RSE departments already established [REF].
-Depending on the demand, these consultations can either be by appointment or in a more structured format where you book an appointment from available dates (e.g. University of Sheffield's "Code Clinic" [REF]) .
+Depending on the demand, these consultations can either be by appointment or in a more structured format where you book an appointment from available dates (e.g. University of Sheffield's "Code Clinic" \footnote{At time of publication the appointment form could be access from the front page of the RSE department’s website: \url{https://rse.shef.ac.uk/}} and Friedrich Schiller University’s Digital Research Clinic\footnote{At the time of publication upcoming clinic’s were advertised on the consulting page of the Competence Center For Digital Research’s website: \url{https://www.zedif.uni-jena.de/en/consulting.html}}).
 
 A larger scale format for RSE consultation services could be that a research project regularly (e.g. quarterly or monthly) meets with an RSE in order to coordinate the research software efforts done in the research project.
 This format enables valuable feedback cycles between researchers and RSEs and allows RSEs to guide the project
@@ -294,7 +297,7 @@ \subsection{Module 3: Development Services}
 Examples of topics that would benefit from such expertise pooling are \eg mobile app development and UI/UX development.
 
 RSE departments that offer development services at all scales have proven to be a success story at many research institutions and have rapidly grown in size due to the influx of third party funding.
-Notable examples are \eg Manchester [REF], Notre-Dame [REF], STANFORD, Princeton~\autocite{Cosden2022a}.
+Notable examples are \eg Manchester~\autocite{Sinclair2022}, Notre-Dame [REF], Stanford~\autocite{Stanford2023}, Princeton~\autocite{Cosden2022a}.
 
 [SuccessStory]
 Founded in January 2017, the Research Computing department of Princeton University has experienced a tremendous growth from the initial two FTEs to a total of 18 FTEs in the span of five years~\autocite{Cosden2022a}.

positionpaper.bib

@@ -267,3 +267,60 @@ @misc{Barker2024
   copyright = {Creative Commons Attribution 4.0 International}
 }
 
+
+@InProceedings{Ostlund2023,
+  author =       {\"{O}stlund, Linus and Wicklund, Niklas and Glassey, Richard},
+  title =        {It's Never too Early to Learn About Code Quality: A
+                  Longitudinal Study of Code Quality in First-year Computer
+                  Science Students},
+  year =         2023,
+  booktitle =    {Proceedings of the 54th ACM Technical Symposium on Computer
+                  Science Education V. 1},
+  series =       {SIGCSE 2023},
+  publisher =    {Association for Computing Machinery},
+  isbn =         9781450394314,
+  pages =        {792–798},
+  doi =          {10.1145/3545945.3569829},
+  url =          {https://doi.org/10.1145/3545945.3569829}
+}
+
+
+@Article{Carver2013,
+  author =       {Carver, Jeffrey and Heaton, Dustin and Hochstein, Lorin and
+                  Bartlett, Roscoe},
+  title =        {Self-perceptions about software engineering: A survey of
+                  scientists and engineers},
+  journal =      {Computing in Science \& Engineering},
+  year =         2013,
+  volume =       15,
+  number =       1,
+  pages =        {7--11},
+  publisher =    {IEEE}
+}
+
+
+@Book{Schulmeyer2008,
+  author =       {Schulmeyer, Gordon},
+  title =        {Handbook of Software Quality Assurance, Fourth Edition},
+  year =         2008,
+  publisher =    {Artech House},
+  isbn =         {978-1-59693-186-2}
+}
+
+
+@Online{Sinclair2022,
+  author =       {Gillian Sinclair},
+  title =        {Research Software Engineering},
+  year =         2022,
+  url =          {https://research-it.manchester.ac.uk/services/research-software-engineering/},
+  urldate =      {2024-04-12}
+}
+
+
+@Online{Stanford2023,
+  author =       {Stanford University IT},
+  title =        {Research Software Engineering Services},
+  year =         2023,
+  url =          {https://uit.stanford.edu/node/27566},
+  urldate =      {2024-04-12}
+}