Nine Best Practices for Research Software Registries and Repositories: A Concise Guide

• URL: http://arxiv.org/abs/2012.13117v1
• Date: Thu, 24 Dec 2020 05:37:54 GMT
• Title: Nine Best Practices for Research Software Registries and Repositories: A Concise Guide
• Authors: Task Force on Best Practices for Software Registries: Alain Monteil (INRIA), Alejandra Gonzalez-Beltran (Science and Technology Facilities Council, UK Research and Innovation), Alexandros Ioannidis (CERN), Alice Allen (University of Maryland), Allen Lee (Arizona State University), Anita Bandrowski (University of California at San Diego), Bruce E. Wilson (Oak Ridge National Laboratory), Bryce Mecum (University of California at Santa Barbara), Cai Fan Du (University of Texas at Austin), Carly Robinson (DOE-OSTI), Daniel Garijo (University of Southern California), Daniel S. Katz (University of Illinois at Urbana-Champaign), David Long (Brigham Young University), Genevieve Milliken (NYU Bobst Library), Herv\'e M\'enager (Institut Pasteur), Jessica Hausman (NASA Jet Propulsion Laboratory), Jurriaan H. Spaaks (Netherlands eScience Center), Katrina Fenlon (University of Maryland), Kristin Vanderbilt (University of New Mexico), Lorraine Hwang (University of California at Davis), Lynn Davis (DOE-OSTI), Martin Fenner (DataCite), Michael R. Crusoe (CWL), Michael Hucka (California Institute of Technology), Mingfang Wu (Australian Research Data Commons), Neil Chue Hong (University of Edinburgh), Peter Teuben (University of Maryland), Shelley Stall (American Geophysical Union), Stephan Druskat (German Aerospace Center (DLR)/University Jena/Humboldt-Universit\"at zu Berlin), Ted Carnevale (Yale University), Thomas Morrell (California Institute of Technology)
• Abstract summary: We present a set of nine best practices that can help managers define the scope, practices, and rules that govern individual registries and repositories. These best practices were distilled from the experiences of the creators of existing resources, convened by a Task Force of the FORCE11 Software Implementation Working Group during the years 2011 and 2012.
• Score: 63.52960372153386
• License: http://creativecommons.org/licenses/by/4.0/
• Abstract: Scientific software registries and repositories serve various roles in their respective disciplines. These resources improve software discoverability and research transparency, provide information for software citations, and foster preservation of computational methods that might otherwise be lost over time, thereby supporting research reproducibility and replicability. However, developing these resources takes effort, and few guidelines are available to help prospective creators of registries and repositories. To address this need, we present a set of nine best practices that can help managers define the scope, practices, and rules that govern individual registries and repositories. These best practices were distilled from the experiences of the creators of existing resources, convened by a Task Force of the FORCE11 Software Citation Implementation Working Group during the years 2019-2020. We believe that putting in place specific policies such as those presented here will help scientific software registries and repositories better serve their users and their disciplines.

Related papers

• On the Creation of Representative Samples of Software Repositories [1.8599311233727087]
  With the emergence of social coding platforms such as GitHub, researchers have now access to millions of software repositories to use as source data for their studies. Current sampling methods are often based on random selection or rely on variables which may not be related to the research study. We present a methodology for creating representative samples of software repositories, where such representativeness is properly aligned with both the characteristics of the population of repositories and the requirements of the empirical study.
  arXiv  Detail & Related papers  (2024-10-01T12:41:15Z)
• An Overview and Catalogue of Dependency Challenges in Open Source Software Package Registries [52.23798016734889]
  This article provides a catalogue of dependency-related challenges that come with relying on OSS packages or libraries. The catalogue is based on the scientific literature on empirical research that has been conducted to understand, quantify and overcome these challenges.
  arXiv  Detail & Related papers  (2024-09-27T16:20:20Z)
• How to Understand Whole Software Repository? [64.19431011897515]
  An excellent understanding of the whole repository will be the critical path to Automatic Software Engineering (ASE) We develop a novel method named RepoUnderstander by guiding agents to comprehensively understand the whole repositories. To better utilize the repository-level knowledge, we guide the agents to summarize, analyze, and plan.
  arXiv  Detail & Related papers  (2024-06-03T15:20:06Z)
• Open Source in Lab Management [0.0]
  This document explores the advantages of integrating open source software and practices in managing a scientific lab. The broader goal is to promote transparent, reproducible science by adopting open source tools.
  arXiv  Detail & Related papers  (2024-05-13T14:18:20Z)
• FAIR-USE4OS: Guidelines for Creating Impactful Open-Source Software [0.41942958779358663]
  This paper extends the FAIR (Findable, Accessible, Interoperable, Reusable) guidelines to provide criteria for assessing if software conforms to best practices in open source. The FAIR-USE4OS guidelines will allow funders and researchers to more effectively evaluate and plan open source software projects.
  arXiv  Detail & Related papers  (2024-02-05T09:15:20Z)
• EASRec: Elastic Architecture Search for Efficient Long-term Sequential Recommender Systems [82.76483989905961]
  Current Sequential Recommender Systems (SRSs) suffer from computational and resource inefficiencies. We develop the Elastic Architecture Search for Efficient Long-term Sequential Recommender Systems (EASRec) EASRec introduces data-aware gates that leverage historical information from input data batch to improve the performance of the recommendation network.
  arXiv  Detail & Related papers  (2024-02-01T07:22:52Z)
• How is Software Reuse Discussed in Stack Overflow? [12.586676749644342]
  We present an empirical study of 1,409 posts to better understand the challenges developers face when reusing code. Our findings show that 'visual studio' is the top occurring bigrams for question posts, and there are frequent design patterns utilized by developers for the purpose of reuse.
  arXiv  Detail & Related papers  (2023-11-01T03:13:36Z)
• The Software Heritage Open Science Ecosystem [0.0]
  Software Heritage is the largest public archive of software source code and associated development history. It has archived more than 16 billion unique source code files coming from more than 250 million collaborative development projects. It supports empirical research on software by materializing in a single Merkle direct acyclic graph the development history of public code. It ensures availability and guarantees integrity of the source code of software artifacts used in any field that relies on software to conduct experiments.
  arXiv  Detail & Related papers  (2023-10-16T11:32:03Z)
• Lessons from Formally Verified Deployed Software Systems (Extended version) [65.69802414600832]
  This article examines a range of projects, in various application areas, that have produced formally verified systems and deployed them for actual use. It considers the technologies used, the form of verification applied, the results obtained, and the lessons that the software industry should draw regarding its ability to benefit from formal verification techniques and tools.
  arXiv  Detail & Related papers  (2023-01-05T18:18:46Z)
• Code Librarian: A Software Package Recommendation System [65.05559087332347]
  We present a recommendation engine called Librarian for open source libraries. A candidate library package is recommended for a given context if: 1) it has been frequently used with the imported libraries in the program; 2) it has similar functionality to the imported libraries in the program; 3) it has similar functionality to the developer's implementation, and 4) it can be used efficiently in the context of the provided code.
  arXiv  Detail & Related papers  (2022-10-11T12:30:05Z)

This list is automatically generated from the titles and abstracts of the papers in this site.

This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.