https://github.com/code4ref/code4ref.github.io

How to record research software in CRIS (Continuing Research Information Systems)
https://github.com/code4ref/code4ref.github.io

collabw19 research-reproducibility research-software ssi

Last synced: 3 months ago
JSON representation

How to record research software in CRIS (Continuing Research Information Systems)

• Host: GitHub
• URL: https://github.com/code4ref/code4ref.github.io
• Owner: code4ref
• License: cc-by-4.0
• Created: 2019-04-03T08:11:11.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2021-03-31T20:54:42.000Z (over 3 years ago)
• Last Synced: 2024-05-14T15:36:11.066Z (6 months ago)
• Topics: collabw19, research-reproducibility, research-software, ssi
• Homepage: https://code4ref.github.io/
• Size: 1.69 MB
• Stars: 5
• Watchers: 5
• Forks: 2
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# Code4REF

## Why

Research software is an eligible REF submission but is rarely submitted.

The systems used to manage the REF at institutions focus on publications and, to some extent, datasets. In our experience these systems can also handle software, but it is not obvious how details of software can be recorded.

## What

We've created the website https://code4ref.github.io to provide guidance to researchers on recording details of their software in a CRIS.

The documentation currently draws on our experiences of the Pure system at St Andrews and the RIS system at Nottingham.

## Who

As well as providing guidance to researchers, the website should also help administrators to see how to support the reporting of research software and encourage them to feed back to vendors on how research software can be better supported.

## Further development

We only have experience of two of the systems currently used in UK HE, we need contributions from others to cover the full range. It is also unclear how customised our reference systems are, so we also need input from other users of those.

## Anticipated impact

Software is still an afterthought when thinking of research outputs. This will go some way to addressing that.

This documentation will facilitate the recording of software produced at an institution, allowing a clearer picture to be developed of the volume and range of software being created.

Encouraging researchers to record details of their software in a CRIS also encourages them to make it openly available and citable.