Intern:TSG Underway Data

On this page you will find information on the requirements for submitting, archiving and publishing and, additionally, for curating Thermosalinograph (TSG) Underway Data, as well as examples of datasets.

Comments specifically for curators are shown as bold

Please note
SOPs for the curation and publication of Underway Data are currently being revised within the DAM Underway Research Data Project to ensure fulfilling the FAIR data principles with every Underway data publication.

This entire page is currently under construction and will be updated continuously

DAM Underway Research Data Project background
! Under Construction !

Underway Data from different devices
During DAM pilot phase workflows for data curation, archiving and publication at PANGAEA are being revised. Besides Thermosalinograph (TSG), other types of processed Underway Data from different devices are in the scope of the project:
 * ADCP Underway Data
 * CTD Underway Data
 * Ferrybox Underway Data
 * Bio-optical Sensors Underway Data

Furthermore, historical and recent Bathymetry data and corresponding workflows are under revision in the framework of DAM.

Example of an Underway TSG Data Publication
! Under Construction - dataset is still in review!

TSG MSM88/2: https://doi.pangaea.de/10.1594/PANGAEA.918071

Standardized Meta-Information of Underway Data
The following information needs to be included in any Underway Data submission at PANGAEA.

List of Authors
! Under Construction !

Usually, the list of authors of Underway Data contain the scientist responsible for the sampling device and the chief scientist. However, a final regulation on how to proceed with the list of authors in all Underway Data sets in the same way is still pending. The same goes for the PI, the contact person responsible for the data.

Dataset Title
The title of the data publication should be generalized and is defined by the specific [ship], [cruise] and [device] (see ).

Abstract
For Underway Data a generalized Abstract per device may be created that will be adapted to each dataset regarding [ship], [cruise] and certain peculiarities.

Cruise Report
The Cruise Report is usually already archived at the Technische Informationsbibliothek and will be linked to the dataset by a data curator (see this example).

The relation type for the Cruise Report is "further details"

Data Processing Report
The Data Processing Report contains information on processing and quality control procedures. It enables to reproduce the processed data from raw data. The preferred format for submission is pdf (see this example).

The relation type for the Data Processing Report is "further details"

! Under construction !

Currently, the Data Processing Reports are being archived at PANGAEA (except for reports for data obtained during Polarstern and Heincke cruises); A long-term solution will include the assignment of a doi for each Data Processing Report. Templates for Data Processing Reports are currently being revised/created within DAM.

It is not yet clear where the Data Processing Reports will be archived; as a workaround we save them to a server and create a reference to download them via the dataset's webpage.

Raw Data
If possible, the raw data should be linked to the processed dataset. This link may lead to an external source, but it may also be an PANGAEA-internal link.

Further References
These may, for example, include Salinity samples as .txt files, netcdf files, etc. They will be stored on one of PANGAEA's servers and can be accessed via a link in the reference section of the data publication.

'''These files are archived on Store. A reference will feature the link to download them (see this example of a linked -nc file in an ADCP Underway Dataset).'''

Cruise Label
The [Cruise] Label given should always include [ship]number/leg (e.g.: MSM88/2).

Event label(s)
The Event Label(s) should be part of each data submission. Event labels equal the station labels and provide meta-information for the data. The Underway Event Label is being created onboard and should always be used when referring to Underway Data (current exception: CTD Data - several events needed). The format of Event Labels format consists of the cruise label and the station ending: [ship]number/leg_station (e.g.: MSM88/2_0_Underway-2).

Event labels are imported with the station lsit directly from DShip; if during the process of Underway Data archiving more precise coordinates, times or other specifications come up, the event may be corrected by the curator.

Device /Sensor
Information on the device used for measuring should also be provided, so it can be linked to the measured parameters.

The sensor information should be added with every event import in the future, as it will be exportable from DShip; however, if this is not yet possible, it would be great to include the Sensor information given by the submitter if possible.

File name
A generalized file name should be used per device (see )

File Formats
Possible file formats include .txt, .tab, .csv, .xlsx. The encoding is preferably UTF-8.

Layout
The authors are asked to not include any header except column names. The decimal separator should be "." and the number of decimals should always reflect the measurement precision. Not available numbers are displayed as blanks in PANGAEA. They should be included as blanks, "NaN", "NA" or event "999.999" in the data table.

Parameters of the data table
''' ! Under construction - parameters may still be changed added for future Underway Data Publications ! '''

This table gives an overview on the parameter names and specifications as they will appear on the web and in the download file of the data. If possible, these names should be included in the submission data table. Also the format and unit of data should be submitted as displayed here. The methods will be included in the data publication by the data curator as specified in the submitted meta-information.

The IDs of the parameters and methods used at the moment are featured in this table for import files or for use in config of the dataset Note: If Quality Flags are used, the Flagging code needs to be explained and will be archived in the parameter comment.