@@ -4,15 +4,15 @@ Quick links to system-specific instructions:
4
4
- [ Pure] ( pure.html )
5
5
- [ RIS] ( RIS.html )
6
6
7
- ## Reporting research software in CRIS (Continuing Research Information Systems)
7
+ ## Reporting research software in CRIS (Current Research Information Systems)
8
8
9
9
Research software is an eligible REF submission. However, the majority
10
10
of REF submissions are research publications. Indeed, refereeing
11
11
research software is a difficult task, and reviewers may not have
12
12
clear guidelines for its evaluation for the REF purposes (something
13
13
else we need to work on), and many researchers prefer the safer route
14
14
of submitting papers. As a result, software outputs are not always
15
- being recorded in Continuing Research Information Systems (CRIS)
15
+ being recorded in Current Research Information Systems (CRIS)
16
16
used by universities. The first step here would be to help to
17
17
research software developers to find a way to record their outputs
18
18
in CRIS. This may not always be obvious, so on this website we provide
@@ -34,7 +34,7 @@ as research output, and will make a stronger case for the campaign
34
34
for the recognition and adoption of the RSE role within academia,
35
35
lead by the [ UK Research Software Engineer Association] ( https://rse.ac.uk/ ) .
36
36
37
- ## Continuing Research Information Systems used in UK Universities
37
+ ## Current Research Information Systems used in UK Universities
38
38
39
39
[ UCISA] ( https://www.ucisa.ac.uk/ ) regularly survey UK Higher Education
40
40
Institutions about the systems they use, including CRIS. [ The 2017 results are
@@ -56,7 +56,7 @@ repository](https://github.com/code4ref/code4ref.github.io).
56
56
57
57
## General workflow
58
58
59
- How to record research software in CRIS (Continuing Research Information Systems)
59
+ How to record research software in CRIS (Current Research Information Systems)
60
60
61
61
Different scenarios. What is minimal. What is recommended.
62
62
0 commit comments