Campaign

The CAMPAIGN table contains metadata about campaigns (synonyms: cruise, expedition, leg) and are related to a certain project. Campaign as the second level in the data model may be used as an option, but is recommended to more easily list separate sampling locations. If no metainformation is available, a generic campaign label or the label 'not_given' may be used.

Define new campaigns CAMPAIGN IMPORT FORM 
 * by clicking on an empty line in the list of campaigns in the project window and fill out the fields as decribed below. Input to relational fields must be defined in the related tables first.
 * For lists of new campaigns to be imported, please use the
 * Import via 4D-Menue File/Import, choose Campaigns.

Field descriptions for the campaign table; recommendations on how to fill out the columns in the import form are given in cursive.

Basics tab
 * Label of the campaign; must be unique and does not contain blanks (use _ instead); use abbreviations instead of full names. (The campaign label is used in the Event import list InpEvent.xls to set the relation between events and campaign.)
 * Optional label may contain any additional name(s) or labels of a campaign as free text, separated by blank.
 * Basis is the station platform used for the operation of the campaign; > relational to table Basis > contains the name as defined in the Basis table.
 * Begin defines the start date of the campaign, format as set up in the local operation system.
 * End defines the end.
 * Responsible scientist(s) are persons beeing responsible for a campaign; > multiple choice relation to Staff; use names or staff-IDs separated by ; for import. (Sverdrup, Harald Ulrik or Sverdrup, HU or 30411. ID of staff is prefered.)
 * Area > relational to table Area; new names are automaticaly added to the area table; avoid misspelling.
 * Project > is related to table Project and set in the requester when choosing Import/Campaign from the menue.

Details tab
 * Report > may contain the citation of the campaigns report (e.g. cruise report); > related to table Reference; relations to be set by hand; use ReferenceID for import.
 * Comment > free text for any additional information.
 * URI may contain the link to a campaigns web page (be aware of its long-term accessibility).

International convention
In some international projects (e.g. WOCE, CarboOcean), cruises of research vessels are identfied via the NODC Ship code, called EXPOCODE. It consists of
 * 1) the two digit NODC country code; e.g. for Germany = 06 or USA = 32
 * 2) an NODC defined abbreviation of the vessel consisting of letters and/or numbers; e.g. for Meteor (1986) = MT or Nathaniel B. Palmer = 06
 * 3) the date of the first day of the cruise in the format JJJJMMDD
 * Example for a cruise of the US research vessel Nathaniel B. Palmer, starting on 2011-02-19: 320620110219

Attension! There is a slight difference for research vessels from Germany using the ships own cruise label in a modified form instead of the start date - examples: If the cruise is part of an international project and the EXPOCODE is used, it should be added to the Campaign table by using the Optional label field.
 * cruise M15/3 of the Germany research vessel Meteor: 06MT15_3
 * cruise ANT-XV/4 of Polarstern: 06AQANTXV_4

The EU-project Eurofleets also intends to use the EXPOCODE, in addition extended to a convention for event labels.

Links

 * Ship tracker
 * NODC country codes
 * NODC ship codes

In the EU-project Eurofleets a new convention for cruise naming was developed: We have reach some conventions Naming cruises (Survey/Cruise Id): (SDN ship Code)+(yyyyMMdd start survey date). Example: 29HE20101223 is the name of a survey onboard BIO Hesperides research vessel starting 23 of December 2010. Naming CSR: Same as cruise Id with “_csr.xml” extension. Naming CDI: (Cruise Id) _(leg, sample or station name)_(instrument name)+xml Example: 29HE20101223_station1_ctd.xml (CTD of station1 from Hesperides starting 23-12-2010 cruise).