What We Want

First off, we rely on the individual scientists to determine what files they consider a "data set". Our basic guidance is to build a data set around a single "event". For a cruise, example events include a single CTD cast, multicore deployment, long line set, net tow, etc. For a laboratory analysis, events may include single sample analyses by a mass spectrometer or other instrument. With models, a single run or experiment may result in a very large data set, so an event may include all files for a given increment in time (e.g., month, year, etc.). For those collecting instrumental or sample observations, we are seeking both the original and processed (cleaned/analyzed) data. For example, CTD data should include the raw data as collected by the instrumentation as well as any files created by the CTD software (e.g., Seabird data processing). We will accept any type of electronic data file (e.g., excel, ascii, netcdf) or digital image (e.g., tiff, jpeg, gif) from an instrument or analysis funded by Deep- C. Note that we do not accept physical samples (e.g., cores, fish, etc.).

File names should include the following (as a minimum):

• Activity, event, or sample description (e.g., CTD, beach_tar, core, ADCP, etc.)
• Date and time of collection/creation (UTC time)
• Location of collection (Either a Deep-C site name or Lat/Lon coordinate)
• Event or sample ID (when available, e.g., from Deep-C cruise workbook)