Persistent Identifiers for Field Deployments: A Missing Link in the Provenance Chain
Abstract
Research in the geosciences is characterized by a wide range of complex and costly field deployments including oceanographic cruises, submersible dives, drilling expeditions, seismic networks, geodetic campaigns, moored arrays, aircraft flights, and satellite missions. Each deployment typically produces a mix of sensor and sample data, spanning a period from hours to decades, that ultimately yields a long tail of post-field products and publications. Publishing persistent, citable identifiers for field deployments will facilitate 1) preservation and reuse of the original field data, 2) reproducibility of the resulting publications, and 3) recognition for both the facilities that operate the platforms and the investigators who secure funding for the experiments. In the ocean domain, sharing unique identifiers for field deployments is a familiar practice. For example, the Biological and Chemical Oceanography Data Management Office (BCO-DMO) routinely links datasets to cruise identifiers published by the Rolling Deck to Repository (R2R) program. In recent years, facilities have started to publish formal/persistent identifiers, typically Digital Object Identifiers (DOIs), for field deployments including seismic networks, oceanographic cruises, and moored arrays. For example, the EarthChem Library (ECL) publishes a DOI for each dataset which, if it derived from an oceanographic research cruise on a US vessel, is linked to a DOI for the cruise published by R2R. Work is underway to create similar links for the IODP JOIDES Resolution Science Operator (JRSO) and the Continental Scientific Drilling Coordination Office (CSDCO). We present results and lessons learned including a draft schema for publishing field deployments as DataCite DOI records; current practice for linking these DOIs with related identifiers such as Open Researcher and Contributor IDs (ORCIDs), Open Funder Registry (OFR) codes, and International Geo Sample Numbers (IGSNs); and consideration of other identifier types for field deployments such as UUIDs and Handles.
- Publication:
-
AGU Fall Meeting Abstracts
- Pub Date:
- December 2016
- Bibcode:
- 2016AGUFMIN43B1699A
- Keywords:
-
- 1904 Community standards;
- INFORMATICSDE: 1908 Cyberinfrastructure;
- INFORMATICSDE: 1912 Data management;
- preservation;
- rescue;
- INFORMATICSDE: 1930 Data and information governance;
- INFORMATICS