PANGAEA Wiki - User contributions [en]

File:Exp data template.xlsx

2026-04-27T13:32:18Z

Fhoering: Fhoering uploaded a new version of File:Exp data template.xlsx

== Summary ==
Excel template file for experimental data

File:Exp data template.xlsx

2026-04-27T12:59:44Z

Fhoering: Fhoering uploaded a new version of File:Exp data template.xlsx

== Summary ==
Excel template file for experimental data

Experimental data

2026-04-27T12:55:31Z

Fhoering: Excel template was added in previous version and related text slightly modified.

This wiki article describes guidelines on how to prepare experimental data for submission to PANGAEA. Please read our [[Authors Guides]] first. They provide general guidelines on how to prepare your metadata and data for publication in PANGAEA. Check if your experimental data file types and format are accepted by PANGAEA (see [[Authors Guides#Data types and file formats accepted by PANGAEA|respective section in our Authors Guides]]). In addition, you can find the template for experimental data in section 2 and the specific requirements for experimental (meta-)data in section 3 below. If you are dealing with biological experimental data, please also have a look at our specific guidelines for [[Biology]].

== Types of experimental data at PANGAEA ==
Experimental data are collected in a structured trial to test a hypothesis by manipulating variables (treatments) and observing their effects on organisms or environmental samples under (semi-)controlled conditions in natural or artificial settings. Experiments are conducted in multiple research domains, and diverse experimental set-ups exist. The main types of experiments can be summarized as:

'''a) Field experiments''' are ''in situ'' studies designed to compare the effects of different treatments on organisms or other samples in their natural environment or under conditions that closely resemble it. Conditions are partially controlled and the treatments are set up by researchers, e.g. to investigate the growth of an organism in different microhabitats. This also includes mesocosm studies with an open experimental set-up that is influenced by several external environmental factors.

Example datasets:

* Biodiversity experiment: https://doi.org/10.1594/PANGAEA.967077
* Benthocosm experiment: https://doi.org/10.1594/PANGAEA.974781

'''b) Enclosed outdoor experiments''' are set up outside in a closed experimental system, e.g. greenhouse studies or bottle experiments. External factors are better controlled in these systems and therefore the studied sample or organism is less influenced by external environmental factors than in field studies. Relevant environmental factors for these outdoor experiments may e.g. include the natural daily cycle of light or air temperature.

Example datasets:

* Greenhouse experiment: https://doi.org/10.1594/PANGAEA.973270
* Ex-situ cultivation system & subsequent outdoor bottle incubation: https://doi.pangaea.de/10.1594/PANGAEA.973666

'''c) Laboratory experiments''' are (comparative) studies on organisms/samples under controlled conditions set up in a land-based or mobile (e.g. ship-based) laboratory, e.g. behaviour of fish larvae in response to different treatments of carbon dioxide (CO2) partial pressure.

Example datasets:

* Culture experiments with phytoplankton: https://doi.org/10.1594/PANGAEA.964086
* Incubation experiments with sediments: https://doi.org/10.1594/PANGAEA.977247
* Laboratory experiments with artificial kelp/simulated water flow: https://doi.pangaea.de/10.1594/PANGAEA.971269

The following data '''are not considered''' experimental data in PANGAEA:
* '''Field observations''': Data are either directly collected in the field, or organisms/samples are collected and preserved (e.g. frozen) for later analysis in the laboratory, e.g. to determine the abundance of species in space and time. For the submission of field observation data, have a look at our general and domain-specific templates: [[Best practice manuals and templates]].
* '''Computational experiments''' (e.g. modelling data) are only archived at PANGAEA, if a direct relation to a corresponding environmental study exists. For further details, see our article [[Model data and PANGAEA]].

== Template for experimental data ==

[[Media:Exp data template.xlsx|'''Generic spreadsheet template''' for experimental data]]

== Specific requirements for metadata and data ==

=== Metadata - Abstract ===

* For general guidelines, please read: [[Abstract]].
* Describe '''how the experiment was carried out''', and include the '''conditions/treatments before and during''' the experiment.
* Specify the '''type of experiment''' and the '''location''' where the experimental data were collected, e.g. "field experiment in the Wadden Sea at Spiekeroog", or "laboratory experiment at the Marine Biology laboratory at Kiel University".

=== Metadata - Keywords ===
It is '''mandatory to include ONE of the following keywords''' for experimental data to distinguish them from other datasets with field observations in PANGAEA:

* Field experiment
* Laboratory experiment
* Mesocosm experiment
* Greenhouse experiment
* Experiment
Further keywords, such as “ship-based”, “land-based”, the name of the experimental site or the analysed sample/species may be included in addition.

=== Metadata - Event table ===
The Event table (see template above) gives an overview when, where and how the experimental sample, organism or data was collected. Please provide the following event information:

* '''Event(s) for the actual experiments''' including the location and the start and end date/time of the experiments
* If available, additionally provide the '''original sampling event''' of the studied sample/organism in the field prior to the experiments
For general information regarding the event information, please read: [[Event]]. Please use one of the following methods for the events of the actual experiments: “Field experiment”, “Laboratory experiment”, “Mesocosm experiment”, “Greenhouse experiment”, “Experiment”.

=== Metadata - Parameter table ===
This table summarizes all variables (PANGAEA "[[Parameter|parameters]]") that are included in the data table, specifies units, principal investigator(s) and the methods used to generate the data. Please read our [[Authors Guides#Requirements for the data files and their metadata|general requirements for parameter information]] and see our respective template (coming soon). Specific requirements for experimental data include:

* The parameter name should specify whether the values in a column reflect an '''experimental condition/treatment''' '''or a measured variable'''. For treatment parameters, use the syntax '''Treatment: XY''', e.g., "Treatment: temperature", “Treatment: light intensity”, or “Treatment: carbon dioxide”.
* The parameter name may include the type of sample or species name, e.g. “Mytilus edulis, wet mass“.

=== Data table/files ===
Prepare your data according to our general requirements for [[Authors Guides#How to prepare tabular Data:|tabular data]] and [[Authors Guides#How to prepare binary files:|binary files]]. Specific requirements for tabular experimental data include:

* The '''first column''' must be the '''Event label'''. The Event label must correspond to the event information of the actual experiments included in the Event table.
* The '''second column''' must be '''"Type of study'''" to separate experimental datasets from field observations. Use e.g. "Laboratory experiment" or "Field experiment" as values, even if all data are from the same type of study.
* If an organism (e.g. Mytilus edulis) was investigated in the experiment, the species should be indicated in the parameter names. Alternatively, if multiple species were studied, include e.g. the '''column "Species, unique identification"''' for the scientific name of the species even if only one species was studied. Please provide a [https://en.wikipedia.org/wiki/LSID Life Science Identifier] (LSID e.g. <nowiki>urn:lsid:marinespecies.org:taxname:140656</nowiki>) in a '''separate column''', e.g. “'''Species, unique identification (Semantic URI)'''”. We recommend to use [https://www.marinespecies.org/index.php WoRMS] LSIDs for marine organisms or [https://www.itis.gov/ Integrated Taxonomic Information System] (ITIS) LSIDs for terrestrial and limnic organisms.
* Any other type of studied samples (e.g. sediment) can either be indicated in the parameter names or alternatively specified in the '''column "Sample type"'''.
* Include the '''date/time of experiment''' in '''ISO-format''' and as '''UTC''' (use e.g. parameter "Sampling date/time, experiment" or "Date/time start, experiment", "Date/time end, experiment"). Start and end date/time must be provided in separate columns.
* '''For field experiments, include the parameters Latitude and Longitude''' in decimal degrees, and the third dimension '''depth''' (e.g. parameters “Depth, sediment, experiment [m]”, "Depth, water, experiment [m]"), even if all observations are from the surface (value = 0). When data are from a depth range, minimum and maximum depths must be provided in separate columns.
* Use "'''Treatment: XY" parameters''', e.g., "Treatment: Temperature, water" to indicate the experimental conditions/treatments for the data.

Experimental data

2026-04-27T12:45:55Z

Fhoering:

This wiki article describes guidelines on how to prepare experimental data for submission to PANGAEA. Please read our [[Authors Guides]] first. They provide general guidelines on how to prepare your metadata and data for publication in PANGAEA. Check if your experimental data file types and format are accepted by PANGAEA (see [[Authors Guides#Data types and file formats accepted by PANGAEA|respective section in our Authors Guides]]). In addition, you can find the template for experimental data in section 2 (coming soon) and the specific requirements for experimental (meta-)data in section 3 below. If you are dealing with biological experimental data, please also have a look at our specific guidelines for [[Biology]].

== Types of experimental data at PANGAEA ==
Experimental data are collected in a structured trial to test a hypothesis by manipulating variables (treatments) and observing their effects on organisms or environmental samples under (semi-)controlled conditions in natural or artificial settings. Experiments are conducted in multiple research domains, and diverse experimental set-ups exist. The main types of experiments can be summarized as:

'''a) Field experiments''' are ''in situ'' studies designed to compare the effects of different treatments on organisms or other samples in their natural environment or under conditions that closely resemble it. Conditions are partially controlled and the treatments are set up by researchers, e.g. to investigate the growth of an organism in different microhabitats. This also includes mesocosm studies with an open experimental set-up that is influenced by several external environmental factors.

Example datasets:

* Biodiversity experiment: https://doi.org/10.1594/PANGAEA.967077
* Benthocosm experiment: https://doi.org/10.1594/PANGAEA.974781

'''b) Enclosed outdoor experiments''' are set up outside in a closed experimental system, e.g. greenhouse studies or bottle experiments. External factors are better controlled in these systems and therefore the studied sample or organism is less influenced by external environmental factors than in field studies. Relevant environmental factors for these outdoor experiments may e.g. include the natural daily cycle of light or air temperature.

Example datasets:

* Greenhouse experiment: https://doi.org/10.1594/PANGAEA.973270
* Ex-situ cultivation system & subsequent outdoor bottle incubation: https://doi.pangaea.de/10.1594/PANGAEA.973666

'''c) Laboratory experiments''' are (comparative) studies on organisms/samples under controlled conditions set up in a land-based or mobile (e.g. ship-based) laboratory, e.g. behaviour of fish larvae in response to different treatments of carbon dioxide (CO2) partial pressure.

Example datasets:

* Culture experiments with phytoplankton: https://doi.org/10.1594/PANGAEA.964086
* Incubation experiments with sediments: https://doi.org/10.1594/PANGAEA.977247
* Laboratory experiments with artificial kelp/simulated water flow: https://doi.pangaea.de/10.1594/PANGAEA.971269

The following data '''are not considered''' experimental data in PANGAEA:
* '''Field observations''': Data are either directly collected in the field, or organisms/samples are collected and preserved (e.g. frozen) for later analysis in the laboratory, e.g. to determine the abundance of species in space and time. For the submission of field observation data, have a look at our general and domain-specific templates: [[Best practice manuals and templates]].
* '''Computational experiments''' (e.g. modelling data) are only archived at PANGAEA, if a direct relation to a corresponding environmental study exists. For further details, see our article [[Model data and PANGAEA]].

== Template for experimental data ==

[[Media:Exp data template.xlsx|'''Generic spreadsheet template''' for experimental data]]

== Specific requirements for metadata and data ==

=== Metadata - Abstract ===

* For general guidelines, please read: [[Abstract]].
* Describe '''how the experiment was carried out''', and include the '''conditions/treatments before and during''' the experiment.
* Specify the '''type of experiment''' and the '''location''' where the experimental data were collected, e.g. "field experiment in the Wadden Sea at Spiekeroog", or "laboratory experiment at the Marine Biology laboratory at Kiel University".

=== Metadata - Keywords ===
It is '''mandatory to include ONE of the following keywords''' for experimental data to distinguish them from other datasets with field observations in PANGAEA:

* Field experiment
* Laboratory experiment
* Mesocosm experiment
* Greenhouse experiment
* Experiment
Further keywords, such as “ship-based”, “land-based”, the name of the experimental site or the analysed sample/species may be included in addition.

=== Metadata - Event table ===
The Event table (see template, coming soon) gives an overview when, where and how the experimental sample, organism or data was collected. Please provide the following event information:

* '''Event(s) for the actual experiments''' including the location and the start and end date/time of the experiments
* If available, additionally provide the '''original sampling event''' of the studied sample/organism in the field prior to the experiments
For general information regarding the event information, please read: [[Event]]. Please use one of the following methods for the events of the actual experiments: “Field experiment”, “Laboratory experiment”, “Mesocosm experiment”, “Greenhouse experiment”, “Experiment”.

=== Metadata - Parameter table ===
This table summarizes all variables (PANGAEA "[[Parameter|parameters]]") that are included in the data table, specifies units, principal investigator(s) and the methods used to generate the data. Please read our [[Authors Guides#Requirements for the data files and their metadata|general requirements for parameter information]] and see our respective template (coming soon). Specific requirements for experimental data include:

* The parameter name should specify whether the values in a column reflect an '''experimental condition/treatment''' '''or a measured variable'''. For treatment parameters, use the syntax '''Treatment: XY''', e.g., "Treatment: temperature", “Treatment: light intensity”, or “Treatment: carbon dioxide”.
* The parameter name may include the type of sample or species name, e.g. “Mytilus edulis, wet mass“.

=== Data table/files ===
Prepare your data according to our general requirements for [[Authors Guides#How to prepare tabular Data:|tabular data]] and [[Authors Guides#How to prepare binary files:|binary files]]. Specific requirements for tabular experimental data include:

* The '''first column''' must be the '''Event label'''. The Event label must correspond to the event information of the actual experiments included in the Event table.
* The '''second column''' must be '''"Type of study'''" to separate experimental datasets from field observations. Use e.g. "Laboratory experiment" or "Field experiment" as values, even if all data are from the same type of study.
* If an organism (e.g. Mytilus edulis) was investigated in the experiment, the species should be indicated in the parameter names. Alternatively, if multiple species were studied, include e.g. the '''column "Species, unique identification"''' for the scientific name of the species even if only one species was studied. Please provide a [https://en.wikipedia.org/wiki/LSID Life Science Identifier] (LSID e.g. <nowiki>urn:lsid:marinespecies.org:taxname:140656</nowiki>) in a '''separate column''', e.g. “'''Species, unique identification (Semantic URI)'''”. We recommend to use [https://www.marinespecies.org/index.php WoRMS] LSIDs for marine organisms or [https://www.itis.gov/ Integrated Taxonomic Information System] (ITIS) LSIDs for terrestrial and limnic organisms.
* Any other type of studied samples (e.g. sediment) can either be indicated in the parameter names or alternatively specified in the '''column "Sample type"'''.
* Include the '''date/time of experiment''' in '''ISO-format''' and as '''UTC''' (use e.g. parameter "Sampling date/time, experiment" or "Date/time start, experiment", "Date/time end, experiment"). Start and end date/time must be provided in separate columns.
* '''For field experiments, include the parameters Latitude and Longitude''' in decimal degrees, and the third dimension '''depth''' (e.g. parameters “Depth, sediment, experiment [m]”, "Depth, water, experiment [m]"), even if all observations are from the surface (value = 0). When data are from a depth range, minimum and maximum depths must be provided in separate columns.
* Use "'''Treatment: XY" parameters''', e.g., "Treatment: Temperature, water" to indicate the experimental conditions/treatments for the data.

File:Exp data template.xlsx

2026-04-27T12:28:06Z

Fhoering: Excel template file for experimental data

== Summary ==
Excel template file for experimental data

Experimental data

2026-03-13T10:17:43Z

Fhoering: minor formatting

This wiki article describes guidelines on how to prepare experimental data for submission to PANGAEA. Please read our [[Authors Guides]] first which provide general guidelines on how to prepare your metadata and data for publication in PANGAEA. Check if your experimental data file types and format are accepted by PANGAEA (see [[Authors Guides#Data types and file formats accepted by PANGAEA|respective section in our Authors Guides]]). In addition, you can find the template for experimental data (see section 2) and the specific requirements for experimental (meta-)data (see section 3) below.

== 1) Types of experimental data at PANGAEA ==
Experimental data are collected in (semi-)controlled experiments where variables are manipulated (using so-called treatments) to observe their effects e.g. on an organism or environmental sample, in a natural or artificial environment. Experiments are conducted in multiple research domains and diverse experimental set-ups exist. The main types of experiments can be summarized as:

'''a) Field experiments''' are ''in situ'' studies designed to compare the effects of different treatments on organisms or other samples in their natural environment or under conditions that closely resemble it.. Conditions are partially controlled and the treatments are set up by researchers, e.g. to investigate the growth of an organism in different microhabitats. This also includes mesocosm studies with an open experimental set-up that is influenced by several external environmental factors.

Example datasets:

* Biodiversity experiment: https://doi.org/10.1594/PANGAEA.967077
* Benthocosm experiment: https://doi.org/10.1594/PANGAEA.974781

'''b) Enclosed outdoor experiments''' are set up outside in a closed experimental system, e.g. greenhouse studies or bottle experiments. External factors are better controlled in these systems and therefore the studied sample or organism is less influenced by external environmental factors than in field studies. Relevant environmental factors for these outdoor experiments may e.g. include the natural daily cycle of light or air temperature.

Example datasets:

* Greenhouse experiment: https://doi.org/10.1594/PANGAEA.973270
* Ex-situ cultivation system & subsequent outdoor bottle incubation: https://doi.pangaea.de/10.1594/PANGAEA.973666

'''c) Laboratory experiments''' are (comparative) studies on organisms/samples under controlled conditions set up in a land-based or mobile (e.g. ship-based) laboratory, e.g. behaviour of fish larvae in response to different treatments of carbon dioxide (CO2) partial pressure.

Example datasets:

* Culture experiments with phytoplankton: https://doi.org/10.1594/PANGAEA.964086
* Incubation experiments with sediments: https://doi.org/10.1594/PANGAEA.977247
* Laboratory experiments with artificial kelp/simulated water flow: https://doi.pangaea.de/10.1594/PANGAEA.971269

The following data '''are not considered''' experimental data in PANGAEA:
* '''Field observations''': Data are either directly collected in the field, or organisms/samples are collected and preserved (e.g. frozen) for later analysis in the laboratory, e.g. to determine the abundance of species in space and time. For the submission of field observation data, have a look at our general and domain-specific templates: [[Best practice manuals and templates]].
* Computational experiments (e.g. modelling data) are only archived at PANGAEA, if a direct relation to a corresponding environmental study exists. For further details, see our article [[Model data and PANGAEA]].

== 2) General template for experimental data ==
coming soon

== 3) Specific requirements concerning metadata and data ==

=== Metadata - Abstract ===

* For general guidelines, please read: [[Abstract]].
* Specify the location and the type of experiment where the experimental data were collected, e.g. field experiment in the Wadden Sea at Spiekeroog, or laboratory experiment at the Marine Biology lab at Kiel University, and describe the conditions before and during the experiment.
* If you are dealing with biological experimental data, please also have a look at our specific guidelines for [[Biology]].

=== Metadata - Keywords ===
It is '''mandatory to include ONE of the following keywords''' for experimental data to distinguish them from other datasets with field observations in PANGAEA:

* Field experiment
* Laboratory experiment
* Mesocosm experiment
* Greenhouse experiment
* Experiment
Further keywords, such as “ship-based”, “land-based”, the name of the experimental site or the analysed sample/species may be included in addition.

=== Metadata - Event table ===
The Event table (see template, coming soon) gives an overview when, where and how the experimental sample, organism or data was collected. Please provide the following event information:

* '''Event(s) for the actual experiments''' including the location and the start and end date/time of the experiments
* If available, additionally provide the original sampling event of the studied sample/organism in the field prior to the experiments
For general information regarding the event information, please read: [[Event]]. Please use one of the following methods for the events of the actual experiments: “Field experiment”, “Laboratory experiment”, “Mesocosm experiment”, “Greenhouse experiment”, “Experiment”.

=== Metadata - Parameter table ===
This table summarizes all variables (PANGAEA "[[Parameter|parameters]]") that are included in the data table, specifies units, principal investigator(s) and the methods used to generate the data. Please read our [[Authors Guides#Requirements for the data files and their metadata|general requirements for parameter information]] and see our respective template (coming soon). Specific requirements for experimental data include:

* The parameter name may include the type of sample or species name, e.g. “Mytilus edulis, wet mass“.
* The parameter name should specify whether a parameter reflects the experimental conditions/treatment or the measured variable. For treatment parameters, use the syntax '''Treatment: XY''', e.g., "Treatment: temperature", “Treatment: light intensity”, or “Treatment: carbon dioxide”.

=== Data table/files ===
Prepare your data according to our general requirements for [[Authors Guides#How to prepare tabular Data:|tabular data]] and [[Authors Guides#How to prepare binary files:|binary files]]. Specific requirements for tabular experimental data include:

* The '''first column''' must be the '''Event label'''. The Event label must correspond to the event information of the actual experiments included in the Event table.
* The '''second column''' must be '''Type of study''' to separate experimental datasets from field observations. Use e.g. "Laboratory experiment" or "Field experiment" as values, even if all data are from the same type of study.
* If an organism (e.g. Mytilus edulis) was investigated in the experiment, the species should be either indicated in the parameter names or alternatively, if multiple species were studied, the '''column Species''' must be included in the data table.
* Any other type of studied samples (e.g. sediment) can either be indicated in the parameter names or alternatively specified in the '''column Sample type'''.
* Include the '''date/time of experiment''' in '''ISO-format''' and as '''UTC''' (use e.g. parameter "Sampling date/time, experiment" or "Date/time start, experiment", "Date/time end, experiment"). Start and end date/time must be provided in separate columns.
* '''For field experiments, include the parameters Latitude and Longitude''' in decimal degrees, and the third dimension '''depth''' (e.g. parameters “Depth, sediment, experiment [m]”, "Depth, water, experiment [m]"), even if all observations are from the surface (value = 0). When data are from a depth range, minimum and maximum depths must be provided in separate columns.
* Use "'''Treatment: XY" parameters''', e.g., "Treatment: Temperature, water" to indicate the experimental conditions/treatments for the data.

Experimental data

2026-03-13T10:16:46Z

Fhoering: added links to example datasets

Experimental data

2026-03-13T10:12:14Z

Fhoering: some formatting

This wiki article describes guidelines on how to prepare experimental data for submission to PANGAEA. Please read our [[Authors Guides]] first which provide general guidelines on how to prepare your metadata and data for publication in PANGAEA. Check if your experimental data file types and format are accepted by PANGAEA (see [[Authors Guides#Data types and file formats accepted by PANGAEA|respective section in our Authors Guides]]). In addition, you can find the template for experimental data (see section 2) and the specific requirements for experimental (meta-)data (see section 3) below.

== 1) Types of experimental data at PANGAEA ==
Experimental data are collected in (semi-)controlled experiments where variables are manipulated (using so-called treatments) to observe their effects e.g. on an organism or environmental sample, in a natural or artificial environment. Experiments are conducted in multiple research domains and diverse experimental set-ups exist. The main types of experiments can be summarized as:

'''a) Field experiments''' are ''in situ'' studies designed to compare the effects of different treatments on organisms or other samples in their natural environment or under conditions that closely resemble it.. Conditions are partially controlled and the treatments are set up by researchers, e.g. to investigate the growth of an organism in different microhabitats. This also includes mesocosm studies with an open experimental set-up that is influenced by several external environmental factors.

Example datasets:

* Biodiversity experiment: <nowiki>https://doi.org/10.1594/PANGAEA.967077</nowiki>
* Benthocosm experiment: <nowiki>https://doi.org/10.1594/PANGAEA.974781</nowiki>

'''b) Enclosed outdoor experiments''' are set up outside in a closed experimental system, e.g. greenhouse studies or bottle experiments. External factors are better controlled in these systems and therefore the studied sample or organism is less influenced by external environmental factors than in field studies. Relevant environmental factors for these outdoor experiments may e.g. include the natural daily cycle of light or air temperature.

Example datasets:

* Greenhouse experiment: <nowiki>https://doi.org/10.1594/PANGAEA.973270</nowiki>
* Ex-situ cultivation system & subsequent outdoor bottle incubation: <nowiki>https://doi.pangaea.de/10.1594/PANGAEA.973666</nowiki>

'''c) Laboratory experiments''' are (comparative) studies on organisms/samples under controlled conditions set up in a land-based or mobile (e.g. ship-based) laboratory, e.g. behaviour of fish larvae in response to different treatments of carbon dioxide (CO2) partial pressure.

Example datasets:

* Culture experiments with phytoplankton: <nowiki>https://doi.org/10.1594/PANGAEA.964086</nowiki>
* Incubation experiments with sediments: <nowiki>https://doi.org/10.1594/PANGAEA.977247</nowiki>
* Laboratory experiments with artificial kelp/simulated water flow: <nowiki>https://doi.pangaea.de/10.1594/PANGAEA.971269</nowiki>

The following data '''are not considered''' experimental data in PANGAEA:
* '''Field observations''': Data are either directly collected in the field, or organisms/samples are collected and preserved (e.g. frozen) for later analysis in the laboratory, e.g. to determine the abundance of species in space and time. For the submission of field observation data, have a look at our general and domain-specific templates: [[Best practice manuals and templates]].
* Computational experiments (e.g. modelling data) are only archived at PANGAEA, if a direct relation to a corresponding environmental study exists. For further details, see our article [[Model data and PANGAEA]].

== 2) General template for experimental data ==
coming soon

== 3) Specific requirements concerning metadata and data ==

=== Metadata - Abstract ===

* For general guidelines, please read: [[Abstract]].
* Specify the location and the type of experiment where the experimental data were collected, e.g. field experiment in the Wadden Sea at Spiekeroog, or laboratory experiment at the Marine Biology lab at Kiel University, and describe the conditions before and during the experiment.
* If you are dealing with biological experimental data, please also have a look at our specific guidelines for [[Biology]].

=== Metadata - Keywords ===
It is '''mandatory to include ONE of the following keywords''' for experimental data to distinguish them from other datasets with field observations in PANGAEA:

* Field experiment
* Laboratory experiment
* Mesocosm experiment
* Greenhouse experiment
* Experiment
Further keywords, such as “ship-based”, “land-based”, the name of the experimental site or the analysed sample/species may be included in addition.

=== Metadata - Event table ===
The Event table (see template, coming soon) gives an overview when, where and how the experimental sample, organism or data was collected. Please provide the following event information:

* '''Event(s) for the actual experiments''' including the location and the start and end date/time of the experiments
* If available, additionally provide the original sampling event of the studied sample/organism in the field prior to the experiments
For general information regarding the event information, please read: [[Event]]. Please use one of the following methods for the events of the actual experiments: “Field experiment”, “Laboratory experiment”, “Mesocosm experiment”, “Greenhouse experiment”, “Experiment”.

=== Metadata - Parameter table ===
This table summarizes all variables (PANGAEA "[[Parameter|parameters]]") that are included in the data table, specifies units, principal investigator(s) and the methods used to generate the data. Please read our [[Authors Guides#Requirements for the data files and their metadata|general requirements for parameter information]] and see our respective template (coming soon). Specific requirements for experimental data include:

* The parameter name may include the type of sample or species name, e.g. “Mytilus edulis, wet mass“.
* The parameter name should specify whether a parameter reflects the experimental conditions/treatment or the measured variable. For treatment parameters, use the syntax '''Treatment: XY''', e.g., "Treatment: temperature", “Treatment: light intensity”, or “Treatment: carbon dioxide”.

=== Data table/files ===
Prepare your data according to our general requirements for [[Authors Guides#How to prepare tabular Data:|tabular data]] and [[Authors Guides#How to prepare binary files:|binary files]]. Specific requirements for tabular experimental data include:

* The '''first column''' must be the '''Event label'''. The Event label must correspond to the event information of the actual experiments included in the Event table.
* The '''second column''' must be '''Type of study''' to separate experimental datasets from field observations. Use e.g. "Laboratory experiment" or "Field experiment" as values, even if all data are from the same type of study.
* If an organism (e.g. Mytilus edulis) was investigated in the experiment, the species should be either indicated in the parameter names or alternatively, if multiple species were studied, the '''column Species''' must be included in the data table.
* Any other type of studied samples (e.g. sediment) can either be indicated in the parameter names or alternatively specified in the '''column Sample type'''.
* Include the '''date/time of experiment''' in '''ISO-format''' and as '''UTC''' (use e.g. parameter "Sampling date/time, experiment" or "Date/time start, experiment", "Date/time end, experiment"). Start and end date/time must be provided in separate columns.
* '''For field experiments, include the parameters Latitude and Longitude''' in decimal degrees, and the third dimension '''depth''' (e.g. parameters “Depth, sediment, experiment [m]”, "Depth, water, experiment [m]"), even if all observations are from the surface (value = 0). When data are from a depth range, minimum and maximum depths must be provided in separate columns.
* Use "'''Treatment: XY" parameters''', e.g., "Treatment: Temperature, water" to indicate the experimental conditions/treatments for the data.

Experimental data

2026-03-13T10:07:18Z

Fhoering: Inserted content from PEB-289

This wiki article describes guidelines on how to prepare experimental data for submission to PANGAEA. Please read our [[Authors Guides]] first which provide general guidelines on how to prepare your metadata and data for publication in PANGAEA. Check if your experimental data file types and format are accepted by PANGAEA (see [[Authors Guides#Data types and file formats accepted by PANGAEA|respective section in our Authors Guides]]). In addition, you can find the template for experimental data (see section 2) and the specific requirements for experimental (meta-)data (see section 3) below.

== 1) Types of experimental data at PANGAEA ==
Experimental data are collected in (semi-)controlled experiments where variables are manipulated (using so-called treatments) to observe their effects e.g. on an organism or environmental sample, in a natural or artificial environment. Experiments are conducted in multiple research domains and diverse experimental set-ups exist. The main types of experiments can be summarized as:

* '''Field experiments''' are ''in situ'' studies designed to compare the effects of different treatments on organisms or other samples in their natural environment or under conditions that closely resemble it.. Conditions are partially controlled and the treatments are set up by researchers, e.g. to investigate the growth of an organism in different microhabitats. This also includes mesocosm studies with an open experimental set-up that is influenced by several external environmental factors.

Example datasets:

Biodiversity experiment: <nowiki>https://doi.org/10.1594/PANGAEA.967077</nowiki>
Benthocosm experiment: <nowiki>https://doi.org/10.1594/PANGAEA.974781</nowiki>

* '''Enclosed outdoor experiments''' are set up outside in a closed experimental system, e.g. greenhouse studies or bottle experiments. External factors are better controlled in these systems and therefore the studied sample or organism is less influenced by external environmental factors than in field studies. Relevant environmental factors for these outdoor experiments may e.g. include the natural daily cycle of light or air temperature.

Example datasets:

Greenhouse experiment: <nowiki>https://doi.org/10.1594/PANGAEA.973270</nowiki>
Ex-situ cultivation system & subsequent outdoor bottle incubation: <nowiki>https://doi.pangaea.de/10.1594/PANGAEA.973666</nowiki>

* '''Laboratory experiments''' are (comparative) studies on organisms/samples under controlled conditions set up in a land-based or mobile (e.g. ship-based) laboratory, e.g. behaviour of fish larvae in response to different treatments of carbon dioxide (CO2) partial pressure.

Example datasets:

Culture experiments with phytoplankton: <nowiki>https://doi.org/10.1594/PANGAEA.964086</nowiki>

Incubation experiments with sediments: <nowiki>https://doi.org/10.1594/PANGAEA.977247</nowiki>
Laboratory experiments with artificial kelp/simulated water flow: <nowiki>https://doi.pangaea.de/10.1594/PANGAEA.971269</nowiki>
The following data '''are not considered''' experimental data in PANGAEA:
* '''Field observations''': Data are either directly collected in the field, or organisms/samples are collected and preserved (e.g. frozen) for later analysis in the laboratory, e.g. to determine the abundance of species in space and time. For the submission of field observation data, have a look at our general and domain-specific templates: [[Best practice manuals and templates]].
* Computational experiments (e.g. modelling data) are only archived at PANGAEA, if a direct relation to a corresponding environmental study exists. For further details, see our article [[Model data and PANGAEA]].

== 2) General template for experimental data ==
coming soon

== 3) Specific requirements concerning metadata and data ==

=== Metadata - Abstract ===

* For general guidelines, please read: [[Abstract]].
* Specify the location and the type of experiment where the experimental data were collected, e.g. field experiment in the Wadden Sea at Spiekeroog, or laboratory experiment at the Marine Biology lab at Kiel University, and describe the conditions before and during the experiment.
* If you are dealing with biological experimental data, please also have a look at our specific guidelines for [[Biology]].

=== Metadata - Keywords ===
It is '''mandatory to include ONE of the following keywords''' for experimental data to distinguish them from other datasets with field observations in PANGAEA:

* Field experiment
* Laboratory experiment
* Mesocosm experiment
* Greenhouse experiment
* Experiment
Further keywords, such as “ship-based”, “land-based”, the name of the experimental site or the analysed sample/species may be included in addition.

=== Metadata - Event table ===
The Event table (see template, coming soon) gives an overview when, where and how the experimental sample, organism or data was collected. Please provide the following event information:

* '''Event(s) for the actual experiments''' including the location and the start and end date/time of the experiments
* If available, additionally provide the original sampling event of the studied sample/organism in the field prior to the experiments
For general information regarding the event information, please read: [[Event]]. Please use one of the following methods for the events of the actual experiments: “Field experiment”, “Laboratory experiment”, “Mesocosm experiment”, “Greenhouse experiment”, “Experiment”.

=== Metadata - Parameter table ===
This table summarizes all variables (PANGAEA "[[Parameter|parameters]]") that are included in the data table, specifies units, principal investigator(s) and the methods used to generate the data. Please read our [[Authors Guides#Requirements for the data files and their metadata|general requirements for parameter information]] and see our respective template (coming soon). Specific requirements for experimental data include:

* The parameter name may include the type of sample or species name, e.g. “Mytilus edulis, wet mass“.
* The parameter name should specify whether a parameter reflects the experimental conditions/treatment or the measured variable. For treatment parameters, use the syntax '''Treatment: XY''', e.g., "Treatment: temperature", “Treatment: light intensity”, or “Treatment: carbon dioxide”.

=== Data table/files ===
Prepare your data according to our general requirements for [[Authors Guides#How to prepare tabular Data:|tabular data]] and [[Authors Guides#How to prepare binary files:|binary files]]. Specific requirements for tabular experimental data include:

* The '''first column''' must be the '''Event label'''. The Event label must correspond to the event information of the actual experiments included in the Event table.
* The '''second column''' must be '''Type of study''' to separate experimental datasets from field observations. Use e.g. "Laboratory experiment" or "Field experiment" as values, even if all data are from the same type of study.
* If an organism (e.g. Mytilus edulis) was investigated in the experiment, the species should be either indicated in the parameter names or alternatively, if multiple species were studied, the '''column Species''' must be included in the data table.
* Any other type of studied samples (e.g. sediment) can either be indicated in the parameter names or alternatively specified in the '''column Sample type'''.
* Include the '''date/time of experiment''' in '''ISO-format''' and as '''UTC''' (use e.g. parameter "Sampling date/time, experiment" or "Date/time start, experiment", "Date/time end, experiment"). Start and end date/time must be provided in separate columns.
* '''For field experiments, include the parameters Latitude and Longitude''' in decimal degrees, and the third dimension '''depth''' (e.g. parameters “Depth, sediment, experiment [m]”, "Depth, water, experiment [m]"), even if all observations are from the surface (value = 0). When data are from a depth range, minimum and maximum depths must be provided in separate columns.
* Use "'''Treatment: XY" parameters''', e.g., "Treatment: Temperature, water" to indicate the experimental conditions/treatments for the data.

Experimental data

2026-03-13T09:37:33Z

Fhoering: Redirect to internal experimental data page was removed

Event lists

2026-03-12T09:34:23Z

Fhoering: small edits in the last paragraph for links to O2A Registry and the German Marine Data Portal

THIS PAGE IS UNDER CONSTRUCTION !

== Event lists in PANGAEA ==
[[File:PS138 event-list.png|thumb|Figure 1: Part of the station list of POLARSTERN cruise PS138 as it appears on https://www.pangaea.de/expeditions/events/PS138]]
Event lists (sometimes called station lists) depict all device operations (=[[event]]<nowiki/>s) of a given research [[campaign]]. These lists can be accessed and downloaded using the generic link “<nowiki>https://www.pangaea.de/expeditions/events/”</nowiki> and adding the name of a campaign, as it is stored in PANGAEA. I.e. for campaign “PS138” the link would be: https://www.pangaea.de/expeditions/events/PS138. Default format is HTML, a tab file of a list can be downloaded by including “?format=textfile” in the URL: https://www.pangaea.de/expeditions/events/PS138?format=textfile.
There are two cases how these event lists are generated, depending on their origin:
# Events are provided during the [https://www.pangaea.de/submit/ submission] process of a [[Data set|dataset]] and added to the [https://www.pangaea.de/ PANGAEA] database.
# Events are systematically archived in PANGAEA for large and medium-sized German research vessels and aircrafts (see https://pangaea.de/expeditions/). For further information on how these event lists are generated, please read the next paragraphs.

== Event lists for German research vessels ==

Event lists are systematically archived in PANGAEA for expeditions of the German research vessels POLARSTERN, SONNE, MARIA S. MERIAN, METEOR, HEINCKE, ELISABETH MANN BORGESE and ALKOR. They can be accessed via https://www.pangaea.de/expeditions, where [[campaign]] lists for certain ships are linked.
=== Generation of Event lists ===
[[File:PS138 AL.jpg|thumb|Figure 2: Part of the ActionLog of POLARSTEN cruise PS138]]
Event lists for the German research vessel are generated from [https://dship.awi.de/ DSHIP Action Logs]. The DSHIP is the system that German Research vessels use to document stations and device usage. Sampling actions are logged manually, including date/time, lat/long, information about the device and several actions are used, i.e. “in the water” or “max depth/on ground”. The resulting log file is an “Action Log”. Action Logs may vary among the different ships they come from, regarding column names, comments, best practices, etc.

In PANGAEA, for each device operation one event is generated depending on the provided actions. For devices that are towed behind the ship or permanently installed, a start and end action is used and the respective times and coordinates of the device operation is used. For point instruments, i.e. MultiCorer or Grab, the action of the actual sampling is used (“max depth/on ground”). For instruments that are deployed or recovered, i.e. moorings, the action of the deployment or recovery is used. All coordinates provided in the ActionLogs refer to the ship position and were not quality controlled before generating the event lists. Quality controlled ship positions for the German research vessels are archived as master tracks in PANGAEA (i.e. Boetius, Antje (2023): Master tracks in different resolutions of POLARSTERN cruise PS138, Tromsø - Bremerhaven, 2023-08-02 - 2023-10-01 [dataset]. Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven, PANGAEA, https://doi.org/10.1594/PANGAEA.963843).

Additional events, that were not logged in DSHIP, can be added to these lists on demand.

=== POLARSTERN event list process ===
For POLARSTERN, the creation of the event list in PANGAEA is closely connected to the generation of the Station list in the cruise report. Most stations are logged in DShip, but those that aren't need to be logged in the [https://registry.o2a-data.de/ O2A Registry]. Both sources are used to create the official station list in PANGAEA. After that, a script is used on the PANGAEA list to create the list used for the cruise report. Moreover, the PANGAEA events (stations) will be harvested by the [https://marine-data.de/ German Marine Data Portal]. In addtion, the BSH also saves station lists from DShip in its original form.

[[File:Event list process for POLARSTERN.png|thumb|Figure 3: Event list generation and usage for POLARSTERN.|center|717x717px]]

__FORCETOC__

Event lists

2026-03-12T09:26:58Z

Fhoering: Small edits for better readability. Link to Marine Data Portal corrected.

THIS PAGE IS UNDER CONSTRUCTION !

== Event lists in PANGAEA ==
[[File:PS138 event-list.png|thumb|Figure 1: Part of the station list of POLARSTERN cruise PS138 as it appears on https://www.pangaea.de/expeditions/events/PS138]]
Event lists (sometimes called station lists) depict all device operations (=[[event]]<nowiki/>s) of a given research [[campaign]]. These lists can be accessed and downloaded using the generic link “<nowiki>https://www.pangaea.de/expeditions/events/”</nowiki> and adding the name of a campaign, as it is stored in PANGAEA. I.e. for campaign “PS138” the link would be: https://www.pangaea.de/expeditions/events/PS138. Default format is HTML, a tab file of a list can be downloaded by including “?format=textfile” in the URL: https://www.pangaea.de/expeditions/events/PS138?format=textfile.
There are two cases how these event lists are generated, depending on their origin:
# Events are provided during the [https://www.pangaea.de/submit/ submission] process of a [[Data set|dataset]] and added to the [https://www.pangaea.de/ PANGAEA] database.
# Events are systematically archived in PANGAEA for large and medium-sized German research vessels and aircrafts (see https://pangaea.de/expeditions/). For further information on how these event lists are generated, please read the next paragraphs.

== Event lists for German research vessels ==

Event lists are systematically archived in PANGAEA for expeditions of the German research vessels POLARSTERN, SONNE, MARIA S. MERIAN, METEOR, HEINCKE, ELISABETH MANN BORGESE and ALKOR. They can be accessed via https://www.pangaea.de/expeditions, where [[campaign]] lists for certain ships are linked.
=== Generation of Event lists ===
[[File:PS138 AL.jpg|thumb|Figure 2: Part of the ActionLog of POLARSTEN cruise PS138]]
Event lists for the German research vessel are generated from [https://dship.awi.de/ DSHIP Action Logs]. The DSHIP is the system that German Research vessels use to document stations and device usage. Sampling actions are logged manually, including date/time, lat/long, information about the device and several actions are used, i.e. “in the water” or “max depth/on ground”. The resulting log file is an “Action Log”. Action Logs may vary among the different ships they come from, regarding column names, comments, best practices, etc.

In PANGAEA, for each device operation one event is generated depending on the provided actions. For devices that are towed behind the ship or permanently installed, a start and end action is used and the respective times and coordinates of the device operation is used. For point instruments, i.e. MultiCorer or Grab, the action of the actual sampling is used (“max depth/on ground”). For instruments that are deployed or recovered, i.e. moorings, the action of the deployment or recovery is used. All coordinates provided in the ActionLogs refer to the ship position and were not quality controlled before generating the event lists. Quality controlled ship positions for the German research vessels are archived as master tracks in PANGAEA (i.e. Boetius, Antje (2023): Master tracks in different resolutions of POLARSTERN cruise PS138, Tromsø - Bremerhaven, 2023-08-02 - 2023-10-01 [dataset]. Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven, PANGAEA, https://doi.org/10.1594/PANGAEA.963843).

Additional events, that were not logged in DSHIP, can be added to these lists on demand.

=== POLARSTERN event list process ===
For POLARSTERN, the creation of the event list in PANGAEA is closely connected to the generation of the Station list in the cruise report. Most stations are logged in DShip, but those that aren't need to be logged in registry.awi.de. Both sources are used to create the official station list in PANGAEA. After that, a script is used on the PANGAEA list to create the list used for the cruise report. Moreover, the PANGAEA events (stations) will be harvested for https://marine-data.de/. In addtion, the BSH also saves station lists from DShip in its original form.

[[File:Event list process for POLARSTERN.png|thumb|Figure 3: Event list generation and usage for POLARSTERN.|center|717x717px]]

__FORCETOC__

Event lists

2026-03-12T08:57:12Z

Fhoering: Punkt 2 im ersten Abschnitt angepasst, sodass die Formulierung mit der Expedition Webseite zusammenpasst und auf diese verwiesen

THIS PAGE IS UNDER CONSTRUCTION !

== Event lists in PANGAEA ==
[[File:PS138 event-list.png|thumb|Figure 1: Part of the station list of POLARSTERN cruise PS138 as it appears on https://www.pangaea.de/expeditions/events/PS138]]
Event lists (sometimes called station lists) depict all device operations (=[[event]]<nowiki/>s) of a given research [[campaign]]. These lists can be accessed and downloaded using the generic link “<nowiki>https://www.pangaea.de/expeditions/events/”</nowiki> and adding the name of a campaign, as it is stored in PANGAEA. I.e. for campaign “PS138” the link would be: https://www.pangaea.de/expeditions/events/PS138. Default format is HTML, a tab file of a list can be downloaded by including “?format=textfile” in the URL: https://www.pangaea.de/expeditions/events/PS138?format=textfile.
There are two cases how these event lists are generated, depending on their origin:
# Events are provided during the [https://www.pangaea.de/submit/ submission] process of a [[Data set|dataset]] and added to the [https://www.pangaea.de/ PANGAEA] database.
# Events are systematically archived in PANGAEA for large and medium-sized German research vessels and aircrafts (see https://pangaea.de/expeditions/). For further information on how these event lists are generated, please read the next paragraphs.

== Event lists for German research vessels ==

Event lists are systematically archived in PANGAEA for expeditions of the German research vessels POLARSTERN, SONNE, MARIA S. MERIAN, METEOR, HEINCKE, ELISABETH MANN BORGESE and ALKOR. They can be accessed via https://www.pangaea.de/expeditions, where [[campaign]] lists for certain ships are linked.
=== Generation of Event lists ===
[[File:PS138 AL.jpg|thumb|Figure 2: Part of the ActionLog of POLARSTEN cruise PS138]]
Event lists for the German research vessel are generated from [https://dship.awi.de/ DSHIP Action Logs]. The DSHIP is the system that German Research vessels use to document stations and device usage. Sampling actions are logged manually, including date/time, lat/long, information about the device and several actions are used, i.e. “in the water” or “max depth/on ground”. The resulting log file is an “Action Log”. Action Logs may vary among the different ships they come from, regarding column names, comments, best practices, etc.

In PANGAEA, for each device operation one event is generated depending on the provided actions. For devices that are towed behind the ship or permanently installed, a start and end action is used and the respective times and coordinates of the device operation is used. For point instruments, i.e. MultiCorer or Grab, the action of the actual sampling is used (“max depth/on ground”). For instruments that are deployed or recovered, i.e. moorings, the action of the deployment or recovery is used. All coordinates provided in the ActionLogs are the ships position and were not quality controlled before generating the event lists. Quality controlled ship positions for the German research vessels are archived as master tracks in PANGAEA (i.e. Boetius, Antje (2023): Master tracks in different resolutions of POLARSTERN cruise PS138, Tromsø - Bremerhaven, 2023-08-02 - 2023-10-01 [dataset]. Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven, PANGAEA, https://doi.org/10.1594/PANGAEA.963843).

Additional events, that were not logged in DSHIP, can be added to these lists on demand.

=== POLARSTERN event list process ===
For POLARSTERN, the creation of the event list in PANGAEA is closely connected to the generation of the Station list in the cruise report. Most stations are logged in DShip, but those that aren't need to be logged in registry.awi.de. Both sources are used to create the official station list in PANGAEA. After that a script is used on the PANGAEA list to create the list used for the cruise report. Also the PANGAEA events (stations) will be harvested for www.marine-data.org. Apart from that the BSH also saves station lists from DShip in its original form.

[[File:Event list process for POLARSTERN.png|thumb|Figure 3: Event list generation and usage for POLARSTERN.|center|717x717px]]

__FORCETOC__

Coverage

2024-12-04T12:13:26Z

Fhoering: Small change of second sentence to align it to the content below

The coverage describes the spatial and/or temporal distribution of the data set. It is calculated automatically using the [[geocode|geocodes]] from the data matrix or the [[event]] information.

The purpose of this document is to describe the details of the coverage calculation depending on the use case, especially when relevant information is provided with the data matrix and [[event]].

=== Calculation of the spatial coverage or geolocation ===

The algorithm will only '''calculate the geolocation from either the coordinates provided in the data matrix or the [[event]], never from (a mixture of) both'''. The reason for this is that there is no clear and universal way to map multiple instances of coordinates to the required [[geocode|GEOCODES]] latitude and longitude. '''The same is true for the 3rd [[geocode|GEOCODE]], elevation. Multiple columns reflecting height or depth information''', e.g. “depth, sediment” & “depth, mbsf.” or elevation information in the [[event]] and data matrix '''cannot be mapped to a single vertical [[geocode|GEOCODE]]'''.

However, the geolocation information is often more accurate in data matrices. Therefore, it is used with priority during calculation. Accordingly, '''the geolocation will be calculated from the coordinates provided in the data matrix if both are present'''.

However, it’s possible that the geolocation in data matrices sometimes has gaps because, for example, a certain method was not applied at a certain position. If these gaps were on the “boundary” of the area of interest, the resulting [[PANGAEA publication types|collection]] of positions wouldn’t correctly reflect the sampled area that may (or may not) be specified in the [[event]] information.

For the bounding box given in the web interface, we only provide the minimum/maximum of the latitude and longitude values. Internally, however, we store the exact locations of each of the four bounding box corners.

=== The calculation of mean (or median) geolocation values ===

'''The center of the sample area is determined by calculating the average of all individual sample coordinate pairs. Thus, the mean or median is not the arithmetic mean (or centroid)''' of the area covered by the constituents, but the arithmetic mean calculated from the entirety of the individual coordinate pairs provided. This is because the mean was introduced at that time to place the map bounding box where most of the data points were located.
However, unlike the calculations for geolocation, there is '''no priority given to information from data matrices and [[Event|events]]'''. As a result, if they are provided in both, this could lead to incorrect values being provided for the mean geolocation.

The value for median found on dataset landing pages does not refer to the strict mathematical term, but seemed to be the more appropriate term to describe the mean in the context of geo-referenced data. [community consensus or rather arbitrary?]

=== Temporal coverage - Date/Time values ===

Similar to the spatial coverage calculation, '''the algorithm will only use either the information provided in the data matrices or the [[event]], never both'''. Using information from both is therefore impossible. '''If no temporal reference is provided with the matrices, the information from the [[event]] will be used and displayed instead'''. Temporal coverage provided in data matrices thus takes precedence over [[Event|events]].
In cases where date lines are passed, a special calculation routine ensures that the correct temporal coverage is displayed.

=== Modifications to calculated values ===

PANGAEA editors cannot change the information displayed in the coverage, as those values are automatically calculated. There is no way to modify the values, unless the coordinates given for associated [[Event|events]] and/or [[geocode|geocodes]] in the data matrix are modified, which is not recommended as this may change the interpretation of data in the matrix.

The coverage values are not part of the curated metadata and may also change over the time, e.g., when PANGAEA's algorithms change or are optimized to improve discoverability of datasets (e.g., the way how dataset [[PANGAEA publication types|collections]] are handled by the system). The coverage is shown on the dataset landing pages to allow users to get a quick overview of the geolocation in addition to the displayed map, especially when they did a geospatial search.

Because coverage is a mandatory discovery property of metadata standards like ISO 19115/19139, Schema.org for Datasets, or DataCite, PANGAEA displays the calculated coverage on the landing page of datasets to make it clear that this information is part of the distributed metadata. 3rd party systems harvesting PANGAEA metadata may use this metadata for discovery and may display the coverage information on their own landing pages.

=== Visualization in the overview map ===
The Google map in the Dataset landing pages is a by-product of the coverage calculation, provided for a fast and convenient preview of the geographical coverage.
==== What is shown in the map? ====
* Markers (red): these represent individual [[Event|Events]]. When an event has start and end (not just a single position), a pair of markers per event is shown. They are numbered 1 and 2 for start and end. Limitation: the markers are not shown when the number of events exceeds XXX.
* Lines (yellow): these can provide tracks for datasets where all 3 [[Geocode|geocodes]] data series (Latitude, Longitude and Date/time) are present in the data table. Limitation: tracks are only shown for datasets under open access license. The lines are also not shown when the number of Lat/Lon/Date/time entries exceeds XXX. If a dataset contains 3 geocodes, but the track visualisation does not make sense in the context of the data, it can be configured out by the editor.
* Group markers (grey): these can be shown in the maps of [[PANGAEA publication types|data collections]] (e.g., publication series or bundled publications). A group marker is shown for each dataset in the collection, either at the position of the Event in case the dataset has a single Event, or at the median position in case the dataset has multiple events.

==== What is not shown in the map? ====
* If no event is present in the dataset, no map is shown.
* A map doesn't show the position of each individual sample or measurement unless these represent individual events. For example, if samples were taken at different locations within a single event, only the position of the event is shown, even though the location changes. An exception to this is the visualization of the "tracks" as yellow line (see above).
* If events are located in polar areas, they might not be shown in the map. The preview map doesn't allow for changing projections.

Coverage

2024-12-04T12:08:04Z

Fhoering: Small corrections of typos in the chapter Visualisation in the overview map.

The coverage describes the spatial and/or temporal distribution of the data set. It is calculated automatically using the [[geocode|geocodes]] from the data matrix and the [[event]] information.

The purpose of this document is to describe the details of the coverage calculation depending on the use case, especially when relevant information is provided with the data matrix and [[event]].

=== Calculation of the spatial coverage or geolocation ===

The algorithm will only '''calculate the geolocation from either the coordinates provided in the data matrix or the [[event]], never from (a mixture of) both'''. The reason for this is that there is no clear and universal way to map multiple instances of coordinates to the required [[geocode|GEOCODES]] latitude and longitude. '''The same is true for the 3rd [[geocode|GEOCODE]], elevation. Multiple columns reflecting height or depth information''', e.g. “depth, sediment” & “depth, mbsf.” or elevation information in the [[event]] and data matrix '''cannot be mapped to a single vertical [[geocode|GEOCODE]]'''.

However, the geolocation information is often more accurate in data matrices. Therefore, it is used with priority during calculation. Accordingly, '''the geolocation will be calculated from the coordinates provided in the data matrix if both are present'''.

However, it’s possible that the geolocation in data matrices sometimes has gaps because, for example, a certain method was not applied at a certain position. If these gaps were on the “boundary” of the area of interest, the resulting [[PANGAEA publication types|collection]] of positions wouldn’t correctly reflect the sampled area that may (or may not) be specified in the [[event]] information.

For the bounding box given in the web interface, we only provide the minimum/maximum of the latitude and longitude values. Internally, however, we store the exact locations of each of the four bounding box corners.

=== The calculation of mean (or median) geolocation values ===

'''The center of the sample area is determined by calculating the average of all individual sample coordinate pairs. Thus, the mean or median is not the arithmetic mean (or centroid)''' of the area covered by the constituents, but the arithmetic mean calculated from the entirety of the individual coordinate pairs provided. This is because the mean was introduced at that time to place the map bounding box where most of the data points were located.
However, unlike the calculations for geolocation, there is '''no priority given to information from data matrices and [[Event|events]]'''. As a result, if they are provided in both, this could lead to incorrect values being provided for the mean geolocation.

The value for median found on dataset landing pages does not refer to the strict mathematical term, but seemed to be the more appropriate term to describe the mean in the context of geo-referenced data. [community consensus or rather arbitrary?]

=== Temporal coverage - Date/Time values ===

Similar to the spatial coverage calculation, '''the algorithm will only use either the information provided in the data matrices or the [[event]], never both'''. Using information from both is therefore impossible. '''If no temporal reference is provided with the matrices, the information from the [[event]] will be used and displayed instead'''. Temporal coverage provided in data matrices thus takes precedence over [[Event|events]].
In cases where date lines are passed, a special calculation routine ensures that the correct temporal coverage is displayed.

=== Modifications to calculated values ===

PANGAEA editors cannot change the information displayed in the coverage, as those values are automatically calculated. There is no way to modify the values, unless the coordinates given for associated [[Event|events]] and/or [[geocode|geocodes]] in the data matrix are modified, which is not recommended as this may change the interpretation of data in the matrix.

The coverage values are not part of the curated metadata and may also change over the time, e.g., when PANGAEA's algorithms change or are optimized to improve discoverability of datasets (e.g., the way how dataset [[PANGAEA publication types|collections]] are handled by the system). The coverage is shown on the dataset landing pages to allow users to get a quick overview of the geolocation in addition to the displayed map, especially when they did a geospatial search.

Because coverage is a mandatory discovery property of metadata standards like ISO 19115/19139, Schema.org for Datasets, or DataCite, PANGAEA displays the calculated coverage on the landing page of datasets to make it clear that this information is part of the distributed metadata. 3rd party systems harvesting PANGAEA metadata may use this metadata for discovery and may display the coverage information on their own landing pages.

=== Visualization in the overview map ===
The Google map in the Dataset landing pages is a by-product of the coverage calculation, provided for a fast and convenient preview of the geographical coverage.
==== What is shown in the map? ====
* Markers (red): these represent individual [[Event|Events]]. When an event has start and end (not just a single position), a pair of markers per event is shown. They are numbered 1 and 2 for start and end. Limitation: the markers are not shown when the number of events exceeds XXX.
* Lines (yellow): these can provide tracks for datasets where all 3 [[Geocode|geocodes]] data series (Latitude, Longitude and Date/time) are present in the data table. Limitation: tracks are only shown for datasets under open access license. The lines are also not shown when the number of Lat/Lon/Date/time entries exceeds XXX. If a dataset contains 3 geocodes, but the track visualisation does not make sense in the context of the data, it can be configured out by the editor.
* Group markers (grey): these can be shown in the maps of [[PANGAEA publication types|data collections]] (e.g., publication series or bundled publications). A group marker is shown for each dataset in the collection, either at the position of the Event in case the dataset has a single Event, or at the median position in case the dataset has multiple events.

==== What is not shown in the map? ====
* If no event is present in the dataset, no map is shown.
* A map doesn't show the position of each individual sample or measurement unless these represent individual events. For example, if samples were taken at different locations within a single event, only the position of the event is shown, even though the location changes. An exception to this is the visualization of the "tracks" as yellow line (see above).
* If events are located in polar areas, they might not be shown in the map. The preview map doesn't allow for changing projections.

Best practice manuals and templates

2024-12-04T10:48:03Z

Fhoering: Typo corrected and section header updated

<h1 style="background-color:#3ba39b; font-size: 30px; font-weight:bold; color:white; padding:0.3em 1em; margin:1em 0; text-align:center"> Best practice manuals and templates </h1>
__TOC__
==About this page==
On this page we present a collection of best practice manuals & submission templates for data submissions to PANGAEA. We provide a general field observation template and a series of guides for specific research areas in order to best capture and preserve the particular contextual information of these research areas for reuse, and to best assist our authors in compiling this helpful and necessary information. The guides also include the corresponding adapted templates to help our authors submit their data.

The templates support the comprehensive compilation of required meta-information related to sampling, methodology, and measured parameters/variables in a well-defined, structured manner. They help to be compliant with our guidelines and requirements, standardize metadata and data in submissions and thus also assist PANGAEA in the process of reviewing and ingesting data submissions, which in turn considerably contributes to a reduction in overall submission processing time.

== General field observation studies from earth and environmental sciences ==
We recommend the following template for authors wishing to submit data for studies that do not fall within the more specific research areas listed below.
[[Media:Envir sample template.xlsx|'''Generic spreadsheet template''' for field observation data]] ('''xlsx-file''' including detailed instructions)

[[Media:Envir sample template tsv.zip|'''Generic text-file template''' for field observation data]] ('''zipped tab separated text files'''. Please see instruction file 0_README.md first!)

==Guidelines and templates for specific research domains==

[[Biology|'''Biological data''']] [[Chemical data|'''Chemical data''']] [[Vertical sediment profile|'''Geological data''']]

'''Geophysical data'''

* Multibeam echosounder data (incl. SVP, MBES water column data) & Side-scan sonar data & bathymetry model data ([[Bathymetry]])

* Sediment echosounder data (e.g. Atlas Parasound P70 echosounder data) ([[Sediment_echosounder]])

[[Meteorological data|'''Meteorological data''']]

[[Eddy-Covariance-Measurement Systems|'''Eddy-Covariance-Measurement Systems''']]

'''Oceanography data'''

* [[ADCP Underway Data]]
* [[Bio-optical Sensors Underway Data]]
* [[CTD|CTD Data]]
* [[CTD Underway Data]]
* [[Ferrybox Underway Data]]
* [[TSG Underway Data]]

== Binary objects ==

This category of data publications includes georeferenced binary object, e.g. NetCDF-files, seismic data files (e.g. segy), photos/images or videos.
* [[Binary_objects|Binary objects]]

Coverage

2024-06-07T09:40:56Z

Fhoering: Created page with "The coverage describes the spatial and/or temporal distribution of the data set. It is calculated automatically using the geocodes from the data matrix and the event information. Notes for editing this page: * More details regarding the calculation will be added by Uwe. * Add examples for different coverage calculations (e.g. event only used, combination of event and data matrix calculation)"

The coverage describes the spatial and/or temporal distribution of the data set. It is calculated automatically using the geocodes from the data matrix and the event information.

Notes for editing this page:
* More details regarding the calculation will be added by Uwe.
* Add examples for different coverage calculations (e.g. event only used, combination of event and data matrix calculation)

PANGAEA Training activities

2024-01-08T12:48:07Z

Fhoering: Added slides for PANGAEA info event

{| class="wikitable"
|+
!Date
!Location
!Who?
!Title/Topic
!Organizer
!# of Participants
!Resources
|-
|2023/11/16 & 17
|Online
|CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA# "FAIR Data Publishing with PANGAEA"]
|PANGAEA
|~40 external
|[https://drive.google.com/drive/folders/1L5vPxxa2Hn9F8Opa5nq9mVZc8dYsXHVD Material GDrive folder (internal)] , [https://nextcloud.awi.de/s/38pqDaF8BePZ76W Slides] (external), [https://pad.gwdg.de/WzeHa1C5T7yPJA61A5pkxA# Orga PAD]
|-
|2023/10/20
|Online
|LM
|Coffee Lecture - "An Introduction to PANGAEA"
|NFDI4Earth Academy
|~30?
|[https://drive.google.com/drive/folders/1oEXJrHrgdhTOmOs_VMeqgIn726t1qwif Material GDrive folder (internal)]
|-
|2023/08/23
|Online
|FH
|PANGAEA info event for DAM research missions
|FH/DAM-UFD2
|20
|[https://docs.google.com/presentation/d/1aGlIntPRkykWI0d1uR_4CY9MWHhR8Gvs/edit?usp=sharing&ouid=113465391393115401654&rtpof=true&sd=true Slides]
|-
|2023/05/11 & 12
|Online
|CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A# "Finding and retrieving data from PANGAEA"]
|PANGAEA
|~25
|[https://drive.google.com/drive/folders/1RLQO3c7QZg1AzUtDakOoMQSXvJLiF6FT?usp=sharing Material GDrive folder (internal)], [https://nextcloud.awi.de/s/w3kycnJpKc4eAJq Slides] (external), [https://pad.gwdg.de/qkyvcnPQRNyuL_NNT6E2CA# Orga PAD]
|-
|2023/05/04
|Online
|FH & GW
|DAM info event for data managers
|FH/DAM-UFD2
|10
|
|-
|2023/03/16
|IPK Gatersleben
|MO & LM
|[https://www.denbi.de/news1/1526-de-nbi-spring-school-program-is-now-available de.NBI Spring School] - "Publishing Research Data with PANGAEA"
|de.NBI
|40?
|[https://ipk-cloud.ipk-gatersleben.de/s/Z4xXzTyGc2jEDPL?dir=undefined&path=%2FPresentations%2FDay4_Thu&openfile=18745297 Slides]
|-
|2023/02/09
|?
|MO
|BASS Workshop - "Publishing Research Data with PANGAEA"
|BASS
|?
|[https://docs.google.com/presentation/d/1rGMGdmo0_jnAiKcJLUBCWjp1qarn2RTQzZDWZhsZeqc/edit# Slides]
|}

PANGAEA Training activities

2024-01-08T11:14:36Z

Fhoering:

{| class="wikitable"
|+
!Date
!Location
!Who?
!Title/Topic
!Organizer
!# of Participants
!Resources
|-
|2023/11/16 & 17
|Online
|CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA# "FAIR Data Publishing with PANGAEA"]
|PANGAEA
|~40 external
|[https://drive.google.com/drive/folders/1L5vPxxa2Hn9F8Opa5nq9mVZc8dYsXHVD Material GDrive folder (internal)] , [https://nextcloud.awi.de/s/38pqDaF8BePZ76W Slides] (external), [https://pad.gwdg.de/WzeHa1C5T7yPJA61A5pkxA# Orga PAD]
|-
|2023/10/20
|Online
|LM
|Coffee Lecture - "An Introduction to PANGAEA"
|NFDI4Earth Academy
|~30?
|[https://drive.google.com/drive/folders/1oEXJrHrgdhTOmOs_VMeqgIn726t1qwif Material GDrive folder (internal)]
|-
|2023/08/23
|Online
|FH
|PANGAEA info event for DAM research missions
|FH/DAM-UFD2
|20
|
|-
|2023/05/11 & 12
|Online
|CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A# "Finding and retrieving data from PANGAEA"]
|PANGAEA
|~25
|[https://drive.google.com/drive/folders/1RLQO3c7QZg1AzUtDakOoMQSXvJLiF6FT?usp=sharing Material GDrive folder (internal)], [https://nextcloud.awi.de/s/w3kycnJpKc4eAJq Slides] (external), [https://pad.gwdg.de/qkyvcnPQRNyuL_NNT6E2CA# Orga PAD]
|-
|2023/05/04
|Online
|FH & GW
|DAM info event for data managers
|FH/DAM-UFD2
|10
|
|-
|2023/03/16
|IPK Gatersleben
|MO & LM
|[https://www.denbi.de/news1/1526-de-nbi-spring-school-program-is-now-available de.NBI Spring School] - "Publishing Research Data with PANGAEA"
|de.NBI
|40?
|[https://ipk-cloud.ipk-gatersleben.de/s/Z4xXzTyGc2jEDPL?dir=undefined&path=%2FPresentations%2FDay4_Thu&openfile=18745297 Slides]
|-
|2023/02/09
|?
|MO
|BASS Workshop - "Publishing Research Data with PANGAEA"
|BASS
|?
|[https://docs.google.com/presentation/d/1rGMGdmo0_jnAiKcJLUBCWjp1qarn2RTQzZDWZhsZeqc/edit# Slides]
|}

PANGAEA Training activities

2024-01-08T11:10:53Z

Fhoering: Added info events for DAM research missions in 2023

{| class="wikitable"
|+
!Date
!Location
!Who?
!Title/Topic
!Organizer
!# of Participants
!Resources
|-
|2023/11/16 & 17
|Online
|CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/jwmLDEgQQGWNIa7ytjMBZA# "FAIR Data Publishing with PANGAEA"]
|PANGAEA
|~40 external
|[https://drive.google.com/drive/folders/1L5vPxxa2Hn9F8Opa5nq9mVZc8dYsXHVD Material GDrive folder (internal)] , [https://nextcloud.awi.de/s/38pqDaF8BePZ76W Slides] (external), [https://pad.gwdg.de/WzeHa1C5T7yPJA61A5pkxA# Orga PAD]
|-
|2023/10/20
|Online
|LM
|Coffee Lecture - "An Introduction to PANGAEA"
|NFDI4Earth Academy
|~30?
|[https://drive.google.com/drive/folders/1oEXJrHrgdhTOmOs_VMeqgIn726t1qwif Material GDrive folder (internal)]
|-
|2023/08/23
|Online
|FH
|PANGAEA info event for DAM research missions
|FH/DAM-UFD2
|20
|
|-
|2023/05/11 & 12
|Online
|CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A#Who Team]
|PANGAEA CWS [https://pad.gwdg.de/KA2JeYAjSPO9vqMTahDH2A# "Finding and retrieving data from PANGAEA"]
|PANGAEA
|~25
|[https://drive.google.com/drive/folders/1RLQO3c7QZg1AzUtDakOoMQSXvJLiF6FT?usp=sharing Material GDrive folder (internal)], [https://nextcloud.awi.de/s/w3kycnJpKc4eAJq Slides] (external), [https://pad.gwdg.de/qkyvcnPQRNyuL_NNT6E2CA# Orga PAD]
|-
|2023/05/04
|Online
|FH/GW
|DAM info event for data managers
|DAM-UFD2
|10
|
|-
|2023/03/16
|IPK Gatersleben
|MO & LM
|[https://www.denbi.de/news1/1526-de-nbi-spring-school-program-is-now-available de.NBI Spring School] - "Publishing Research Data with PANGAEA"
|de.NBI
|40?
|[https://ipk-cloud.ipk-gatersleben.de/s/Z4xXzTyGc2jEDPL?dir=undefined&path=%2FPresentations%2FDay4_Thu&openfile=18745297 Slides]
|-
|2023/02/09
|?
|MO
|BASS Workshop - "Publishing Research Data with PANGAEA"
|BASS
|?
|[https://docs.google.com/presentation/d/1rGMGdmo0_jnAiKcJLUBCWjp1qarn2RTQzZDWZhsZeqc/edit# Slides]
|}

CTD Underway Data

2022-06-14T07:42:51Z

Fhoering: Question mark was removed for 4D parameter "Density, mass density"

On this page you will find information on the requirements for submitting, archiving and publishing '''Conductivity, Temperature, Depth Sonde (CTD) Underway Data''', as well as examples of datasets. Although not "underway" per definition, CTD data taken continuously onboard a research vessel without scientific program will be names "underway" here for the sake of consistency with similar efforts with other devices.

== Please note ==
SOPs for the curation and publication of Underway Data are currently being revised within the [https://www.allianz-meeresforschung.de '''DAM Underway Research Data''' Project] to ensure fulfilling the [https://doi.org/10.1038/sdata.2016.18 '''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 ==
[[File:DAM_Logo_small.png|frame|https://www.allianz-meeresforschung.de/en/]]
=== Underway Data from different devices ===
During DAM pilot phase, workflows for data curation, archiving and publication at PANGAEA are being revised. Besides CTD, other types of processed '''Underway Data from different devices''' are in the scope of the project:
* [https://wiki.pangaea.de/wiki/ADCP_Underway_Data ADCP Underway Data]
* [https://wiki.pangaea.de/wiki/Ferrybox_Underway_Data Ferrybox Underway Data]
* [https://wiki.pangaea.de/wiki/Bio-optical_Sensors_Underway_Data Bio-optical Sensors Underway Data]
* [https://wiki.pangaea.de/wiki/TSG_Underway_Data TSG Underway Data]

Furthermore, historical and recent [https://wiki.pangaea.de/wiki/Bathymetry Bathymetry data and corresponding workflows] are under revision in the framework of DAM.
== Example of a CTD Underway Data Publication ==
CTD HE549: https://doi.pangaea.de/10.1594/PANGAEA.917455
== Standardized Meta-Information of Underway Data ==
The following information needs to be included in any '''Underway Data submission at PANGAEA'''. To start a data submission at PANGAEA go to https://www.pangaea.de/submit/ .
'''Further information''' on the ticket system used for communication and documentation during the processing of the data submission can be found [https://wiki.pangaea.de/wiki/Ticket_System in this wiki].
=== PANGAEA Data Submission Form Example ===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Issue Type
|
|Data Submission ''(default)''
|-
|Summary
|Name of the ticket that will automatically be generated; the institution should be included here
|For example “Data submission 2020-03-24T07:32:46 ([submitter/responsible scientist], Alfred Wegener Institute Helmholtz Centre for Polar and Marine Research, Bremerhaven)
|-
|Author(s)
|[[#List of Authors]]
|[responsible scientist], [chief scientist]
|-
|Title
|Adapted, generalized [[#Dataset Title]]
|Physical oceanography during [ship] cruise [cruise label]
|-
|Description
|[[#Abstract]]; if the [[#Data Processing Report]] or the [[#Raw Data]] are already archived, the links may be placed here
|
|-
|Keywords
|
|''(default)''
|-
|Attachment(s)
|[[#Data Processing Report]]; [[#Data Table]]; [[#Further References]]
|
|-
|License
|The license specifies how the record can be used and modified after publication and how it must be cited by re-users. The use of license CC-BY 4.0 is strongly recommended by PANGAEA and DAM, ensuring for re-usability of the Underway Data and credit for the author(s).
|[https://creativecommons.org/licenses/by/4.0/ CC-BY: Creative Commons Attribution 4.0 International] ''(default)''
|-
|Labels
|The project the data has been obtained in may be named here
|DAM
|-
|Data used/published in the following article/manuscript
|
|''(default)''
|}

=== List of Authors ===
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 [[#PANGAEA Data Submission Form Example]]).
=== 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. For more information on what needs to be included in a PANGAEA data publication abstract see [https://wiki.pangaea.de/wiki/Ticket_System this page].
=== References ===
Several references may be of importance for Underway Data.
==== Cruise Report ====
The '''Cruise Report''' is sometimes already archived at the Technische Informationsbibliothek and will be linked to the dataset by a data editor (see [https://doi.org/10.2312/cr_msm88 this example]).
==== 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 [https://epic.awi.de/id/eprint/50046/ this example]).

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.
==== 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.
=== Further information ===
==== Cruise Label ====
The '''[Cruise] Label''' given should always include [ship]number/leg (e.g.: MSM88/1).
==== 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.: HE549_10-1).
==== Device /Sensor ====
'''Information on the device''' used for measuring should also be provided, so it can be linked to the measured parameters.

==== Keywords/Project ====
Use "DAM:Underway Research Project" as project and technical keyword "DAMUnderwayReserach".

== Data Table ==
=== File name ===
A '''generalized file name''' should be used per device (see [[#PANGAEA Data Submission Form Example]])
=== File Formats ===
Possible file formats include .txt, .tab, .csv, .xlsx . The encoding is preferably UTF-8.
=== Layout ===
Please do 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 ===
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 editor as specified in the submitted meta-information.
{| class="wikitable"
!|Parameter Name
!|Format
!|Unit
!|Example
!|Method
!|Comment
|-
|Event label
|
|
|HE549_10-1
|
|
|-
|DATE/TIME
|Yyy-mm-ddThh:mm:ss
|
|2020-03-19T19:24:11
|
|
|-
|LATITUDE
|decimal
|
|53.840
|
|
|-
|LONGITUDE
|decimal
|
|8.089
|
|
|-
|Depth, water
|
|m
|2.0
|
|
|-
|Pressure, water
|
|dbar
|2.0
|CTD, SEA-BIRD SBE 911plus, SN 1015
|
|-
|Temperature, water
|
|°C
|6.9138
|CTD, SEA-BIRD SBE 911plus, SN 1015
|ITS-90
|-
|Conductivity
|
|mS/cm
|48.471
|CTD, SEA-BIRD SBE 911plus, SN 1015
|
|-
|Salinity
|
|
|35.6154
|CTD, SEA-BIRD SBE 911plus, SN 1015
|PSU, corrected
|-
|Temperature, water, potential
|
|°C
|19.8085
|Calculated
|ITS-90
|-
|Density, sigma-theta (0)
|
|kg/m3
|25.2818
|Calculated
|
|-
|Oxygen
|
|µmol/l
|238.581
|CTD, SEA-BIRD SBE 911plus, SN 1015
|calibrated based on Winkler titration
|-
|Oxygen saturation
|
|%
|103.44
|CTD, SEA-BIRD SBE 911plus, SN 1015
|calibrated based on Winkler titration
|-
|Attenuation, optical beam transmission
|
|arbitrary units
|82.49
|CTD, SEA-BIRD SBE 911plus, SN 101
|
|-
|Fluorometer
|
|arbitrary units
|0.13
|CTD, SEA-BIRD SBE 911plus, SN 101
|
|-
|Number of observations
|
|#
|1
|
|
|-
|}

Note: If Quality Flags are used, the flagging code needs to be explained and will be archived in the parameter comment.

'''This template may help for preparation of your data file''': [https://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/CTD_template.xlsx template]

'''Here a few infos on Density in water:'''

Density = 1027.1234

Sigma = Density - 1000 = 27.1234

Density depends on pressure, temperature and salt content: Density = f(P,T,S)

As a rule, one considers the density (or sigma) and sets P = 0 and denotes this as sigma-theta.

If the potential temperature (theta) is used instead of the in-situ temperature T, then the result is the potential density or sigma-theta.

'''Density in situ''' ('' Note: "Density, mass density" in 4D'') - should always have values around 1000 (e.g. 1027)

'''Density, potential''' should also always have values around 1000 (e.g. 1027)

'''Density sigma-theta''' should always have lower tens values, e.g. around 27

'''Density, sigma, in situ''' should also have lower tens values, e.g. around 27

Event

2022-06-01T11:30:05Z

Fhoering: For ELEVATION, "mean" was added to "sea level"

[[File:Event webpage.PNG|thumb|800 px|Event information in the data set metaheader at PANGAEA website]]
[[#Data set|Data sets]] published in PANGAEA are usually associated with an '''EVENT''' (synonyms ''site, station''). An EVENT refers to the '''sampling event''' at which the data was obtained. Data submitters must provide sufficient information about these events, the EVENT '''label and latitude/longitude being mandatory information''' (for further details, see [[#Basic information that should be provided|Basic information that should be provided]]).

EVENT information can be added as separate metadata files, or can also be part of the data table (especially, if a data table includes several sampling EVENTS). If '''data comes from field campaigns with official sampling events''' (e.g. stations, as defined in the [[station lists]]), the EVENTS presented in PANGAEA '''correspond to the official sampling events''' and have the same name (label). To help accelerating the editorial workflow, it is helpful to provide the station list to the data editor. For a majority of German vessels such lists are curated in PANGAEA. To access them, please check the [https://www.pangaea.de/expeditions/ Expedition site] and select the respective vessel to find the official [[station lists]].
For measurements that are not subject to official sampling events, the data authors can define the name of the EVENT themselves, but must follow nomenclature rules (see [[#EVENT nomenclature|below]]).

Each EVENT is unique and must be clearly identifiable based on its [[metaheader]] (coordinates, times, measurement methods etc., see [[Event#Basic_information_that_should_be_provided|below]]). With an exact description, EVENTS can be recognizable by other data providers or users. EVENT details appears in the [[metaheader]] of the [[data set]].

Providing detailed EVENT information is generally mandatory, but in a few cases, data published in PANGAEA may not be georeferenced (please ask the [[editor]] in charge for further information).

==Examples for EVENTS==
EVENT is a rather generic term, depending on the type of data it can refer to (for example):
* '''Stations''' (during a cruise, expedition, field campaign)
* '''Deployments''' of sampling devices / sensors (device operation ID)
* Sampling events/ measurements along a '''transect / profile'''
* Sampling / observation '''time series'''
* '''Geographical origin''' of organisms (also of culture organisms)
* Time and space limited '''surveys'''
* '''Mappings'''
* '''Moorings'''
* Multiple investigations at a single site
* Field experiments
* Sample labels

==Basic information that should be provided==
[[File:Sensor-URI.png|thumb|800 px|Attribute '''Sensor URI''' gives the link to sensor metadata information stored in Sensor information system https://sensor.awi.de/, see example: {{doi|10.1594/PANGAEA.925325}} ]]
* '''Label''' is the name of a sampling/measuring EVENT (for details on how to label EVENTs, see below).
* '''Optional label''' may be used if the same EVENT has different labels (see below).
* '''[[Method]]''' is a tool, gear or method used to take a sample or to measure something. If several measurements were performed at the same EVENT, the “Multiple investigations” method is selected. In this case, methods must be specified in the dataset/parameter descriptions.
* '''LATITUDE and LONGITUDE''' in decimal degree (positive for North, negative for South, WGS84) are mandatory for georeferenced data.
* '''ELEVATION''' positive above mean sea level, negative below mean sea level - e.g. for specifying a location of a sediment core site at the bottom of the sea
* '''DATE/TIME''' (ISO-format: YYYY-MM-DD'''T'''hh:mm:ss as coordinated universal time, UTC) should be provided if available.
* If an EVENT is a profile with a start and end point, all Latitude, Longitude, Elevation and Date/Time for start and end must be specified separately.
* '''[[Project]]''', '''[[Campaign]]''' associated with the EVENT.
* '''Location''' is the geographical location (e.g., North Sea; Espoo, Finland).
* '''Comment''' may be used to add free text which should be closely event specific (no limit of characters).
* '''Keywords''' can be used to define specific groups of EVENTS.
* '''URI''' links to a more detailed description of an EVENT, e.g. on an external web page or a document.


* '''Additional attributes''' give the possibility to add more sampling information.
** '''Sensor URI''' gives the link to sensor metadata information stored in Sensor information system https://sensor.awi.de/, see example: {{doi|10.1594/PANGAEA.925325}}.
** '''IGSN''' gives the link to [http://www.geosamples.org/aboutigsn International Geo Sample Number].
** '''Penetration''' maximum coring depth (in meter).
** '''Recovery''' gives the length of the core (in meter).
** '''Number of cores''' gives the number of cores sampled during a multicorer deployment.
** '''Deployment''' gives the Event label of a station during which a device (e.g. a mooring) was deployed.
** '''Recovery''' is also used for the Event label of a station during which a device (e.g. a mooring) was recovered.
** '''Lake water depth''' gives the total water depth at sampling position in lakes (in meter).
** '''River water depth''' gives the total water depth at sampling position in rivers (in meter).
** '''Mesh size''' gives the mesh size of net devices.
** '''Pump volume''' gives the volume pumped for obtaining a sample.
** '''Transect length''' gives the length of a sampling / measurement transect.

== How to provide EVENT information during the data submission?==
* Check whether the EVENT already exists in PANGAEA.
**In the PANGAEA search, all data sets related to a specific EVENT can be searched for with the following input: "event:label:''EventLabel''", e.g. [https://www.pangaea.de/?q=event%3Alabel%3AGeoB16224* event:label:GeoB16224*] for all EVENTS with labels starting with "GeoB16224", e.g. "GeoB16224-1" and "GeoB16224-2".
**EVENTS often already exist when they are part of international expeditions (IODP/ ODP) or cruises organized by PANGAEA host institutes (MARUM, AWI). [[Station lists|List of existing EVENTS (station lists)]] as part of Cruise inventory and cruise data for the German research vessels can be found at the [https://www.pangaea.de/expeditions/ PANGAEA Expeditions page]: select vessel and available station lists can be found in the table sorted by expeditions.
* If the EVENT already exists, use the same EVENT label for your data.
* If the EVENT was not found in PANGAEA, please provide as much information as possible, preferable as a supplementary text file/table.

== EVENT nomenclature ==
There is a great risk of confusion with event labels. The event labels in the archived data sets should be '''identical''' to those that appear in a publication, in the expedition report and in the [[station lists]]. In some cases, an additional labeling of events can not be avoided; in this case an ''Optional label'' can be used. In the final data set, it will appear behind the event label in parenthesis (example with 3 labels {{doi|10.1594/PANGAEA.206409}}).

Three different systems exist for labeling events during expeditions:
# Ship related (based on the ship acronym, e.g. Vema, Polarstern)
# Institution related (e.g. GIK..., GeoB...)
# Free format

The label must be unique and does not contain blanks. In the case of stations, this can be ensured by combining the campaign label with the station number, using an underline to join (e.g. Taymyr97_3). Devices or projects should not be replicated in the label to avoid redundancies.

== See also ==
* [[Data model]]

Event

2022-06-01T11:22:50Z

Fhoering: For ELEVATION the abbreviation "NN" was replaced by "sea level"

[[File:Event webpage.PNG|thumb|800 px|Event information in the data set metaheader at PANGAEA website]]
[[#Data set|Data sets]] published in PANGAEA are usually associated with an '''EVENT''' (synonyms ''site, station''). An EVENT refers to the '''sampling event''' at which the data was obtained. Data submitters must provide sufficient information about these events, the EVENT '''label and latitude/longitude being mandatory information''' (for further details, see [[#Basic information that should be provided|Basic information that should be provided]]).

EVENT information can be added as separate metadata files, or can also be part of the data table (especially, if a data table includes several sampling EVENTS). If '''data comes from field campaigns with official sampling events''' (e.g. stations, as defined in the [[station lists]]), the EVENTS presented in PANGAEA '''correspond to the official sampling events''' and have the same name (label). To help accelerating the editorial workflow, it is helpful to provide the station list to the data editor. For a majority of German vessels such lists are curated in PANGAEA. To access them, please check the [https://www.pangaea.de/expeditions/ Expedition site] and select the respective vessel to find the official [[station lists]].
For measurements that are not subject to official sampling events, the data authors can define the name of the EVENT themselves, but must follow nomenclature rules (see [[#EVENT nomenclature|below]]).

Each EVENT is unique and must be clearly identifiable based on its [[metaheader]] (coordinates, times, measurement methods etc., see [[Event#Basic_information_that_should_be_provided|below]]). With an exact description, EVENTS can be recognizable by other data providers or users. EVENT details appears in the [[metaheader]] of the [[data set]].

Providing detailed EVENT information is generally mandatory, but in a few cases, data published in PANGAEA may not be georeferenced (please ask the [[editor]] in charge for further information).

==Examples for EVENTS==
EVENT is a rather generic term, depending on the type of data it can refer to (for example):
* '''Stations''' (during a cruise, expedition, field campaign)
* '''Deployments''' of sampling devices / sensors (device operation ID)
* Sampling events/ measurements along a '''transect / profile'''
* Sampling / observation '''time series'''
* '''Geographical origin''' of organisms (also of culture organisms)
* Time and space limited '''surveys'''
* '''Mappings'''
* '''Moorings'''
* Multiple investigations at a single site
* Field experiments
* Sample labels

==Basic information that should be provided==
[[File:Sensor-URI.png|thumb|800 px|Attribute '''Sensor URI''' gives the link to sensor metadata information stored in Sensor information system https://sensor.awi.de/, see example: {{doi|10.1594/PANGAEA.925325}} ]]
* '''Label''' is the name of a sampling/measuring EVENT (for details on how to label EVENTs, see below).
* '''Optional label''' may be used if the same EVENT has different labels (see below).
* '''[[Method]]''' is a tool, gear or method used to take a sample or to measure something. If several measurements were performed at the same EVENT, the “Multiple investigations” method is selected. In this case, methods must be specified in the dataset/parameter descriptions.
* '''LATITUDE and LONGITUDE''' in decimal degree (positive for North, negative for South, WGS84) are mandatory for georeferenced data.
* '''ELEVATION''' positive above sea level, negative below sea level - e.g. for specifying a location of a sediment core site at the bottom of the sea
* '''DATE/TIME''' (ISO-format: YYYY-MM-DD'''T'''hh:mm:ss as coordinated universal time, UTC) should be provided if available.
* If an EVENT is a profile with a start and end point, all Latitude, Longitude, Elevation and Date/Time for start and end must be specified separately.
* '''[[Project]]''', '''[[Campaign]]''' associated with the EVENT.
* '''Location''' is the geographical location (e.g., North Sea; Espoo, Finland).
* '''Comment''' may be used to add free text which should be closely event specific (no limit of characters).
* '''Keywords''' can be used to define specific groups of EVENTS.
* '''URI''' links to a more detailed description of an EVENT, e.g. on an external web page or a document.


* '''Additional attributes''' give the possibility to add more sampling information.
** '''Sensor URI''' gives the link to sensor metadata information stored in Sensor information system https://sensor.awi.de/, see example: {{doi|10.1594/PANGAEA.925325}}.
** '''IGSN''' gives the link to [http://www.geosamples.org/aboutigsn International Geo Sample Number].
** '''Penetration''' maximum coring depth (in meter).
** '''Recovery''' gives the length of the core (in meter).
** '''Number of cores''' gives the number of cores sampled during a multicorer deployment.
** '''Deployment''' gives the Event label of a station during which a device (e.g. a mooring) was deployed.
** '''Recovery''' is also used for the Event label of a station during which a device (e.g. a mooring) was recovered.
** '''Lake water depth''' gives the total water depth at sampling position in lakes (in meter).
** '''River water depth''' gives the total water depth at sampling position in rivers (in meter).
** '''Mesh size''' gives the mesh size of net devices.
** '''Pump volume''' gives the volume pumped for obtaining a sample.
** '''Transect length''' gives the length of a sampling / measurement transect.

== How to provide EVENT information during the data submission?==
* Check whether the EVENT already exists in PANGAEA.
**In the PANGAEA search, all data sets related to a specific EVENT can be searched for with the following input: "event:label:''EventLabel''", e.g. [https://www.pangaea.de/?q=event%3Alabel%3AGeoB16224* event:label:GeoB16224*] for all EVENTS with labels starting with "GeoB16224", e.g. "GeoB16224-1" and "GeoB16224-2".
**EVENTS often already exist when they are part of international expeditions (IODP/ ODP) or cruises organized by PANGAEA host institutes (MARUM, AWI). [[Station lists|List of existing EVENTS (station lists)]] as part of Cruise inventory and cruise data for the German research vessels can be found at the [https://www.pangaea.de/expeditions/ PANGAEA Expeditions page]: select vessel and available station lists can be found in the table sorted by expeditions.
* If the EVENT already exists, use the same EVENT label for your data.
* If the EVENT was not found in PANGAEA, please provide as much information as possible, preferable as a supplementary text file/table.

== EVENT nomenclature ==
There is a great risk of confusion with event labels. The event labels in the archived data sets should be '''identical''' to those that appear in a publication, in the expedition report and in the [[station lists]]. In some cases, an additional labeling of events can not be avoided; in this case an ''Optional label'' can be used. In the final data set, it will appear behind the event label in parenthesis (example with 3 labels {{doi|10.1594/PANGAEA.206409}}).

Three different systems exist for labeling events during expeditions:
# Ship related (based on the ship acronym, e.g. Vema, Polarstern)
# Institution related (e.g. GIK..., GeoB...)
# Free format

The label must be unique and does not contain blanks. In the case of stations, this can be ensured by combining the campaign label with the station number, using an underline to join (e.g. Taymyr97_3). Devices or projects should not be replicated in the label to avoid redundancies.

== See also ==
* [[Data model]]