-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.qmd
216 lines (122 loc) · 5.53 KB
/
index.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
---
title: "Central software stewards at UT: Their role, activities and support"
# format:
# revealjs:
# incremental: false
# css: styles.css
# execute:
# echo: true
---
# Open Science Twente event
When: 31st October 2024 14:00 - 15:00
Where: LA 1218 (Langezijds)
Who: Néstor DelaPaz-Ruíz and Efe Kerem Sözeri
DCC coordinator: Raisa Biega
Visit [Openscience-Twente.com](https://www.openscience-twente.com/Events/Past%20OSCTDCC%20events/) for more information.
# Abstract
At this event, the UT software stewards Néstor de la Paz Ruiz and Efe Kerem Sözeri will introduce themselves and their efforts to make software open at the UT. Néstor and Efe give software carpentry workshops, offer training, provide guidance on UT staff software projects and are involved in the development of UT research software policy and guidelines.If you want to learn more about the UT software stewards, this event is a great opportunity to get in touch.
# Content
## Context
- Definition of software
- Software, a valuable resource
- Software quality
## Problems
- Who has more work?
- Where to start?
- What do I need to know?
## Opportunities
- Why managing UT software?
- What resources are available?
- Who guides me in the process?
## Software management policy and guideline
- Updates
# Context: Definition of software
Definition of research software from the FAIR for Research Software Working Group
```
“Includes source code files, algorithms, scripts, computational workflows
and executables that were created during the research process or for
a research purpose.”]
```
[Defining Research Software: a controversial discussion](https://doi.org/10.5281/zenodo.5504015)
# Context: Software as a valuable resource
```
“Software plays an increasingly important role in research
and it has become a key output of many research projects.”
```
```
“Making research software openly and sustainably available
supports reproducibility and reusability of research outcomes
and contributes to further research – key elements in the
transition to open science.”
```
[NWO: A national guide to research software management](https://www.nwo.nl/en/news/national-guide-research-software-management)
[Reproducibility crisis: https://www.labnews.co.uk/](https://www.labnews.co.uk/article/2029884/reproducibility-crisis)
# Context: Software quality
*From a reproducibility crisis to a credibility revolution.*
Google scholar/search:
“scientific replication crisis”: About 68.000 results
“scientific reproducibility crisis”: About 266.000 results
Korbmacher, M., Azevedo, F., Pennington, C.R. et al. The replication crisis has led to positive structural, procedural, and community changes. Commun Psychol 1, 3 (2023). https://doi.org/10.1038/s44271-023-00003-2
# Problems
Who has more work?
Those who writes research code at UT
Where to start?
UT software policy and guideline
What do I need to know?
Prepare for a learning process
# Opportunities
- Why managing UT software?
A new quantifiable and official output
- What resources are available?
Books, training, funding, OS tools
- Who guides me in the process?
Software stewards
    
# Summary: Role, activities, and support
- UT Research Software Policy 1.3 (UT-RSP)
- Guidelines for research software management at UT
- Developing digital competences (Training):
-- Software carpentry workshops
-- Software sustainability in practice
-- Guidance on UT staff for software projects
-- Recognition and regards
# Summary: Action plans
- UT Research Software Policy 1.3 (UT-RSP):
A complete document
Policy objectives
Legal clarification
Roles, rights, and responsibilities
- Guideline:
Technical guidance
Potential output into numbers
- Room for improvement
AI
Sustainability
Rewards and recognition
# Positives: A complete document
- Short and Precise: 6 pages and 1393 words
- NWO & NeSC guidelines
- Review of literature (meta studies)
- Hyperlinks to national and international arrangements
- Reference to internal UT policies
- The groundwork for the UT Research Software Guideline, hub of experts, software ambassadors, open-source community
# Positives: Roles, rights and responsibilities
- UT staff
- Software stewards
- Digital Competence Centre (DCC)
- Pure Faculty Managers
- Knowledge Safety Office
- Knowledge and Technology Transfer Office
- Faculty Boards
# Guideline: Technical guidance
- Software Management Plan (NeSC & NWO)
- Funding and requirements
- Legal restrictions
- Valorisation
- Attribution and compatibility (Licences)
- Documentation
- Public repository
# Thank you