Tracking research software outputs in the UK
Domhnall Carlin, Austen Rainer

TL;DR
This paper investigates how UK research institutions store and share software outputs, revealing low sharing rates and issues with links, which threaten the long-term sustainability of research software in the scientific community.
Contribution
It provides an empirical analysis of UK research software registration and sharing practices using UKRI GtR metadata, highlighting gaps and challenges in research software dissemination.
Findings
Low proportion of software reported as research outcomes
High incidence of missing or erroneous URLs for software links
GitHub is the most common platform for publicly funded research software
Abstract
Research software is crucial in the research process and the growth of Open Science underscores the importance of accessing research artifacts, like data and code, raising traceability challenges among outputs. While it is a clear principle that research code, along with other essential outputs, should be recognised as artifacts of the research process, the how of this principle remains variable. This study examines where UK academic institutions store and register software as a unique research output, searching the UKRI's Gateway to Research (GtR) metadata for publicly funded research software in the UK. The quantity of software reported as research outcomes remains low in proportion to other categories. Artifact sharing appears low, with one-quarter of the reported software having no links and 45% having either a missing or erroneous URL. Of the valid URLs, we find the single largest…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
