{"id":9408,"date":"2025-03-19T15:09:10","date_gmt":"2025-03-19T15:09:10","guid":{"rendered":"https:\/\/wissenschaftliche-integritaet.de\/?post_type=kommentare&p=9408"},"modified":"2025-03-19T15:09:14","modified_gmt":"2025-03-19T15:09:14","slug":"fairer-zugang-forschungssoftware","status":"publish","type":"kommentare","link":"https:\/\/wissenschaftliche-integritaet.de\/en\/comments\/fairer-zugang-forschungssoftware\/","title":{"rendered":"FAIR access to research software"},"content":{"rendered":"\n

According to Guideline 13, research software that has been used to generate and make research results publicly available should always be included in scientific discourse. Making research software accessible through recognised repositories supports the verifiability of scientific results, enables follow-up research on related questions, and promotes reuse of the findings.<\/p>\n\n\n\n

Researchers remain responsible for deciding whether, how and where to make their research software publicly accessible, taking into account the standards and practices of their discipline. In line with the FAIR4RS principles<\/a>, efforts should be made to ensure that research software is as easily findable as possible for machines and that it is released under an appropriate licence for use in research so as to enable reuse, particularly with a view to further developing the software. This generally also includes transparent, verifiable documentation and provision of such elements as the source code, together with the underlying algorithms where applicable, the functionality of the research software, and its architecture (including compilers used, operating systems, information on data, rights management systems and governance structures, where relevant).<\/p>\n\n\n\n

If research software developed in-house is to be made available not only to ensure the verifiability of research results but also for use or reuse by third parties, the rights holder of the research software may grant usage rights under an appropriate licence (see also Struck et al., 2020). However, in individual cases there may be reasons that prevent the public release of the research software including its source code, or the granting of usage rights under a licence. Generally speaking, in view of various facets of Article 5(3) of the German Basic Law (freedom of research) \u2013 such as the right not<\/em> to publish \u2013 there may be reasons that justify limiting public access. These include ongoing publication processes that have not yet been completed, novelty-destroying disclosure with regard to intellectual property rights, conflicting third-party rights in connection with commissioned research, and ethical considerations in the context of security-related research.<\/p>\n\n\n\n