Open Science & Research Services

Open Research Software and Code refers to custom, author-generated code used in a scientific research study, often during data collection, interpretation or analysis, and subsequently made publicly available under an Open Access license via a linked repository, or as Supporting Information. Reference.

The UNESCO Recommendation on Open Science advises that open-source software and source code should be made publicly available in a timely, user-friendly, modifiable format under an open licence that allows others to use, study, modify, create derivatives, and share it. The source code must be included in the release, deposited in openly accessible repositories, and licensed under terms that permit modification and redistribution. In open science, when software is part of the research process, reuse and replication generally require that the code be shared together with open data and clear specifications of the environment needed to compile and run it.

Reasons for researchers opening up their research software or code or reusing open research software or code of others include:

1. Accessibility and transparency: Open Code is easily accessible and provides a high degree of transparency. It makes it possible to understand and review the processes and results of other researchers. 
2. Reproducibility: Open Code supports the reproducibility of research work. It enables others to examine, verify, and build on previous research results. This strengthens credibility and trust in research work.
3. Collaboration in the community: Open Code promotes knowledge sharing, troubleshooting, and innovation and opens up perspectives for new research directions. By sharing code openly, others can actively contribute to the code, give feedback, build their work on it, and thus avoid duplication of effort.
4. Getting credits for programming: Programmers receive recognition for their programming work.

Source: Open Economics Guide by ZBW

You may like to refer to this checklist when making your research software or code open:

• If you have written code, have you documented your test protocol?
• Have you scripted your analysis, including data cleaning and wrangling, where applicable?
• Is your code well annotated and documented for ease of understanding and reuse?
• Has the use of all software versions and computing environments been documented where applicable?
• Are you able to openly share your code?
• If you have shared your code, have you shared it under an open license?
• Have you adopted the FAIR principles for research software?
• Did you know that you can anonymise your GitHub repository when sharing your code with blind peer reviewers?

Check out the following tools:

• Use the 'Self-assessment for FAIR research software' Checklist by Netherlands eScience Center and Australian Research Data Commons to assess your software’s FAIRness and receive a badge:

• Walk through the 'Five Recommendations for FAIR Software' by Netherlands eScience Center and DANS.

Making your software citable both gains credit for your work, and improves reproducibility of research that relies on the software. There are a variety of ways to make your software citable:

• Publishing your software in a software journal provides a citation with a persistent identifier, and provides peer review.
• Publishing your software in a major general replication archive provides a citation with a persistent identifier, and usually allows you to publish citable new versions of the software as you choose. Contact DR-NTU (Data) for guidance.
• If you publish software in Github, you can create a citable archived version whenever you choose, through Zenodo.

Software Citation Use Cases:

1. Researcher who uses someone else’s software for a paper.
2. Researcher who uses someone else’s software for new software.
3. Researcher who contributes to someone else’s software (open source project)
4. Researcher who wants to know who uses the researcher’s software. 
5. Researcher gets credit for software development at the academic/governmental institution, in professional career, etc.
6. Researcher who wants to “reproduce” another person/group’s analysis. 
7. Researcher who wants to find a piece of software to implement a task. 
8. Publisher wants to publish a software paper. 
9. Publisher who wants to publish papers that cite software. 
10. Indexer (e.g., Scopus, WoS, Scholar, MS Academic Search) who wants to build a catalog of software. 

Reference.

Health Data Research UK: Open Science Open Code