Parameter

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

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 internal ‚standard‘ units.)
 * 3) Do not define parameters with user specific 'qualifiers' e.g. 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).
 * 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 of the parameter, will be used in the header of data sets.
 * Unit should follow international usage as close as possible. An already existing parameter should only be defined with an other unit if the values can not be converted from one to an other.
 * 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 ParamGroup.
 * 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 set.
 * 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 ###0.00 Some predefined formats are offert by a menue. The format should follow the general precision and will be used by the system as the default. It can be changed during the import of data on the config card.
 * Default data type of a parameter can be numeric or text. If a text parameter is defined, no unit, format and min/max values should be given. Text parameter can store up to 80 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. (Field not included in 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 dynamicaly be produced by a link using the DDI tool on any web page. (Field not included in parameter import form); relational to Keywords.