Parameter

The parameter table contains all parameters with unit and ID, grouped by categories (ParamGroup, see also discussion page).

When defining new parameters, the following points should be kept in mind:
 * 1) Check first for existing parameters by using the 4D-client or the parameter dictionary page.
 * 2) Avoid duplication of parameters by defining already existing parameters! If the parameter exists with a unit different from the one needed and the data can easily be converted, a new parameter should NOT be defined and the data must be converted prior to import. (It is one of the major challanges of Pangaea, that it delivers data in a consistent format, which also means it uses standard units as far as defined in science.)
 * 3) Do not define parameters with user specific 'qualifiers', e.g. in species names something like Thalassiosira sp. F. In this case the data should be linked to the parameter Thalassiosira sp. and the data series comment should contain sp. F (see import, for the use of abbreviations in taxonomic names see Taxon).
 * 4) Do not define parameters containing two different individuals, e.g. Convallina logani/dawsoni. Use Convallina logani and add to the data series comment including Convallina dawsoni.
 * 5) Clearly separate parameters and methods. Methods are defined in the method table; the relation between a data series and the method is set during the import.
 * 6) New parameters are defined by the data librarian. Use the import form for new definitions and send it to [mailto:hgrobe@pangaea.de Hannes Grobe]

Description of the fields of the parameter table:
 * Name should contain the full name of the parameter.
 * Abbreviation or short name of the parameter; will be used in the header of data sets.
 * Unit should follow standard use i.a. Already existing parameter should only be defined with an other unit if the values can not be converted from one to an other. Delete Unit-column if text parameter have to be defined or leave empty.
 * Parameter group is used for a better overview and grouping of parameters. Before defining a new parameter, ensure, that the required parameter group already exists; relational to the ParamGroup table, use the ParamGroupID.
 * Data group Primary data are raw data, e.g. counts of microfossils are weight of samples. Secondary data are those calclulated from the raw data and are the most commonly used, e.g. concentrations in % or ppm. Tertiary data are mostly calculated data on a higher level of scientific interpretation, e.g. paleotemperatures. For technical parameters, the group not classified can be used.
 * Lower-/UpperLimit (=Range min/max) can be used to define the numeric range of values in which a certain parameter will occur. An internal routine will check during the import of data for outlayers and will flag them as ‚not valid‘.
 * Default format some predefined formats are offert by a menue but can be eddited by hand. The format should follow the general precision and will be used by the system as the default. Format can be changed during (or after) the import of data on the config card.
 * Default data type of a parameter can be numeric (1) or text (2). If a text parameter is defined, no unit, format and min/max values should be given. Text parameter can store up to 255 characters per value.
 * Default method is a relational field to the method table where a required method has to be defined first. A method in this field is the default, shown during the import of data. The default can be individually changed during the import procedure.
 * Reference If a parameter was defined in a publication, a link to the relational reference field can be given. The reference has to be defined first in the reference table; relational to reference.
 * URL may contain a link to a more detailed explanation/definition of the parameter, e.g. in Wikipedia. This definition should be of general use. (This field is not included in the parameter import form.)
 * Comment may be used for any usefull descriptions, helpfull to other curators to understand its meaning.
 * Keywords may be used to define a certain parameter group for special purpose, projects or users. Keyword-related parameter lists can be produced using the DDI tool to set up a dynamic link; relational to the Thesaurus. (This field is not included in the parameter import form).

Find missing parameter in an import file with PanTool
 * 1) Create ParameterDB.pdb through a download of all parameter from http://www.pangaea.de/parameter/
 * 2) prepare import file with parameter names and unit in header line, format e.g. Olivine [%]
 * 3) open import file with PanTool,
 * 4) choose default location of parameter database (from 1) at File > Options,
 * 5) choose special tools > create parameter import file,
 * 6) find unknown parameter prepared in a preformatted import file at ...
 * 7) parameter import table needs some further editing, see field descriptions above