What role should a domain-specific repository play in treating code as a first class research product? [poster]

Presented at AGU Fall Meeting 10 – 14 December 2018, Washington, D.C. The Biological and Chemical Oceanography Data Management Office (BCO-DMO) is a publicly accessible earth science data repository created to curate, publicly serve (publish), and archive digital data and information from biological...

Full description

Bibliographic Details
Main Authors: Biddle, Matt, Ake, Hannah, Copley, Nancy, Kinkade, Danie, Rauch, Shannon, Saito, Mak A., Shepherd, Adam, Wiebe, Peter, York, Amber
Format: Conference Object
Language:unknown
Published: 2018
Subjects:
D.C
Online Access:https://hdl.handle.net/1912/23633
Description
Summary:Presented at AGU Fall Meeting 10 – 14 December 2018, Washington, D.C. The Biological and Chemical Oceanography Data Management Office (BCO-DMO) is a publicly accessible earth science data repository created to curate, publicly serve (publish), and archive digital data and information from biological, chemical and biogeochemical research conducted in coastal, marine, great lakes and laboratory environments. The BCO-DMO repository works closely with investigators funded through the NSF OCE Division’s Biological and Chemical Sections and Antarctic Organisms & Ecosystems. The office provides services that span the full data life cycle, from data management planning support and DOI creation, to archiving with appropriate national facilities. Recently, more and more of the projects submitted to BCO-DMO represent modeling efforts which further increase our knowledge of the chemical and biological properties within the ocean ecosystem. But, as a repository traditionally focused on observational data as a primary research output, what roles should domain-specific data repositories play in this field? Recognizing code as a first class research product, how should repositories support the discovery, access and reuse of code and software used in hypothesis driven research? We feel the time is at hand for the community to begin a concerted and holistic approach to the curation of code and software. Such strategy development should begin with asking what is the appropriate output to curate? What is the minimum metadata required for re-use? How should code be stored and accessed? Should repositories support or facilitate peer reviewing code? The answers to these questions will better inform domain-specific repositories on how to better manage code as a first class research asset in order to support the scientific community. This presentation will explore these topics, inviting discussion from the audience to advance a collective strategy. NSF #1435578