| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Please add any new resources through this form or by commenting on this google sheet. The data can also be downloaded from this sheet. | |||||||||||||||||||||||||||
2 | Acknowledgement: This project has received funding from the European Union’s Horizon Europe research and innovation programme under grant agreement No 101094406. | |||||||||||||||||||||||||||
3 | Organisation | Policy | Country | Notes | Areas covered | Added to Collection | Last internal update or review of policy | |||||||||||||||||||||
4 | Aalto University | Open Source Policy | Finland | This policy supports the release of work with limited commercial potential. | Ownership | 2023 | 2017-11-13 | |||||||||||||||||||||
5 | Ahmadu Bello University | Research Policy | Nigeria | Ownership of copyright for software belongs to the university; software included under inventions. | ownership, copyright | 2025 | ||||||||||||||||||||||
6 | Alfred Wegener Institut | Guidelines for the development and use of research software | Germany | The AWI recognizes research software as both a vital tool and a scientific product, protected by copyright, and commits to sustainable, open, and reusable software development to ensure traceability, reproducibility, and quality in line with Helmholtz Centre guidelines. To support this, AWI provides infrastructure, consulting, publication platforms, and training opportunities, while promoting recognition of software developers’ contributions and career development. | various, including reuse, copyright, reproducibility, training, roles and career advancement | 2025 | ||||||||||||||||||||||
7 | American University of Beirut | Intellectual Property Policy | Cyprus | Intellectual property includes research outputs like software or inventions, which are presumed owned by the University with benefit-sharing rights for the originator. | intellectual property | 2025 | ||||||||||||||||||||||
8 | Caltech (California Institute of Technology) | Caltech Copyright and Software Policy | USA | The policy outlines the ownership and distribution of copyrights and royalties for various copyrightable materials produced by faculty members at the Institute. | Ownership, royalty income, copyright | 2023-05-16 | 2007-03-13 | |||||||||||||||||||||
9 | CERN | Open Science Policy | Switzerland | Includes a section on Open Source Software that covers openess/licensing, best practice, and contribution to open source software relevant to its mission through code contributions, participation in the evolution of software, and standardisation. | Various including licensing, reuse, reproducibility, integrity, education, training and outreach | 2023 | 2022-09 | |||||||||||||||||||||
10 | Department of Energy (DOE) United States | Open Source Software Policy | USA | For development and use of open source software. | Licensing, Open Source | 2023-05-16 | 2010-04-29 | |||||||||||||||||||||
11 | Department of Energy (DOE) Office of Scientific and Technical Information | DOE CODE Software Policy | USA | The DOE Office of Scientific and Technical Information (DOE OSTI) developed DOE CODE, providing functionality for collaboration, archiving, and discovery of scientific and business software. DOE CODE fulfills requirements to maintain an inventory of all DOE-funded custom-developed software and to report this inventory to the government-wide Code.gov website. | Access, sharing, preservation, licensing | 2024-08 | 2018 | |||||||||||||||||||||
12 | ETH Zurich | Guidelines for the Financial Exploitation of Research Results at ETH Zurich | Switzerland | This document covers the financial exploitation of research results, specifically the commercial exploitation of inventions and computer programs. It includes sections on ownership, disclosure procedures, funding patents, and revenue allocation. It seeks to protect intellectual property while giving guidance to academics regarding innovation and collaboration with industry. | Intellectual property, licensing, commercialization | 2024-03-30 | 2020-01-01 | |||||||||||||||||||||
13 | EURAC | Research Data and Source Code Management Strategy for Eurac Research | international | Considers source code and research software as primary research outputs; and requires their management in line with FAIR principles, including documentation, maintenance, version control, licensing compliance, and open-source publication where possible. | various, including documentation, versioning, licensing, FAIR, publication | 2025 | ||||||||||||||||||||||
14 | European Molecular Biology Laboratory (EMBL) | Open Science and Open Access Policy | Europe | Requirements include using open source software by default and sharing your software in a public software repository; ORCID required. | various, including open access, open source, recognition | 2025 | ||||||||||||||||||||||
15 | European Space Agency (ESA) | ESA open source policy | International | To effectively implement an OSS strategy and seize industry opportunities in the global market, both within and beyond the space sector, ESA must establish a clear strategy. This strategy will reinforce ESA's leadership in software development for the space sector and enable ESA to fulfill its role as a focal point for European research and innovation. | Open Source Software, distribution, licensing, intellectual property, visibility | 2023-05-16 | NA | |||||||||||||||||||||
16 | Finnish Meteorological Institute | Open-Source Software Policy | Finland | This policy is designed for publicly funded research that results in software development. It outlines the need for clear copyright ownership and encourages using Finnish Meteorological Society-approved licenses like MIT, Apache 2.0, or BSD 3-Clause to ensure the software's wide availability. An embargo period of up to two years is allowed before software must be open-sourced. The policy stresses the importance of using OSS dependencies, maintaining rigorous version control, comprehensive documentation, and archiving for long-term preservation, recommending GitHub for version control repository. This policy applies to all publicly funded research activities that have as a result the development of software. | Licensing, reuse | 2023-05 | NA | |||||||||||||||||||||
17 | Forschungszentrum Jülich | Guidelines for the development and distribution of software at Forschungszentrum Jülich | Germany | Software development is an intellectual achievement protected by copyright and, in the context of research, an independent, first-class product of scientific work.Until now, Forschungszentrum Jülich did not have a practical or secure framework within which employees could develop software.With the guidelines presented here, Forschungszentrum Jülich aims to support the development, management, distribution and impact of research software that meets high quality standards.They primarily target developers and employees who are involved in and deserve credit for this. | Software development, Licensing, and distribution. | 2025-07 | 2022 | |||||||||||||||||||||
18 | Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) | Guidelines for implementing open science at Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). Open Science Policy | Germany | FAU promotes open-source software by prioritizing it over proprietary systems, embedding open science practices into research and evaluation, and aiming to publish all in-house or contracted software openly for community use. | open source software, open science | 2025 | ||||||||||||||||||||||
19 | Helmholtz Open Science Office | Model Policy on Sustainable Software at the Helmholtz Centers | Germany | The Model Policy was drawn up by the Research Software Task Group with the assistance of other experts from the Helmholtz Association and was agreed with the Technology Transfer and Commercial Legal Protection Working Group and the Legal Affairs Working Group. See also the Checklist to Support the Helmholtz Centers in Implementing Policies on Sustainable Research Software and the 2019 Recommendations for the Implementation of Guidelines and Policies on Research Software Management at the Helmholtz Centers | Open science, research software management | 2023 | 2019-11-21 | |||||||||||||||||||||
20 | Helmholtz-Centrum Postdam (GFZ) | Policy on Use and Licensing of Research Software | Germany | Includes strategic measures for the valorisation of software; and principles for the development, use, exploitation and licensing of research software. | Licensing | 2023 | 2023-04-12 | |||||||||||||||||||||
21 | Heriot Watt University | Intellectual Property Policy | UK | The policy specifies that software and related works are included as copyrightable IP, with open-licensed materials and software required to release derivatives into the public domain under their licensing terms. | intellectual property | 2025 | ||||||||||||||||||||||
22 | Imperial College London | Research Data Management Policy | UK | Principal Investigators must archive the specific software version used in research data generation or analysis in a repository, notify the Library of its location, and are encouraged to follow the Software Sustainability Institute’s Sustainability and Preservation Framework. | archiving, versioning | 2025 | ||||||||||||||||||||||
23 | Indian Institute of Technology Roorkee | Intellectual Property Rights Policy | India | Intellectual property, including software, created with significant institutional resources, sponsorship, or as work-for-hire belongs to the Institute, while creations made independently without substantial use of resources remain with the creator. | intellectual property, use of university resources | 2025 | ||||||||||||||||||||||
24 | Instituto de Investigacion Sanitaria | Institutional Policy of Open Science | Spain | All research-related software should be released under open licenses to enable review, improvement, and reuse by the scientific community and beyond. | various, including open source software, licensing, reuse | 2025 | ||||||||||||||||||||||
25 | Johns Hopkins University | Intellectual Property Policy | US | When software is developed by faculty using University support, the University will own all rights to such property, including copyright (subject to agreements with appropriate funding sources). | intellectual property, use of university resources | 2025 | ||||||||||||||||||||||
26 | Kenyatta University | Research & Innovation Policy | Kenya | Outlines ownership of software; software belongs to creator if individual scholarship, owned by the university if employee is hired for purpose of developing software. | ownership | 2025 | ||||||||||||||||||||||
27 | Kings College London | Fair Publication Policy | UK | Incudes research software engineers in list of staff who should receive appropriate recognition and acknowledgement of their level of contribution to publications as standard practice within tjhe research community. | Roles and career advancement | 2023 | 2022-04-20 | |||||||||||||||||||||
28 | Leibniz Association | Leibniz Open Science Policy | Germany | The policy defines Open Research Software, Infrastructure, and Methodology as openly accessible, licensed, and referenceable tools, platforms, and processes (primarily based on open-source software) that enhance transparency, usability, and visibility of research outputs and methods. | open source software, publication, visibility | 2025 | ||||||||||||||||||||||
29 | Leipzig University Library | Guidelines for the Development of Open Source Software at Leipzig University Library v1.0 and Github (both in German) | Germany | An introductory overview of the benefits of using open source are explained here, among others. Cite the the Public Code Initiative, Open Source Guide, Criteria for open-source software from the Open Source Initiative. | Versioning, licensing, archiving, publication, documentation, | 2023-05-16 | 2020-06-08 | |||||||||||||||||||||
30 | Maastricht University | Open Science | Netherlands | Includes FAIR software as one of the seven branches of the policy. Addresses topics such as versioning, training, use of Software Management Plans. | Open science, FAIR, SMPs, training, versioning | 2023 | 2022 | |||||||||||||||||||||
31 | Max Planck Institute for Meteorology | Software Licensing and Copyright Policy for Research Software Code cites the Contributor Licence Agreement (CLA) | Germany | As good scientific practice, the MPI-M encourages and supports the publication of software written at the institute as "Free and Open Source Software". This ensures that the authorship of the software remains visible even if the software is passed on or further developed. | Licensing, reuse, FOSS, copyright, contribution | 2023 | 2022-07-04 | |||||||||||||||||||||
32 | McGill University | Policy on inventions and software | Canada | The policy sets forth the rules applying to the ownership of, and rights to, intellectual property in the form of Inventions and Software developed by McGill University academic staff, administrative and support staff, students, as well as any other physical person working or doing research at or under the auspices of the University. | Inventions and software; ownership; commercialization | 2024-06-14 | NA | |||||||||||||||||||||
33 | MIT | Intellectual Property Policy | US | The government retains certain rights to software and data from federally funded research, while MIT owns patentable inventions, software, and materials. | intellectual property | 2025 | ||||||||||||||||||||||
34 | Mohamed Bin Zayed University of Artificial Intelligence (MBZUAI) | Intellectual Property Policy | UAE | The University explicitly claims ownership of software created by personnel or students within employment scope, using significant resources, or under third-party agreements, while independent works without such involvement remain with the creator. | intellectual property, use of university resources | 2025 | ||||||||||||||||||||||
35 | Monash University (Business School) | Research Software Standards | Australia | This outlines a process for assessing software in career advancement. Whilst this is a draft, the final policy is in place (but not publicly available). | Roles and career advancement | 2023 | 2021-09-23 | |||||||||||||||||||||
36 | NASA (Science Mission Directorate) | Scientific Information policy | USA | Describes how scientific information (including software) is shared. | Licensing | 2023 | NA | |||||||||||||||||||||
37 | Netherlands eScience Center | Policy towards publishing, licensing and intellectual property | Netherlands | The eScience Center strives to make its software available in a way that enables collaborative Open Science, as well as use by private parties. This is done by publicly releasing software under a permissive free and open source (FOSS) license, in particular the Apache License version 2.0. | IP | 2024 | 2017 | |||||||||||||||||||||
38 | Netherlands eScience Center | Policy concerning the use of Generative AI at the Netherlands eScience Center | Netherlands | Provides guidance on how Generative AI can be used to assist the creation of research software (among other things). | AI | 2023-11-23 | 2023-11-23 | |||||||||||||||||||||
39 | Netherlands eScience Center | Special conditions Netherlands eScience Center grants | Netherlands | The Netherlands eScience Center adheres to the principle that academic research must be as open as possible. Results from publicly funded research are published Open Access, with all relevant data available as Open Data, and all software as Open Source software. Special grants terms and conditions for the projects awarded through the Netherlands eScience Center calls, covers rules on collaboration, publication, communication, and software/data release. | Open source | 2024 | ||||||||||||||||||||||
40 | Netherlands Institute for Radio Astronomy (ASTRON) | Open Source Policy v2.0 and publication | Netherlands | The goal of this policy is to provide the ASTRON organisation with the guidelines that support the openness of the software developed by employees of our institute. The main goal of this is to stimulate sharing of software and making citation possible. This is important from a perspective of open science, and making the software developed at ASTRON more visible to the outside world. See related article, Towards an open source policy by Y.G. Grange, T. Jürges, T.J. Dijkema, R. Halfwerk, G.W. Schoonderbeek | Accessibility, citation | 2023 | 2022-08-23 | |||||||||||||||||||||
41 | Norwegian University of Science and Technology (NTNU) | Guidelines for policy for Open Science | Norway | This is an Open Science policy; however, under the licensing section (3.1), there are indications on how licensing should be conducted. Specifically software and source code, which mentions, for instance, that "NTNU-produced software should be licensed with the European Union Public Licence." | Licensing | 2024-03-30 | 2023-10-09 | |||||||||||||||||||||
42 | Politecnico di Torino | University Policy on Research Data Management | Italy | Software included as part of research data; supports the openness of scientific publications, data, and software. | software management, licensing, FAIR | 2025 | ||||||||||||||||||||||
43 | Potsdam Institute for Climate Impact Research | Open Source and Open Data Policy | Germany | This policy supports publication of open source software developed at the institute, and covers open source licensing. | open source software, licensing | 2025 | ||||||||||||||||||||||
44 | Qatar University | Intellectual Property Policy and Procedures | Qatar | Software included as copyrightable work. | intellectual property | 2025 | ||||||||||||||||||||||
45 | Radboud University - Donders Institute Network | Policy for Research Data and Software Management | Netherlands | This policy covers research software management. | various, including FAIR, SMPs, roles and responsibilities | 2025 | ||||||||||||||||||||||
46 | Royal Holloway University London | Open Research policy | UK | Open Research is identified as a practice that improves the quality, reproducibility and impact of research. Open Research enables access to research, namely publications, data and software. See allso the 11-step plan on implementation. | Various | 2023 | NA | |||||||||||||||||||||
47 | Shizuoka University | Intellectual Property Policy | Japan | Copyrights to works like source code generally belong to the individual creator, but works produced at the University’s request belong to the University unless released as public domain or open-source software. | intellectual property | 2025 | ||||||||||||||||||||||
48 | Simon Fraser University | Intellectual Property Policy | Canada | Software included as IP content. | intellectual property | 2025 | ||||||||||||||||||||||
49 | Stanford University | Inventions, Patents, and Licensing | DoResearch | USA | Pursuant to section is 9.1.4, researchers at Stanford have the ability to bequeath their work to the public domain, including open sourcing their code under a license selected by the research team, without having to get permission in advance. | Inventions, Patents, Licensing, tech transfer | 2024-06-14 | NA | |||||||||||||||||||||
50 | Tec de Monterrey | Intellectual Property | Mexico | Software created under employment is subject to policy, with ownership and benefits split equally between the Institute and the inventors. | intellectual property, ownership, royalties | 2025 | ||||||||||||||||||||||
51 | Technische Universität München (Technical University of Munich) | Handreichung für die Veröffentlichung wissenschaftlicher Daten und Softwareprogramme (Guide for the publication of scientific data and software programs) | Germany | This document aims to guide the publication of scientific data and software programs. It emphasises open access and interdisciplinary cooperation to enhance visibility and reputation. It highlights the importance of selecting appropriate licenses for the reuse of research outputs (e.g. software), and mentions also, legal considerations to ensure third-party rights are not infringed. | Licensing, Open-Source Software, Intellectual Property | 2024-03-30 | 2023-12 | |||||||||||||||||||||
52 | TU Delft | Research Software Policy | Netherlands | Facilitates best-practices on research software management and sharing; emphasises the value of research software as a standalone research output and facilitates proper recognition of the contribution of TU Delft researchers to software, etc. - best-practices on research software management and sharing, irrespective of whether the code is proprietary or open source. - the value of research software as a standalone research output and facilitates proper recognition of the contribution of TU Delft researchers to software. - high-level requirements for how software should be managed, the responsibilities of the different stakeholders involved in software development and describes the global workflows that facilitate sharing software openly. See also the Research Software Guidelines. | Various | 2023 | 2021 | |||||||||||||||||||||
53 | Universidad Austral | General Regulations on Intellectual Property | Argentina | Software created during employment is owned by the University, must be disclosed for potential protection (including patents) under confidentiality obligations, and detailed records and forms must document authorship, dependencies, and registration. | intellectual property, inventions | 2025 | ||||||||||||||||||||||
54 | Universidad Nacional Autónoma de México (UNAM) | Principles of free and open software at UNAM | Mexico | The policy promotes technological innovation and research by encouraging the development and use of free and open-source software, with careful adherence to licensing and usage agreements. | open source software, licensing | 2025 | ||||||||||||||||||||||
55 | Universidad de los Andes | Intellectual Property Regulations | Costa Rica | Inventions, including software, created at the University must be disclosed for royalty distribution, while the University retains exclusive copyright ownership of collective works, student works done on its behalf, and all software or databases produced by students or academics in their official capacity. | intellectual property, royalties | 2025 | ||||||||||||||||||||||
56 | Universidade de Minho | Open Science Policy | Portugal | Encourages researchers to share their code with an appropriate open source license; promote practices that guarantee the reproducibility of data analysis and all other code-dependent processes and software. | open source software, licensing, reproducibility | 2025 | ||||||||||||||||||||||
57 | Universidad de Zaragoza | Open Science Policy | Spain | Encourages the use of free and open-source software in research and expects non-commercial code developed by its researchers to be shared under open-source licenses to promote verification, reuse, and collaboration. | open source software, licensing, reuse | 2025 | ||||||||||||||||||||||
58 | Universidad Hemisferios | Intellectual Property Regulation | Ecuador | All software and databases created at UHE are the institution’s exclusive property, with creators required to assign rights and provide source code and documentation. | intellectual property | 2025 | ||||||||||||||||||||||
59 | Universidad Panamericana | Intellectual Property Policy and Incentives for Intellectual Property and Technology Transfer | Mexico | Intellectual property includes software, defined as any original copyrighted computer program or source code that instructs a device to perform specific tasks or functions; financial incentives for software development | intellectual property | 2025 | ||||||||||||||||||||||
60 | Universidad Tecnologica de Bolivar | Regulation of Intellectual Property | Colombia | The University owns the rights to software and related works created under its contracts or by its academic community, requiring disclosure, registration, and transfer of source code and documentation to ensure institutional ownership and protection. | intellectual property | 2025 | ||||||||||||||||||||||
61 | University College London | Intellectual Policy Property | UK | Encourages the development of software for research and permits staff to release as open source | Licensing | 2024-03-23 | NA | |||||||||||||||||||||
62 | University of Bristol | Open Code Sub-Policy and Guidance | UK | Provides practical advice on how to enhance transparency, rigour, and reproducibility of research. To help researchers make their software open source, the university will provide guidance on code repositories, invest in providing institutional access to code respositories, and provide training on how to publish software. | open source software, training | 2025 | ||||||||||||||||||||||
63 | University of Calgary | Faculty of Social Sciences Policy Guidelines Relative to Appointment, Increment, Promotion and Tenure | Canada | These guidelines for appointment, promotion, tenure, and annual assessment include a mention to data and software as part of the promotion section. | Career advancement | 2024-09-18 | 2005 | |||||||||||||||||||||
64 | University of Dundee | Open Research Policy | UK | Promotes open access to research outputs, including software code; consideration of open sharing of research software; and use of a reputable specialist repository to ensure software can be shared to maximize its potential reuse and provide documentation. | various open access, sharing, reuse, documentation | 2025 | ||||||||||||||||||||||
65 | University of Edinburgh | Research Data Management Policy | UK | This is a general research data management policy that covers software explicitly in the section titled FAIR data sharing. See also the Research Data Management Policy website | FAIR | 2024-08-08 | NA | |||||||||||||||||||||
66 | University of Electro-Communications | Copyright Handling Regulations | Japan | Software and other works created by staff using university resources, funding, or research contracts are considered “works related to the course of work” and fall under the university’s regulations on ownership and handling. | intellectual property, use of university resources | 2025 | ||||||||||||||||||||||
67 | University of Grenoble Alpes | Open Science Charter (in French) | France | This recommends distribution for software of archiving research codes in Software Heritage, in conjunction with a HAL.codes notice. See also the master plan. | Preservation | 2025-06 | 2022-12-01 | |||||||||||||||||||||
68 | University of Groningen | Research Data Management Policy of the Faculty of Science and Engineering | Netherlands | The "Special Considerations for data" section includes 4.3.1 Software as a data type. This includes requirements such as: If the software will be made Open, then the repository should contain the appropriate license and the citation file. A research software management plan (RSMP) should be developed as part of an RDMP. Date 2023 | Licensing, reuse | 2023 | 2022-10 | |||||||||||||||||||||
69 | University of Illinois | Open Source Licensing policy | USA | The Office of Technology Management supports faculty who are interested in releasing software via open source licensing. | Licensing, reuse | 2023 | NA | |||||||||||||||||||||
70 | University of Johannesburg | Policy on the protection, management and commercial exploitation of intellectual property | South Africa | The University holds copyright over software developed by employees or students in the course of their duties, requires disclosure and delivery of source code for IP protection, and seeks to negotiate copyright or licensing rights for software created by independent contractors. | copyright | 2025 | ||||||||||||||||||||||
71 | University of Maryland | Department of Psychology Procedures for Promotion to Associate Professor with Tenure | USA | Includes that procedures should recognize the multitude of research products that people produce as part of their research program (eg openly available research tools and software). | Career advancement | 2024-09-18 | NA | |||||||||||||||||||||
72 | University of Melbourne | Academic Specialist | Australia | This role is one of four academic staff work categorisations, that includes the role of Research Software Engineers (RSEs). | Roles and career advancement | 2023 | 2022-11 | |||||||||||||||||||||
73 | University of Minnesota | Reporting Inventions or Software Arising from Research | USA | This policy describes University employees’ and others’ duty to disclose the development of software and patentable inventions emanating from research activities and their right to release software under an Open-Source License. | Licensing | 2023 | 2022-01 | |||||||||||||||||||||
74 | University of North Texas (UNT) | Open Source Software Policy | USA | Focuses on the use of, contribution to, and creation and release of Open Source Software in order to support open scholarship. Includes that the libraries encourages librarians and staff members to contribute to projects for the Open Source Software that they use. | Licensing, contributions | 2023 | 2017-12-01 | |||||||||||||||||||||
75 | University of Pittsburgh | Intellectual Property Policy | US | Software developed during research belongs to the creator, with some exceptions (e.g., sponsored projects, university directed/supported) | intellectual property | 2025 | ||||||||||||||||||||||
76 | University of Pretoria | Intellectual Property Policy | South Africa | The University promotes broad access to intellectual property, implicitly including software, through Creative Commons licenses, open-source software, and open research data, except where ethical or legal restrictions apply. | intellectual property, licensing, open source software | 2025 | ||||||||||||||||||||||
77 | University of Rijeka (UNIRI) | Open Science Policy | Croatia | The policy encourages the storage and publication of source code generated from research in publicly accessible repositories, preferably under an open license. Authors are encouraged to publish complete, up-to-date and correct documentation of the code as a necessary prerequisite for compliance with the FAIR principles for software code. | Various | 2025-06 | 2025-03 | |||||||||||||||||||||
78 | University of Sharja | Intellectual Property Management | UAE | Software is considered IP content. | intellectual property | 2025 | ||||||||||||||||||||||
79 | University of Sheffield | University statement on Open Research | UK | Includes commitments to: Support training and development in best practice for computational literacy and reproducibility (e.g. by centralised provision of software experts (Research Software Engineers); and Recognise the equal value of non-traditional outputs (e.g. scholarly software, standards, datasets and tools), including in the hiring and promotion processes. Expectations of reserachers include: Transparent research methods - Share process and methods used in obtaining and evaluating research results, as appropriate to particular projects and disciplines (e.g. by publishing research software using best practice techniques for reproducibility, by preregistering protocols and analyses in advance of data collection when appropriate). | Various | 2023 | NA | |||||||||||||||||||||
80 | University of Strathclyde Glasgow | Research Data Management and Sharing Policy | UK | Software included as a research output and IP. | software management, intellectual property | 2025 | ||||||||||||||||||||||
81 | University of Stuttgart | Handling Research Software at the University of Stuttgart (In German) | Germany | Proposes measures for creating and funding new Research Software Engineering (RSE) positions, integrating existing positions, and attracting and nurturing suitable individuals. RSEs are individuals responsible for the design, organization, implementation, testing, documentation, and maintenance of research software. Institutional support for research software development is necessary due to the increasing importance of software in research and the requirements imposed by organizations such as the DFG (German Research Foundation). | Roles and career advancement | 2023-05-16 | NA | |||||||||||||||||||||
82 | University of Twente | Research Software Policy | Netherlands | UT's research software policy is designed to ensure the recognition of all research output and encourage open access across the board with FAIR principles—making both data and software Findable, Accessible, Interoperable, and Reusable. Key features of the policy include: - Open Access: Promoting transparency and enabling global collaboration. - Recognition & Rewards: Acknowledging the research software as an output with appropriate incentives. - Sustainability: Ensuring that UT research software remains functional in a wider ecosystem of open-source software. | FAIR, Roles and career advancement, sustainability | 2025-06-03 | 2024-11-25 | |||||||||||||||||||||
83 | University of the Western Cape | Research Data Management Policy | South Africa | Software included as part of research data; must be stored in secure environment, with metadata and documentation for discoverability and reuse; encourage making research software available. | software management, reuse | 2025 | ||||||||||||||||||||||
84 | University of Zagreb | Open Science Policy | Croatia | Covers open source code as a research output. | FAIR, open source software | 2025 | ||||||||||||||||||||||
85 | Vrije Universiteit Amsterdam | Research Data and Software Management Policy | Netherlands | Describes the university-wide principles for careful handling of research data and research software; provides guidance on FAIR principles; reuse; and compliance. | various, including software management, roles and responsibilities, preservation, citation, FAIR, publication | 2025 | ||||||||||||||||||||||
86 | ||||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||||
100 |