Parameter



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

When defining new parameters, please keep in mind:
PARAMETER IMPORT FORM for new definitions and submit as excel or text/zipped format via the ticket system. Also request of changes of a parameter definition must be submitted as ticket.
 * 1) First check for existing parameters by using the 4D-client or the Parameter Dictionary.
 * 2) Avoid duplicate definitions of parameters at any time! If the parameter already 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 or during 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 also 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. Instead use Convallina logani and add to the data series comment including Convallina dawsoni. Do not define any mixed parameters accordingly.
 * 5) Clearly separate parameters from methods or any other specifications. Methods are defined in the method table; the relation between a data series and the method or data specific comments is set during the import.
 * 6) New parameters are defined by the data librarian. Please use the

A nearly unlimited number of parameters can be used in a data set. An example set containing 550 parameter (columns) is

Field description of the parameter table
Hints on how to fill out the columns in the parameter import form are given in italic; mandatory fields are underlined ; unused columns in import files should be deleted. Names in the header line used in the parameter import form are added in (brackets).
 * Name (ParameterName) contains the full name of the parameter. ParameterName in combination with the unit must be unique in Pangaea.
 * Abbreviation (Abbreviation) or short name of the parameter; is used in the header of data sets.
 * Unit (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 column for text-parameters in import form or leave empty.
 * Parameter group (ParameterGroupID) 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 Parameter groups table. For import use the ID of the parameter group.
 * Data group (DataGroup)
 * 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.
 * not classified can be used for technical parameters.
 * Range min/max (LowerLimit/UpperLimit) 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 outliers and will flag them as not valid. Delete columns for text-parameters in import form or leave empty.
 * Default format (DefaultFormat) 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 (DefaultDataType) of a parameter can be numeric (1), text (2) or datetime (3, only used for 1599 DATE/TIME). If a text parameter is defined, no unit, format and min/max values should be given. A field of a text parameter may contain up to 255 characters.
 * Default method (DefaultMethodID) is a relational field to the Method table where a required method has to be defined first. Methods defined in this field are shown during import of data by default. The default can be changed during the import procedure. Use the ID of the method for import.
 * Reference (ReferenceID) can be given in case a parameter was defined through a publication; relational to Reference. Use the ID of the referenceI for import.
 * 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 the parameter import form.
 * Comment (Description) may be used for any descriptions, helpfull to other curators to understand its meaning. This is an internal info field, its content does not appear in datasets!
 * 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. Field not included in the parameter import form. Keywords need to be added by hand for each parameter.

Find missing parameter in an import file with Split2Events

 * 1) Install Split2Events Split2Events
 * 2) Prepare a local list of all parameters called ParameterDB.pdb. For this step use Tools->Refresh parameter database or Tools->Merge new parameters to parameter database. The name of the parameter database can be given first with File->General options....
 * 3) Open your import file.
 * 4) Create a metadata file with the option use metadata file; find parameter by name. Split2Events identifies the ID for each parameter by using the parameter database. If a parameter is unknown, the ID is set to unknown. If write parameter import file on the Options tab was checked, a list of the unknown parameters is written to imp_Parameters.txt. After completing this file create an issue (http://issues.pangaea.de) and upload it to the issue.
 * 5) Continue with step 1.

How is a parameter recognized during import?
In principle, parameter definitions should be unique but the import using parameter (short) names may still produce some ambiguous parameter messages.
 * ID of parameter
 * Parameter name with unit in square bracket, e.g. Equivalent dose [mSv]
 * Parameter abbreviation with unit, e.g. H [mSv]

Check taxonomic parameters in the pangaea parameter table - the script (by Robert Huber) matches the pangaea parameter table with the species catalog of UBIO