Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

FAIR principles for research software

  • Creator
    Discussion
  • #134272

    Neil Chue Hong
    Participant

    Introduction (30 minutes)

    What makes software different from data with respect to the application of the FAIR principles? (5 minutes)

    Raising awareness of the work done so far on FAIR for software. (5 minutes)

    Overview of related projects including CodeMeta, software identification and citation, FAIR maturity model. (5 minutes)

    What can be measured and what cannot be measured. Overcoming the tyranny of metrics for software. (5 minutes)

    Q&A session on FAIR and software (10 minutes)

    Parallel discussion groups of technical issues relating to FAIR for research software (30 minutes)

    What controlled vocabularies are currently available to describe software and its associated metadata?

    Software versioning and how to handle releases? A discussion about software provenance. 

    What aspects should be taken into account in order to create indicators to measure FAIRness in software? How can automatic measurement be used to guarantee sustainability?

    Outputs and impact (30 minutes)

    Discussion and feedback on proposed WG (10 minutes)

    Initial draft of new working group aims (15 minutes)

    Wrap-up and next steps (5 minutes)
     

    The group session will be recorded using online collaborative meeting notes and welcomes remote participation.

    Additional links to informative material

    Towards FAIR principles for research software

    Pre-print (with reviews): https://datasciencehub.net/paper/towards-fair-principles-research-software

    Publication: https://doi.org/10.3233/DS-190026 (links to https://content.iospress.com/articles/data-science/ds190026)

    Activities that led to the paper:

    https://www.rd-alliance.org/group/software-source-code-ig/wiki/what-fair-software-source-code-we-need-your-input

    Activities after the publication of the paper:

    https://fair-software.nl/

    https://www.slideshare.net/annalenalamprecht/towards-fair-principles-for-research-software/

    Metrics and code for assessing software FAIRness:

    https://github.com/inab/FAIRsoft 

    Software Source Code IG past meetings

    SSC IG wiki and resources from meetings at P10 and P11, and P13.

    The SSC IG session “Research Software Source Code: why and how do we care?” at P13 collected references about FAIR for Software Source Code in the group’s wiki as well as running a group activity on how to make software FAIR

    A Research Software Hackathon at FORCE2019, which included activities around FAIR for research software, was jointly organised by the RDA/FORCE11 Software Source Code Identification WG and FORCE11 Software Citation Implementation WG. Recap: https://www.rd-alliance.org/group/software-source-code-ig-software-source-code-identification-wg/post-1

    BoF at P14 on Curating for FAIR and reproducible data and code and the collaborative notes

    Other initiatives around FAIR principles for software

    FAIR is not fair enough blog post https://danielskatzblog.wordpress.com/2017/06/22/fair-is-not-fair-enough/

    The FAIRsFAIR project is currently working on the subject of FAIR services and FAIR software. A first milestone about software is due in May 2020, titled: “Assessment report on FAIRness of research software”.

    Avoid conflict with the following group (1)
    RDA/FORCE11 Software Source Code Identification WG

    Avoid conflict with the following group (3)
    FAIR Data Maturity Model WG

    Meeting objectives

    Remote Access Registration:  https://uqz.zoom.us/webinar/register/WN_Qwb7FiCqRkCn-DhCwH9Qyw 
    Collaborative Notes Link: https://drive.google.com/open?id=19-VzECamBP7V1Aa-6zug0SbAGk8gndm2avjtrz…

    Software has become essential for research. To improve the findability, accessibility, interoperability, and reuse of the software used, it is desirable to apply the FAIR Guiding Principles. Many of the FAIR principles can be directly applied to research software, where software and data can be treated as the same kind of digital research objects. However, specific characteristics of software – such as their executability, composite nature, and continuous evolution and versioning – make it necessary to revise and extend the original principles.
     
    This session continues community-led discussions (at RDA, FORCE11 and ELIXIR) on how to effectively apply FAIR principles to research software. The goal of this session is to assess the interest across the community on the topic of adapting and defining FAIR principles for research software with the aim of defining the scope, outputs and leadership of a new working group to take forward development of the principles.
     
    The objectives of the meeting are:

    Provide updates on community efforts around FAIR principles for research software, including:

    Summary of work presented in “Towards FAIR principles for research software”.
    Recap of previous discussions at RDA on FAIR software including Software Source Code IG session at RDA P13 and Curating for FAIR and reproducible data and code BoF at P14. 
    Summary of other initiatives around FAIR principles for software, including FAIR metrics, software metadata, software identifiers. 

    Engage the wider community in the importance of adapting or reinterpreting the FAIR principles for research software.

    Clarify the scope of the FAIR principles in relation to different forms of software at different granularity levels (e.g. notebooks, libraries, applications, services).

    Discuss the formation of a new Working Group, including scope, outputs, membership and leadership, to take forward the adaptation and definition of FAIR principles for research software, including: 

    Plan the process for coming to consensus on the FAIR principles for research software.

    Identify if the definition of metrics to automatically measure software FAIRness is in scope for this WG or should become a separate WG.

    Privacy Policy
    1

Log in to reply.