Skip to content

Latest commit

 

History

History
125 lines (93 loc) · 5.01 KB

paper.md

File metadata and controls

125 lines (93 loc) · 5.01 KB
Raw
title title_short tags authors affiliations date cito-bibliography event biohackathon_name biohackathon_url biohackathon_location group git_url authors_short
BioHackEU24 report: Recognising research software contributions leveraging the ELIXIR infrastructure
BioHackEU24 #25: Software contributions in APICURON
APICURON
research recognition
OpenEBench
ELIXIR
name orcid affiliation
Adel Bouhraoua
0000-0001-9531-6339
1
name orcid affiliation
Gavin Farrel
1
name orcid affiliation
José M. Fernández
0000-0002-4806-5140
2
name index
BioComputingUP, University of Padova
1
name index
Barcelona Supercomputing Center (BSC), ELIXIR Spain, Barcelona, Spain
2
8 November 2024
paper.bib
BH24EU
BioHackathon Europe 2024
Barcelona, Spain, 2024
Project 25
Bouhraoua \emph{et al.}

Introduction

As part of the BioHackathon Europe 2024, the proposed project has aimed to enhance the capabilities of the ELIXIR infrastructure to track, credit, and recognise software contributions made by research software engineers. The project has sought to foster collaboration and engagement within the ELIXIR Communities and platforms by working with different stakeholders, including individual contributors to research software, to indicators that help measure the value of these contributions.

The primary objective of this project is to promote a strong sense of community by recognising individual software contributions. We plan to connect APICURON and GitHub to track open-source research software contributions and reward each contributor for their efforts. We will also link OpenEBench evaluation data to this process by crosslinking GitHub repositories available in the Software Observatory section with APICURON. This will involve retrieving activity data from GitHub and OpenEBench, processing it, and integrating it into the APICURON platform. Recognition items will be pushed to ORCID from APICURON and made available for third-party services.

We will leverage the involvement of APICURON and OpenEBench in the Data and Tools platforms and in the ELIXIR STEERS and EVERSE projects. These platforms and projects provide a network of stakeholders and guidance for implementing a fair recognition infrastructure.

The project's usefulness lies in its ability to address a significant gap in the recognition and valuation of research software contributions. By providing a framework for recognition, we can incentivise and motivate developers to contribute to open-source software projects, leading to improved software quality and reproducibility and positively impacting the environment by reducing the carbon footprint.

Formatting

This document use Markdown and you can look at this tutorial.

Subsection level 2

Please keep sections to a maximum of only two levels.

Tables and figures

Tables can be added in the following way, though alternatives are possible:

Table: Note that table caption is automatically numbered and should be given before the table itself.

Header 1 Header 2
item 1 item 2
item 3 item 4

A figure is added with:

Caption for BioHackrXiv logo figure

Other main section on your manuscript level 1

Lists can be added with:

  1. Item 1
  2. Item 2

Citation Typing Ontology annotation

You can use CiTO annotations, as explained in this BioHackathon Europe 2021 write up and this CiTO Pilot. Using this template, you can cite an article and indicate why you cite that article, for instance DisGeNET-RDF [@citesAsAuthority:Queralt2016].

The syntax in Markdown is as follows: a single intention annotation looks like [@usesMethodIn:Krewinkel2017]; two or more intentions are separated with colons, like [@extends:discusses:Nielsen2017Scholia]. When you cite two different articles, you use this syntax: [@citesAsDataSource:Ammar2022ETL; @citesAsDataSource:Arend2022BioHackEU22].

Possible CiTO typing annotation include:

  • citesAsDataSource: when you point the reader to a source of data which may explain a claim
  • usesDataFrom: when you reuse somehow (and elaborate on) the data in the cited entity
  • usesMethodIn
  • citesAsAuthority
  • citesAsEvidence
  • citesAsPotentialSolution
  • citesAsRecommendedReading
  • citesAsRelated
  • citesAsSourceDocument
  • citesForInformation
  • confirms
  • documents
  • providesDataFor
  • obtainsSupportFrom
  • discusses
  • extends
  • agreesWith
  • disagreesWith
  • updates
  • citation: generic citation

Results

Discussion

...

Acknowledgements

...

References