13 FEB 2024
Collaborative session notes https://docs.google.com/document/d/1ItNozXXs6GSmdAc9cn-bCnLk5boi7fhXcqXUAWuEZLc/edit?usp=drive_link
Group(s) submitting the application:
Meeting objectives:
“Open science infrastructures are often the result of community-building efforts, which are crucial for their long-term sustainability and therefore should be not-for-profit and guarantee permanent and unrestricted access to all public to the largest extent possible.” (UNESCO Recommendation on Open Science, 2021).
In this meeting, we invite RDA members with a keen interest in software, especially software source code, to engage in meaningful discussions encompassing various aspects of software in the research lifecycle. Our primary focus will be on the critical importance of building bridges between infrastructures and communities, because research software usually depends on many pieces of software that aren’t in research.
During RDA P22, we will explore different infrastructures, tools and bridges that support researchers on their quest to submit their software as first class outputs. The demos will include:
- Software Heritage: the universal source code archive
- InvenioRDM software submission: developed by CERN, it is the engine behind Zenodo
- HAL & Episciences: the moderated workflow in France’s scholarly repository and the result in the Open Access journal
- SwMath: the software portal for the mathematics community and the vital connection to publications
After an introduction and a few demos we will facilitate an online activity on adopting the upcoming infrastructures, services and tools in different communities. The main questions:
- Do researchers know what possibilities they have regarding Research Software?
- How do we get researchers to use these infrastructures, services and tools?
- Are these infrastructures, services and tools increasing Research Software FAIRness? (hint: Absolutely!)
Expected outcomes:
- Collect ideas on how to increase adoption of services that can support Research Software
- Empower participants to build together bridges between the existing infrastructures, services and tools and the communities that are searching for solutions.
- Knowledge of the tools and services will equip participants with practical insights into the capabilities of the existing solutions.
- Awareness of FAIR4RS and Other Community Efforts: Attendees will be updated on the latest developments in the FAIR4RS (Findable, Accessible, Interoperable, and Reusable for Research Software) initiative and other collaborative efforts within the research software community.
Join us in this session to contribute toward the adoption of research software infrastructures, services and tools and its pivotal role in ensuring trustworthy and reproducible research outcomes.
Don’t miss out on this opportunity to connect with experts, exchange knowledge, and contribute to addressing challenges in making software a first class output. Mark your calendars and join us for a productive session.
Meeting agenda:
Join us for an engaging event focused on encouraging adoption of infrastructures supporting research software
– Introduction to the group (5-10 min)
– icebreaker 1
– Infrastructures demos
- Software Heritage: the universal source code archive (7 min)
- InvenioRDM software submission: developed by CERN, it is the engine behind Zenodo (7 min)
- HAL & Episciences: the moderated workflow in France’s scholarly repository and the result in the Open Access journal (7 min)
- SwMath: the software portal for the mathematics community and the vital connection to publications (7 min)
– Activity: “Adoption of infrastructures for research software ” (40 min)
– Closing (10-15 min)
– activity conclusion
– update on FAIR4RS steps in 2024
– announcement and call for participants for FAIR4RS adoption stories for RDA P23
During this event, we will discuss ongoing initiatives and collaborative efforts related to software source code management, identification, reproducibility, and quality. The demonstrations of services, infrastructures and tools will provide valuable insights into existing possibilities for researchers when it comes to disseminating Research Software.
In our adoption activity, we aim to go beyond just picking up new tools or services. We’ll look at embracing important principles like those found in the Research Software MetaData Guidelines or in the FAIR4RS principles and adopting practices that make research software more open, reproducible, and findable. Our approach to adoption is all-encompassing, involving learning, integrating, and eventually advocating for the use of research software infrastructures, services, and tools, all in the service of advancing scientific discovery.
Target Audience:
The target audience for this session comprises: repository managers, software project owners, software catalog maintainers, researchers, research software engineers, archivists, librarians, and others with an interest in the discovery, description and preservation of software source code. This session will be particularly of interest to those who are developing software or assisting with software curation.
Participants should familiarize themselves with current efforts in preserving source code (such as Software Heritage), describing software (e.g. CodeMeta) and citing software (the FORCE11 Software Citation Principles).
Group chair serving as contact person:
Brief introduction describing the activities and scope of the group:
The Software Source Code IG was founded in 2017, after a BoF session at the 9th Plenary. It aims to discuss issues on identification, management, sharing, discovery, archival and provenance of software source code, review and revise metadata for describing and discovering source code, develop guidelines for managing, describing and publishing software source code, collect and publish use cases of current examples and practices, and contribute software related expertise to other groups in the RDA which have a software aspect.
During the P12 SSC IG session, a discussion to create a Working Group dedicated to software source code identification led to the creation of the Software Source Code Identification Working Group [SCID WG] which is a joint RDA and FORCE11 WG. This working group has completed its life-cycle with the supporting output:
“Use cases and identifiers schemes for software source code identification” [1].
At RDA plenary (VP15) we discussed the FAIR principles and started the process of creating a new working group, which was launched at the end of June 2020, the FAIR for research software working group [FAIR4RS WG]. The FAIR4RS WG is a joint initiative with ReSA and FORCE11.
At VP16 we have presented the SCID WG output and other outputs and activities from different RDA and FORCE11 working groups that discuss software. We have also collected software practices in the academic community.
At VP17 we have presented the EOSC SIRS TF [2] and other outputs and activities from different RDA and FORCE11 working groups that discuss software. We have also conducted a mini-workshop about software quality.
At VP18 we had a session about reproducibility, GUIX, the first free software distribution backed by a stable archive and how GUIX is used in a computational center (GRICAD).
At P20 the session was focussed on policies and incentives driving change for software source code recognition in the scholarly ecosystem. Several policies and initiatives were highlighted, including internationally through the FAIR4RS initiative and with academic publishers, at the national governmental level in France, and at the national research infrastructure level in Australia. An activity at the end of the session identified incentives to drive change in software source code practices.
At P21 we delved into the metadata realms with the RSMD Guidelines[4] and the FAIR-IMPACT Metrics for Assessing Research Software FAIRness[5].
References
[1] Research Data Alliance/FORCE11 Software Source Code Identification WG, Allen, A., Bandrowski, A., Chan, P., Di Cosmo, R., Fenner, M., Garcia, L., Gruenpeter, M., Jones, C. M., Katz, D. S., Kunze, J., Schubotz, M. & Todorov, I. T. (2020). Use cases and identifier schemes for persistent software source code identification (V1.1). Research Data Alliance. https://doi.org/10.15497/RDA00053
[2] European Commission. Directorate General for Research and Innovation. (2020). Scholarly infrastructures for research software: report from the EOSC Executive Board Working Group (WG) Architecture Task Force (TF) SIRS. Publications Office. https://doi.org/10.2777/28598
[3] Chue Hong, N. P., Katz, D. S., Barker, M., Lamprecht, A.-L., Martinez, C., Psomopoulos, F. E., Harrow, J., Castro, L. J., Gruenpeter, M., Martinez, P. A., Honeyman, T., Struck, A., Lee, A., Loewe, A., van Werkhoven, B., Jones, C., Garijo, D., Plomp, E., Genova, F., … WG, R. F. (2022). FAIR Principles for Research Software (FAIR4RS Principles) (1.0). https://doi.org/10.15497/RDA00068
[4] Gruenpeter, M., Granger, S., Monteil, A., Chue Hong, N., Breitmoser, E., Antonioletti, M., Garijo, D., González Guardia, E., Gonzalez Beltran, A., Goble, C., Soiland-Reyes, S., Juty, N., & Mejias, G. (2023). D4.4 – Guidelines for recommended metadata standard for research software within EOSC (V1.0 DRAFT NOT YET APPROVED BY EUROPEAN COMMISSION). Zenodo. https://doi.org/10.5281/zenodo.8199104
[5] Chue Hong, N., Breitmoser, E., Antonioletti, M., Davidson, J., Garijo, D., Gonzalez-Beltran, A., Gruenpeter, M., Huber, R., Jonquet, C., priddy, M., Shepeherdson, J., Verburg, M., & Wood, C. (2023). D5.2 – Metrics for automated FAIR software assessment in a disciplinary context (1.0 – DRAFT not yet approved by the European Commission). Zenodo. https://doi.org/10.5281/zenodo.10047401
Type of Meeting:
Working meeting
Additional links to informative material:
For further information, see:
Avoid conflict with the following group (1):
Avoid conflict with the following group (2):
Meeting presenters:
Morane Gruenpeter (Software Heritage), Lars Holm Nielsen (CERN), Maud Medve (INRIA), Maxence Azzouz-Thuderoz (FIZ), TBC
Are you willing to host a second, repeat, session at a different time zone?:
Yes