Comment on:

The following comment refers to this/these guideline(s)

Guideline 7

Cross-phase quality assurance

Researchers carry out each step of the research process lege artis. When research findings are made publicly available (in the narrower sense of publication, but also in a broader sense through other communication channels), the quality assurance mechanisms used are always explained. This applies especially when new methods are developed.


Continuous quality assurance during the research process includes, in particular, compliance with subject-specific standards and established methods, processes such as equipment calibration, the collection, processing and analysis of research data, the selection and use of research software, software development and programming, and the keeping of laboratory notebooks.

If researchers have made their findings publicly available and subsequently become aware of inconsistencies or errors in them, they make the necessary corrections. If the inconsistencies or errors constitute grounds for retracting a publication, the researchers will promptly request the publisher, infrastructure provider, etc. to correct or retract the publication and make a corresponding announcement. The same applies if researchers are made aware of such inconsistencies or errors by third parties.

The origin of the data, organisms, materials and software used in the research process is disclosed and the reuse of data is clearly indicated; original sources are cited. The nature and the scope of research data generated during the research process are described. Research data are handled in accordance with the requirements of the relevant subject area. The source code of publicly available software must be persistent, citable and documented. Depending on the particular subject area, it is an essential part of quality assurance that results or findings can be replicated or confirmed by other researchers (for example with the aid of a detailed description of materials and methods).

Guideline 10

Legal and ethical frameworks, usage rights

Researchers adopt a responsible approach to the constitutionally guaranteed freedom of research. They comply with rights and obligations, particularly those arising from legal requirements and contracts with third parties, and where necessary seek approvals and ethics statements and present these when required. With regard to research projects, the potential consequences of the research should be evaluated in detail and the ethical aspects should be assessed. The legal framework of a research project includes documented agreements on usage rights relating to data and results generated by the project.


Researchers maintain a continual awareness of the risks associated with the misuse of research results. Their responsibility is not limited to compliance with legal requirements but also includes an obligation to use their knowledge, experience and skills such that risks can be recognised, assessed and evaluated. They pay particular attention to the aspects associated with security-relevant research (dual use). HEIs and non-HEI research institutions are responsible for ensuring that their members’ and employees’ actions comply with regulations and promote this through suitable organisational structures. They develop binding ethical guidance and policies and define procedures to assess ethical issues relating to research projects.

Where possible and practicable, researchers conclude documented agreements on usage rights at the earliest possible point in a research project. Documented agreements are especially useful when multiple academic and/or non-academic institutions are involved in a research project or when it is likely that a researcher will move to a different institution and continue using the data he or she generated for his or her own research purposes. In particular, the researcher who collected the data is entitled to use them. During a research project, those entitled to use the data decide whether third parties should have access to them (subject to data protection regulations).

Guideline 13

Providing public access to research results

As a rule, researchers make all results available as part of scientific/academic discourse. In specific cases, however, there may be reasons not to make results publicly available (in the narrower sense of publication, but also in a broader sense through other communication channels); this decision must not depend on third parties. Researchers decide autonomously – with due regard for the conventions of the relevant subject area – whether, how and where to disseminate their results. If it has been decided to make results available in the public domain, researchers describe them clearly and in full. Where possible and reasonable, this includes making the research data, materials and information on which the results are based, as well as the methods and software used, available and fully explaining the work processes. Software programmed by researchers themselves is made publicly available along with the source code. Researchers provide full and correct information about their own preliminary work and that of others.


In the interest of transparency and to enable research to be referred to and reused by others, whenever possible researchers make the research data and principal materials on which a publication is based available in recognised archives and repositories in accordance with the FAIR principles (Findable, Accessible, Interoperable, Reusable). Restrictions may apply to public availability in the case of patent applications. If self-developed research software is to be made available to third parties, an appropriate licence is provided.

In line with the principle of “quality over quantity”, researchers avoid splitting research into inappropriately small publications. They limit the repetition of content from publications of which they were (co-)authors to that which is necessary to enable the reader to understand the context. They cite results previously made publicly available unless, in exceptional cases, this is deemed unnecessary by the general conventions of the discipline.

What is the correct interpretation of the sentence: “Software programmed by researchers themselves is made publicly available along with the source code”?

The sentence “Software programmed by researchers themselves is made publicly available along with the source code” is intrinsically linked to the concept of enabling public availability as introduced in Guideline 7 (“Cross-phase quality assurance”). Enabling public availability can – in a narrower sense – take the form of publication, but in a broader sense it can also happen “through other communication channels”, as stated in Guideline 7.

The scope available for enabling public availability depends on the individual case and can be organised in different ways and vis-à-vis different groups of individuals, including restricted groups or even limited to a single person and on request. The purpose of the regulation is to take into account the notion of replication as far as this is possible and reasonable.

If this broad understanding of enabling public availability is taken as a basis for Guideline 13, too, the self-programmed software and source code do not necessarily have to be published, put on the internet or otherwise made accessible to the general public or the professional public without restriction.

The comment belongs to the following categories:

GL7 (General) , GL10 (General) , GL13 (General)