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

dc.contributor.author Biddle, Matt
dc.contributor.author Ake, Hannah
dc.contributor.author Copley, Nancy
dc.contributor.author Kinkade, Danie
dc.contributor.author Rauch, Shannon
dc.contributor.author Saito, Mak A.
dc.contributor.author Shepherd, Adam
dc.contributor.author Wiebe, Peter
dc.contributor.author York, Amber
dc.date.accessioned 2019-02-06T18:23:52Z
dc.date.available 2019-02-06T18:23:52Z
dc.date.issued 2018-12-13
dc.description Presented at AGU Fall Meeting 10 – 14 December 2018, Washington, D.C. en_US
dc.description.abstract 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. en_US
dc.description.sponsorship NSF #1435578 en_US
dc.identifier.doi 10.1575/1912/23633
dc.identifier.uri https://hdl.handle.net/1912/23633
dc.rights Attribution 4.0 International *
dc.rights.uri http://creativecommons.org/licenses/by/4.0/ *
dc.subject Data management en_US
dc.subject Provenance en_US
dc.subject Data repository en_US
dc.subject Worfklow en_US
dc.subject Modeling Conference Name: AGU 2018 Conference Location: Washington, D.C en_US
dc.title What role should a domain-specific repository play in treating code as a first class research product? [poster] en_US
dc.type Presentation en_US
dspace.entity.type Publication
relation.isAuthorOfPublication 5a1ec46b-03cf-40c3-b294-551ee5f54cf7
relation.isAuthorOfPublication fabbcd8e-ce7a-4ede-b638-e47af490c67c
relation.isAuthorOfPublication 18a11994-2e73-4de3-adf6-cda9a0ddddb6
relation.isAuthorOfPublication 09cddcd0-c893-4334-8a78-292171f697b4
relation.isAuthorOfPublication 45bc735f-0c2f-4a1f-bad1-b8ccc7f7da61
relation.isAuthorOfPublication acaa04eb-34c3-4dcd-a8a7-e2a6c525e6cb
relation.isAuthorOfPublication 0fd499a5-2c8f-4e73-afd8-b33db071dd97
relation.isAuthorOfPublication cb145654-8987-45bf-8412-902f2c36b648
relation.isAuthorOfPublication 8c6806d4-c72e-47a8-b713-fe927d8dce80
relation.isAuthorOfPublication.latestForDiscovery 5a1ec46b-03cf-40c3-b294-551ee5f54cf7
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
2018_AGU_Poster_FINAL.pdf
Size:
9.03 MB
Format:
Adobe Portable Document Format
Description:
AGU_Poster_2018_Dec
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.89 KB
Format:
Item-specific license agreed upon to submission
Description: