Sharing code that supports research articles: is it time to align goals and publisher policies?

You are here

24 Feb 2022

Sharing code that supports research articles: is it time to align goals and publisher policies?

Submitted by Lauren Cadwallader


Meeting objectives: 

This BoF aims to understand if there is community interest in the code sharing approaches taken by different publishers (and possibly funders) and if there is a desire and compelling reason to look towards aligning or standardising these at the present time. Code sharing, i.e. openly sharing code that underpins a research article, is related to data sharing in that they are both methods that support reproducibility of research, but is not approached in a consistent manner by publishers or funders, who may or may not include it in data sharing policies. In addition, publishers may also implement code sharing tools, such as code presented in executable forms like a Jupyter notebook or compute capsule. Code sharing can be achieved in a number of different ways and with different goals, for example availability, openness, reproducibility or preservation, which creates differing expectations of the research community.

As both technological and cultural (policy) approaches to code sharing are already being used in the research workflow and scholarly publishing, this BoF session would aim to bring those approaches together to look for common areas of interest that might form the basis of a future RDA group that aims to advance efforts in code sharing.

This session also will explore if there is consensus on where the community should focus efforts to increase code sharing, or if the community - including researchers, publishers, funders and infrastructure providers - is even ready to decide this is an appropriate goal. We would seek thoughts from the community on where efforts should be focused or what evidence is needed to progress work towards community (publishers, funders, researchers who produce and use code, code infrastructure providers, and data managers) alignment when it comes to code sharing. For this session we will discuss source code in a broad sense to encompass the different types of code that can be produced during the research process, e.g. analysis scripts, models, so we are not prescriptive in which areas the community might want to discuss nor are we unduly influencing the outcome of the session. 

The topic of code sharing goals and approaches is not currently served by any RDA group but is closely related to data sharing in certain research fields, if reuse and replication of research are to be fully achieved. The closest related group is the Software Source Code Interest Group, which deals with the mechanics of software sharing (e.g., metadata, archiving, discovery) rather how code is approached from a publication or policy point of view (e.g. should sharing be mandatory, how can different stakeholders facilitate code sharing). Other RDA groups have already looked towards policy issues for research data (e.g., Data policy standardisation and implementation IG and Research Funders and Stakeholders on Open Research and Data Management Policies and Practices IG) and could serve as a model framework for later approaches if there is enough interest in code sharing.

Meeting agenda: 

Collaborative meeting notes: https://docs.google.com/document/d/1LLuBXhyokHJ2-y0KqNS9olt50HEgmGB3tAuO...

 

  1. Presentation of the themes to be discussed:

    • Why share code? Who produces code? Who shares it? What are reasons to not share code?

    • What problems are we trying to solve?

    • Examples of technological and cultural solutions to code sharing

    • Existing principles or best practices

  2. Open questions and discussion. The discussion will be driven by the attendees and react to areas of interest, however, we will initially use the following areas to help guide the discussion:

    • Which problems are most important/urgent?

    • What is the desired outcome for code sharing?

    • Which approaches have the best chance of meeting the outcome at the present time?

    • Which communities/disciplines might be a good focus for this work?

    • Is there interest in developing work on code sharing in an RDA context?

Type of Meeting: 
Working meeting
Short introduction describing any previous activities: 

The individuals proposing/speaking at the event belong to a number of different code/software-related groups, such as the RDA groups FAIR for Research Software WG and Software Source Code IG, and external groups such as FORCE11 Software Citations Group. Individually they all work in areas that are directly related to software/code sharing in a variety of different context, eg as publishers, researchers, research infrastructure providers. Some of the groups previous activities related to this BoF are:

  • Katerbow, M., & Feulner, G. (2018). Recommendations On The Development, Use And Provision Of Research Software. Zenodo. https://doi.org/10.5281/ZENODO.1172988 

  • Cadwallader, L., & Hrynaszkiewicz, I. (forthcoming) A survey of researchers’ code sharing and code reuse practices, and assessment of interactive notebook prototypes. [preprint to be posted on OSF in early March] 

BoF applicant serving as contact person: 
Meeting presenters: 
Lauren Cadwallader, Daniel S. Katz, Tom Honeyman, Alexander Struck, Melissa Harrison
Avoid conflict with the following group (1): 
Avoid conflict with the following group (2): 
Contact for group (email): 
Driven by RDA Organisational Member: 
No