Software development is often an important part of scientific work at TUHH. Many of you use GitLab or GitHub to collaboratively create and share scientific software. But how can you best cite the software then?
Digital Object Identifiers (DOI) have become the quasi-standard for referencing electronic publications. So what could be more obvious than using DOIs for software as well? Since 2014, this has been possible thanks to the cooperation between GitHub and Zenodo:
Zenodo is an open platform for the permanent archiving of research outputs of almost any kind, operated by CERN and funded by the EU and others: zenodo.org/features
Those who are already active on GitHub can connect an existing repository with Zenodo. This will permanently archive the repository on Zenodo and assign the DOI for the repository. Further releases are also taken care of.
A current example from the Institute of Mathematics at TUHH:
Fabian Gabel, Dennis Gallaun, Julian Großmann, Marko Lindner, & Riko Ukena. (2023). fabiangabel/simulation_aperiodSchr: v.3 (v3.0.0). Zenodo. https://doi.org/10.5281/zenodo.7657268
GitHub describes how it works in just under 10 minutes reading time: Making Your Code Citable
And three more tips:
- Use the TUHH community on Zenodo: https://zenodo.org/communities/tuhh/
Assignment is also possible at a later date.
- Put a CITATION.cff in your repository
- Add the ORCID iD (Give credit where credit is due) to the authors.
And worth reading is the practical report from the Institute for Control Systems: Open Access Publishing at TUHH: Exemplary Step-by-step guide for a toolchain with TORE, GitLab, Sherpa Romeo and Zenodo von Patrick Göttsch, Christian Hespe, Adwait Datar, Simon Heinke und Lennart Heeren. tub.torials. 20 May 2022