Talk:Event

Data sets published in PANGAEA are usually associated with the sampling event from which the investigated samples originated. Each event is unique in terms of location and time and must be identifiable by its metadata (see Basic information that should be provided). Event information can be added as separate metadata files, or can also be part of the data table. #refer to templates.... Providing detailed EVENT information is generally mandatory, but in a few cases data published in PANGAEA does not have to be georeferenced (e.g., if the origin of samples used for laboratory experiments is unknown).



Event nomenclature

 * Event labels are unique and must not contain blanks. They are identical to those that appear in a journal publication, expedition reports or in station lists. To help accelerating the editorial workflow, please provide the respective station lists to the data editors.


 * For measurements that are not subject to official sampling events, data authors can define event labels themselves, but must be unique and not contain blanks.


 * 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, the optional label will appear behind the event label in parenthesis (example with 3 labels ).

Examples for EVENTS and their nomenclature
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.

UNDER CONSTRUCTION
 * Stations (during a cruise, expedition, field campaign), e.g. station (17-6) on a polarstern cruise (PS133/1) separated by underscore: PS133/1_17-6
 * Sites (deployments of devices/sensors), e.g. device ID as defined by IODP:
 * Deployments of sampling devices / sensors
 * 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

 * 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) are mandatory for georeferenced data.
 * ELEVATION positive above NN, negative below NN - e.g. for specifying a location of a sediment core site at the bottom of the sea
 * DATE/TIME (ISO-formatYYYY-MM-DDThh:mm:ss) 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:.
 * IGSN gives the link to 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 water depth at sampling position in lakes (in meter).
 * River water depth gives the 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. 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). List of existing EVENTS (station lists) as part of Cruise inventory and cruise data for the German research vessels can be found at the 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.