Lessons Learned from FAIRCORE4EOSC and FAIR-IMPACT: Research Software Outputs

This presentation provided an overview of key outcomes from the FAIRCORE4EOSC and FAIR-IMPACT projects as they relate to research software. Sharing the results from the projects: FAIRCORE4EOSC: The RSAC components connecting Software Heritage with Scholarly repositories: Zenodo (CERN), DANS Dataverse’s instance, Publishers: Dagstuhl, Episciences Aggregators: swMath, OpenAire & Datacite Deploying in 2025 the EOSC mirror of Software Heritage at GRNET SWHID ISO Standardization - published ISO/IEC 18670:2025 FAIR-IMPACT: Maintaining the Research Software MetaData guidelines https://github.com/FAIR-IMPACT/RSMD-guidelines Contributing to the CodeMeta initiative, towards FAIRer mappings FUJI - Implementation of Research Software FAIR assessment And the deliverables: - D5.2 - Metrics for automated FAIR software assessment in a disciplinary context (1.1). Zenodo. https://doi.org/10.5281/zenodo.15535629 - D4.4 - Guidelines for recommended metadata standard for research software within EOSC (V1.0). Zenodo. https://doi.org/10.5281/zenodo.10786147 - D6.1 | Report on Standardisation and Curation of Software Metadata and PIDs. Zenodo. https://doi.org/10.5281/zenodo.14509418 - D6.2 - Report on Research Software Archival APIs and Connectors. Zenodo. https://doi.org/10.5281/zenodo.15552472 It emphasized three foundational lessons for building a community-driven vision for Research Software:(1) Clear policy frameworks are essential for cross-infrastructure coordination and avoiding fragmentation;(2) Dedicated technical support and resources are needed to enable streamlined and sustainable integration;(3) Institutional engagement and training are critical to embed FAIR-aligned practices across the research ecosystem. The talk also introduced the OSPO-RADAR project, funded by the Sloan P. Foundation, designed to support institutions through a software dashboard, CodeMeta standard adoption, and a helpdesk service. A call to action was issued to promote global coordination and institutional policies for research software recognition. Finally, the presentation framed key challenges for the OA7 workstreams—and the need for actionable, low-effort, high-impact recommendations to EOSC.