Add missing citations

bibliography.bib

@@ -532,6 +532,19 @@ @Online{BluefieldIBMBadges
   urldate = {2023-07-03},
 }
 
+@Article{Boehlke2024,
+  author    = {Boehlke, Fabian},
+  title     = {Das {K}ompetenzzentrum f{\"u}r {F}orschungsdaten ({FoKUS}) der {U}niversit{\"a}t {S}tuttgart und die {B}er{\"u}cksichtigung geisteswissenschaftlicher {F}orschungsdaten},
+  journal   = {API Magazin},
+  year      = {2024},
+  volume    = {5},
+  number    = {1},
+  month     = jan,
+  issn      = {2699-6693},
+  doi       = {10.15460/apimagazin.2024.5.1.163},
+  publisher = {Hamburg University Press},
+}
+
 @Article{Bolyen2018,
   author    = {Bolyen, Evan and Rideout, Jai Ram and Chase, John and Pitman, T. Anders and Shiffer, Arron and Mercurio, Willow and Dillon, Matthew R. and Caporaso, J. Gregory},
   title     = {An {I}ntroduction to {A}pplied {B}ioinformatics: a free, open, and interactive text.},
@@ -1424,13 +1437,15 @@ @Misc{DFG_50_01
   urldate = {2023-11-14},
 }
 
-@misc{dfg_gsp,
-  author       = {Deutsche Forschungsgemeinschaft},
-  title        = {Guidelines for Safeguarding Good Research Practice. Code of Conduct},
-  month        = apr,
-  year         = 2022,
-  publisher    = {Deutsche Forschungsgemeinschaft},
-  doi          = {10.5281/zenodo.6472827},
+@TechReport{dfg_gsp,
+  author    = {Deutsche Forschungsgemeinschaft},
+  title     = {Guidelines for Safeguarding Good Research Practice},
+  year      = {2022},
+  type      = {Code of Conduct},
+  number    = {version~1.1},
+  month     = apr,
+  doi       = {10.5281/zenodo.6472827},
+  publisher = {Deutsche Forschungsgemeinschaft},
 }
 
 @InCollection{Diamond2016,
@@ -1448,6 +1463,37 @@ @InCollection{Diamond2016
   month        = jun,
 }
 
+@InProceedings{DiCosmo2020,
+  author     = {Di Cosmo, Roberto},
+  title      = {Archiving and Referencing Source Code with Software Heritage},
+  booktitle  = {Mathematical Software -- ICMS 2020},
+  year       = {2020},
+  editor     = {Bigatti, Anna Maria and Carette, Jacques and Davenport, James H. and Joswig, Michael and de Wolff, Timo},
+  eventtitle = {7\textsuperscript{th} International Conference Mathematical Software},
+  eventdate  = {2020-07-13/2020-07-16},
+  venue      = {Braunschweig, Germany},
+  volume     = {12097},
+  series     = {Lecture Notes in Computer Science},
+  publisher  = {Springer International Publishing},
+  isbn       = {978-3-030-52200-1},
+  pages      = {362--373},
+  doi        = {10.1007/978-3-030-52200-1_36},
+  address    = {Cham},
+}
+
+@InBook{DiCosmo2023,
+  author    = {Di Cosmo, Roberto and Zacchiroli, Stefano},
+  title     = {The Software Heritage Open Science Ecosystem},
+  booktitle = {Software Ecosystems: Tooling and Analytics},
+  year      = {2023},
+  editor    = {Mens, Tom and De Roover, Coen and Cleve, Anthony},
+  publisher = {Springer International Publishing},
+  isbn      = {978-3-031-36060-2},
+  pages     = {33--61},
+  doi       = {10.1007/978-3-031-36060-2_2},
+  address   = {Cham},
+}
+
 @Online{DigiFlex,
   author  = {{Institute for Innovation Research and Management}},
   title   = {{D}igi{F}lex - Digital Flexibilization Program for an Individualized Freshman Year},
@@ -1569,6 +1615,16 @@ @online{edX
 urldate = {2023-07-20}
 }
 
+@Book{Elsholz2006,
+  author    = {Elsholz, Uwe and J{\"a}kel, Lutz and Megerle, Andreas and Vollmer, Lutz-Michael},
+  title     = {{V}erstetigung von {N}etzwerken},
+  year      = {2006},
+  publisher = {Arbeitsgemeinschaft Betriebliche Weiterbildungsforschung e. V., Projekt Qualifikations-Entwicklungs-Management},
+  url       = {https://www.abwf.de/content/main/publik/handreichungen/lipa/012_88hand-12.pdf},
+  address   = {Berlin, Germany},
+  month     = sep,
+}
+
 @online{ENCCS,
 author = {{EuroCC National Competence Centre Sweden}},
 title = {{ENCCS - Supercomputer access and training for your business/organisation}},
@@ -1716,6 +1772,15 @@ @Article{FAIRaddendum
   publisher = {Springer Science and Business Media {LLC}},
 }
 
+@online{FAIRmaturity,
+author = {{FAIR Data Maturity Model Working Group}},
+title = {{FAIR} Data Maturity Model: core criteria to assess the implementation level of the {FAIR} data principles},
+url = {https://www.rd-alliance.org/groups/fair-data-maturity-model-wg},
+year = {2019},
+month = apr,
+urldate = {2024-03-06},
+}
+
 @Article{Fanfarelli2015,
   author    = {Fanfarelli, Joseph and Vie, Stephanie and McDaniel, Rudy},
   title     = {Understanding digital badges through feedback, reward, and narrative},
@@ -1976,16 +2041,24 @@ @online{GitHubStreakStats
   urldate = {2023-06-14},
 }
 
+@Online{GitHubZenodo,
+  author  = {GitHub},
+  title   = {Referencing and citing content},
+  url     = {https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content},
+  urldate = {2024-03-06},
+}
 
-@article{Goble2014,
-	author = {Goble, C.},
-	journal = {IEEE Internet Computing},
-	month = {Sep.},
-	number = {5},
-	pages = {4-8},
-	title = {Better Software, Better Research},
-	volume = {18},
-	year = {2014}
+@Article{Goble2014,
+  author  = {Goble, Carole},
+  title   = {Better Software, Better Research},
+  journal = {IEEE Internet Computing},
+  year    = {2014},
+  volume  = {18},
+  number  = {5},
+  month   = sep,
+  pages   = {4--8},
+  issn    = {1089-7801},
+  doi     = {10.1109/MIC.2014.88},
 }
 
 @Article{Godoy2022,
@@ -2300,6 +2373,38 @@ @TechReport{Hedinger2022
   address     = {Zurich, Switzerland},
 }
 
+@TechReport{Helmholtz2017,
+  author      = {{Helmholtz Open Science Office}},
+  title       = {Recommendations for Policies of the {H}elmholtz {C}enters on Research Data Management},
+  institution = {Helmholtz Association Open Science Working Group},
+  year        = {2017},
+  type        = {Position paper},
+  doi         = {10.48440/os.helmholtz.036},
+  address     = {Potsdam, Germany},
+}
+
+@TechReport{Helmholtz2019a,
+  author      = {{Task Group Research Software}},
+  title       = {Recommendations for the Implementation of Guidelines and Policies on Research Software Management at the {H}elmholtz {C}enters},
+  institution = {Helmholtz Open Science Office},
+  year        = {2019},
+  type        = {Position paper},
+  month       = nov,
+  doi         = {10.48440/os.helmholtz.040},
+  address     = {Potsdam, Germany},
+}
+
+@TechReport{Helmholtz2019b,
+  author      = {Bach, Felix and Bertuch, Oliver and Busse, Christian and zu Castell, Wolfgang and Celo, Sabine and Denker, Michael and Dinkelacker, Stefan and Druskat, Stephan and Faber, Claas and Finke, Ants and Fritzsch, Bernadette and Hammitzsch, M. and Haseleu, Julia and Konrad, Uwe and Krupa, J{\"o}rn and Leifels, Yvonne and Mohns-P{\"o}schke, Kerstin and Moravcikova, Martina and N{\"o}ller, Joachim and M{\"o}hl, Christoph and Nolden, Marco and Scheinert, Markus and Schelhaas, Ute and Scheliga, Katharina Sara and Schlauch, Tobias and Schnicke, Thomas and Scholz, Almut and Schwennsen, Florian and Seifarth, Jenny and Selzer, Michael and Shishatskiy, Sergey and Steglich, Dirk and Strohbach, Sandra and Terhorst, Dennis and Al-Turany, Mohammad and Vierkant, Paul and Wieser, Thomas and Witter, Ludwig and Wortmann, Daniel},
+  title       = {Model Policy on Sustainable Software at the {H}elmholtz {C}enters},
+  institution = {Helmholtz Open Science Office},
+  year        = {2019},
+  type        = {Model policy},
+  month       = nov,
+  doi         = {10.48440/os.helmholtz.041},
+  address     = {Potsdam, Germany},
+}
+
 @Article{Hennah2017,
   author    = {Hennah, Naomi and Seery, Michael K.},
   title     = {Using Digital Badges for Developing High School Chemistry Laboratory Skills},
@@ -2849,6 +2954,28 @@ @TechReport{Konkol2021
   publisher   = {Zenodo},
 }
 
+@TechReport{Konrad2020,
+  author    = {Konrad, Uwe and F{\"o}rstner, Konrad and Reetz, Johannes and Wannemacher, Klaus and Kett, J{\"u}rgen and Mannseicher, Florian},
+  title     = {Digitale {D}ienste f{\"u}r die {W}issenschaft -- wohin geht die {R}eise?},
+  year      = {2020},
+  type      = {Position paper},
+  month     = dec,
+  doi       = {10.5281/zenodo.4301924},
+  publisher = {Zenodo},
+}
+
+@TechReport{Konrad2021,
+  author        = {Konrad, Uwe and F{\"o}rstner, Konrad and Reetz, Johannes and Wannemacher, Klaus and Kett, J{\"u}rgen and Mannseicher, Florian},
+  title         = {Digital services for science -- where is the journey heading?},
+  year          = {2021},
+  type          = {Position paper},
+  month         = feb,
+  doi           = {10.5281/zenodo.4301947},
+  publisher     = {Zenodo},
+  related       = {Konrad2020},
+  relatedstring = {Translation of},
+}
+
 @InProceedings{Koopman2022,
   title      = {{S}us{T}rainable: Promoting Sustainability as a Fundamental Driver in Software Development Training and Education},
   year       = {2022},
@@ -2958,6 +3085,21 @@ @InProceedings{Laginja2022
   venue        = {Montr{\'e}al, Qu{\'e}bec, Canada},
 }
 
+@Article{Lamprecht2020,
+  author    = {Lamprecht, Anna-Lena and Garcia, Leyla and Kuzak, Mateusz and Martinez, Carlos and Arcila, Ricardo and Martin Del Pico, Eva and Dominguez Del Angel, Victoria and van de Sandt, Stephanie and Ison, Jon and Martinez, Paula Andrea and McQuilton, Peter and Valencia, Alfonso and Harrow, Jennifer and Psomopoulos, Fotis and Gelpi, Josep Ll and Chue Hong, Neil and Goble, Carole and Capella-Gutierrez, Salvador},
+  title     = {Towards {FAIR} principles for research software},
+  journal   = {Data Science},
+  year      = {2020},
+  volume    = {3},
+  number    = {1},
+  month     = jan,
+  issn      = {2451-8484},
+  doi       = {10.3233/DS-190026},
+  pages     = {37--59},
+  publisher = {IOS Press},
+  urldate   = {2024-03-06},
+}
+
 @Article{Lamprecht2022a,
   author    = {Lamprecht, Anna-Lena and Martinez-Ortiz, Carlos and Barker, Michelle and Bartholomew, Sadie L. and Barton, Justin and Chue Hong, Neil and Cohen, Jeremy and Druskat, Stephan and Forest, Jeremy and Grad, Jean-No{\"e}l and Katz, Daniel S. and Richardson, Robin and Rosca, Robert and Schulte, Douwe and Struck, Alexander and Weinzierl, Marion},
   title     = {What Do We (Not) Know About Research Software Engineering?},
@@ -4988,6 +5130,35 @@ @Online{usRSETraining
   urldate = {2023-07-12},
 }
 
+@Online{UtrechtRDM,
+  title   = {Research Data Management Support},
+  url     = {https://www.uu.nl/en/research/research-data-management},
+  urldate = {2024-03-06},
+}
+
+@TechReport{Utrecht2016a,
+  author   = {{Utrecht University}},
+  title    = {Universitair beleidskader onderzoeksdata {U}niversiteit {U}trecht},
+  year     = {2016},
+  type     = {Policy paper},
+  language = {nl},
+  month    = jan,
+  url      = {https://www.uu.nl/sites/default/files/universitair_beleidskader_onderzoeksdata_universiteit_utrecht_versie_januari_2016_0.pdf},
+  urldate  = {2024-03-06},
+}
+
+@TechReport{Utrecht2016b,
+  author        = {{Utrecht University}},
+  title         = {University policy framework for research data {U}trecht {U}niversity},
+  year          = {2016},
+  type          = {Policy paper},
+  month         = jan,
+  url           = {https://www.uu.nl/sites/default/files/university_policy_framework_for_research_data_utrecht_university_-_january_2016.pdf},
+  urldate       = {2024-03-06},
+  related       = {Utrecht2016a},
+  relatedstring = {Translation of},
+}
+
 @Article{Vanganjil2023,
   author    = {Vanganjil, Lut-Ochir and Banzragch, Buyandelger and Adiyasuren, Zolzaya and Boloo, Nyamsuren},
   title     = {A Competency Framework Implementation for International Public in the Information, Communication and Technology},
@@ -5272,6 +5443,17 @@ @Article{White2022
   publisher = {The Open Journal},
 }
 
+@TechReport{Wilkinson2023,
+  author      = {Wilkinson, Mark D. and Sansone, Susanna-Assunta and Grootveld Marjan and Nordling, Josefine and Dennis, Richard and Hecker, David},
+  title       = {{FAIR} Assessment Tools: Towards an ``Apples to Apples'' Comparisons},
+  institution = {EOSC Association AISBL},
+  year        = {2023},
+  type        = {Project deliverable},
+  month       = jan,
+  doi         = {10.5281/zenodo.7463421},
+  publisher   = {Zenodo},
+}
+
 @Article{Williams2016,
   author    = {Williams, Jason J. and Teal, Tracy K.},
   title     = {A vision for collaborative training infrastructure for bioinformatics},

paper.tex

@@ -26,6 +26,10 @@
     Alexander Struck
     \and
     Axel Loewe
+    \and
+    Markus Ankenbrand
+    \and
+    Jean-Noël Grad
 }
 
 \date{\today}
@@ -81,14 +85,19 @@ \section{Motivation}
 
 Research Data Management has proved to benefit data quality through training researchers, the reusability through data repositories and to avoid duplication of effort.
 [TODO elaborate parallels to RDM SuccessStory] For over a decade, research funders and organizations made a significant effort to establish RDM and teams around it.
+[TODO: should we list examples of RDM teams?] See for example the Utrecht University Research Data Management Support~\autocite{UtrechtRDM}, University of Stuttgart FoKUS team~\autocite{Boehlke2024}.
 We assume that research software will follow a similar trajectory.
-\footnote{For arguments why research software is unlike data, see REF .}
+\footnote{For arguments why research software is unlike data, see \autocite{Lamprecht2020}.}
 While we focus on Germany here, it is beneficial to review how other countries approach research software.
 In the UK, for example, many universities started initiating dedicated RSE departments about a decade ago~\autocite{Crouch2013}.
 The successful establishment of such staff roles is a role model for similar academic organizations worldwide.
 A range of already-existing departments can be seen in this map: https://society-rse.org/community/rse-groups/ 
 
-Policies for research software management and guidelines involving responsible research practices detailing software handling are the precursors for a research software engineering environment. [REF Helmholtz, AllianzInitiative, Utrecht, …]
+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},
+the AllianzInitiative~\autocite{Konrad2021},
+the University Utrecht~\autocite{Utrecht2016b},
+and the German Research Council~\autocite{dfg_gsp}.
 
 \subsection{Tasks - Why do central software services make sense?}
 
@@ -97,7 +106,7 @@ \subsection{Tasks - Why do central software services make sense?}
 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.
 
-Cite for international comparison \autocite{Cosden2022} Princeton RSE group model
+Cite for international comparison the Princeton RSE group model~\autocite{Cosden2022a}.
 
 
 
@@ -126,7 +135,7 @@ \subsection{People}
 While this is a problem already today, it is expected to get a lot worse in the future due to both an aging society and an ever-increasing demand for these individuals.
 Thus, it is in the best interest of research organisations to avoid losing the RSEs they employ to industry.
 One of the most under-used possibilities they have is to offer permanent positions. 
-RSE departments act as knowledge hubs in a network of academic developers[REF: Dissertation zur Verstetigung von Netzwerken].
+RSE departments act as knowledge hubs in a network of academic developers~\autocite{Elsholz2006}.
 This enables the embedded experts to maintain in-depth knowledge and to assess current trends and developments, both in research as well as technology.
 According to [SUB Goettingen] employee satisfaction significantly increases with RSE services.
 The SUB library department “Software and Digital Services” was founded to support their (research) software needs~\autocite{schimavoigt2023}.
@@ -150,15 +159,15 @@ \section{Benefits - Why centralized RSEs would become a success story}
 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.
 
 Coming back to RDM again for comparison: The most recent funding guidelines suggest “data stewards” in data-driven research.
-Such experts are to be employed in advanced research projects like “Collaborative Research Centers” (CRC)[Footnote Sonderforschungsbereich (SFB)] or “Clusters of Excellence”
+Such experts are to be employed in advanced research projects like “Collaborative Research Centers” (CRC) \footnote{Sonderforschungsbereich (SFB)} or “Clusters of Excellence”
 \footnote{Cluster der Exzellenzinitiative}.
 These data experts support research projects in several aspects including DMPlans, grant applications, data availability for journal publications, compliance, FAIRification and more.
 With the increasing recognition of software as a research object/result, it is easy to see how projects will require and benefit from very similar support in software needs in the near future.
 
 The latest DFG grant application templates require discussion of data 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).
 A few journals started asking for code submission [REF CHORUS? Nature?].
-The rather complex assessment of FAIRness [REF apples to apples] has widened from data to software~\autocite{fair_data_maturity_model_working_group_2020}.
+The rather complex assessment of FAIRness~\autocite{Wilkinson2023,FAIRmaturity} has widened from data to software~\autocite{Lamprecht2020}.
 
 A decentralized RSE will provide training, improve software, and support research publications, in close relationship with the local research team.
 
@@ -384,7 +393,7 @@ \subsection{Software Maintenance Service}
 
 Funder policies such as~\autocite{dfg_gsp} require long-term preservation of used research data and software in an adequate way.
 For research data, established procedures to implement this requirement exist.
-For research software, dedicated archiving solutions such as Software Heritage [REF] or Zenodo's GitHub integration [REF] exist.
+For research software, dedicated archiving solutions such as Software Heritage~\autocite{DiCosmo2020,DiCosmo2023} or Zenodo's GitHub integration~\autocite{GitHubZenodo} exist.
 
 In contrast to research data, the long-term availability and usability of research software requires more than an adequate archiving method:
 Software maintenance is the ongoing change process of software after its release.