Research software is not data, and the FAIR principles — designed for data — do not carry over to it unchanged. These doctoral course notes take software as a first-class research output and work through what it takes to archive it, reference it precisely, and reproduce the results built on it. They introduce Software Heritage, the universal archive of source code, and the SWHID (ISO/IEC 18670) intrinsic identifier that names any source-code artefact by a cryptographic hash of its content. From there they build up software citation with the biblatex-software style, the qualified identifiers that pin an exact version, module or line range in context, and the practical workflows — Save Code Now, self-archival, artefact evaluation — that let a paper point at code that will still be there, and still be the same, years later. Written for PhD students and researchers across disciplines, suitable for self-study or taught delivery.

YouTube video by Ink & Switch

An increasing number of researchers see their work as interactive authoring tools or software substrates for interactive computational media. By talking about “authoring tools”, we remove the divide between programmers and users; “software substrates” let us look beyond conventional programming languages and systems; and “interactive computational media” promises a more malleable and adaptable notion of tools for thought we are striving for. This workshop aims to bring together a wide range of perspectives on these matters.

wingolog: article: in which our protagonist dreams of laurels