FAIR4RS WG will present its first output, the FAIR Principles for Research Software, and will discuss next steps. Wide-scale community engagement continues to be critical to this work, and this session will include information on different ways to engage with this work.
Collaborative session notes: https://docs.google.com/document/d/1LtvhaRHKfem-aV-ARApM6tJbSDObearVRSnbIE9VbtU/edit
This meeting will focus on two main areas:
-
Presentation of the final FAIR principles for research software. Examples of implementation plans by early adopters will also be provided.
-
Outlining upcoming work on use cases and adoption guidelines. This is likely to include work to:
-
Identify existing FAIR research software guidelines and tools that could be leveraged and identify gaps
-
Work with creators of existing guidelines to extend their reach to include more of the FAIR4RS principles
-
Bring together community members involved in guidelines development to maximize standardisation and enable knowledge transfer
-
Facilitate development of additional guidelines where needed
-
Identify use cases at different levels, e.g., national, disciplinary, funder and specific software
-
Trial guidelines with use cases and evaluate success
These activities will engage different stakeholders, including those that will:
-
Endorse and promote the guidelines
-
Use the guidelines
-
Provide training on the guidelines
Anyone interested in the progress of this group is invited to attend. This work will be of value to software project owners, researchers, users of research software, research software engineers, software developers who publish their software, software catalogue maintainers, repository managers, software preservation and archival experts, policymakers who are responsible for defining digital policies, and organisations that create, fund, modify, manage, share, protect, and/or preserve research software.
We would also like to invite members of RDA groups whose interests overlap with this group: CURE FAIR WG, Software Source Code IG, Software Source Code Identification WG, FAIR Data Maturity Model, Research Metadata Schemas WG, FAIR data maturity model, Go FAIR IG, Exposing Data Management Plans WG, Active Data Management Plans IG, Research Funders and Stakeholders on Open Research Data Management Policies and Practices IG, and Global Open Research Commons IG.
Software has become essential for research. To improve the findability, accessibility, interoperability, and reuse of research software, it is desirable to develop and apply a set of FAIR Principles for Research Software. FAIR4RS WG is a coordination group to leverage existing community-led discussions on how to define and effectively apply FAIR principles for research software, to achieve adoption of these principles. Application of the FAIR principles to software will continue to advance the aims of the open science movement and support research innovation. The FAIR For Research Software Working Group (FAIR4RS WG) is jointly convened as an RDA Working Group, FORCE11 Working Group, and Research Software Alliance (ReSA) Taskforce in recognition of the importance of this work for the advancement of the research sector.
FAIR4RS WG has completed its first output through creation of a community-endorsed definition of FAIR for research software. The milestones for the next year, as listed in the WG Case Statement, include developing guidelines on how to apply the FAIR principles for research software, as well as a plan for adoption of the guidelines, and adoption examples. Details of the FAIR4RS WG structure and community engagement is available in The FAIR4RS team: Working together to make research software FAIR.
FAIR Principles for Research Software (FAIR4RS Principles) - this draft of the FAIR4RS first output was open for community review across the communities of the Research Software Alliance (ReSA), Research Data Alliance (RDA) and FORCE11 in June-July 2021.
The FAIR4RS team: Working together to make research software FAIR” - details about the structure and community engagement of this Working Group.
- 746 reads