Intern:Basic rules

'''! Keep consistence ! Avoid abbreviations ! Avoid redundancies !'''
 * Keep event labels unique but short.
 * No blanks in campaign and event labels; use underline (_) instead.
 * In principle one event is related to one to many data set(s).
 * Two-dimensional horizontal data distributions include many events; e.g.
 * If a parameter is imported more than once in one data set, the difference must be visible through the method and/or the data series comment (e.g. 78746).
 * An empty cell in a data matrix means not analyzed. If the result of the analysis is zero, the cell must be filled with a '0' (e.g. 78037). In range charts of microfossil assemblages, using text parameters, a dash (-) is used instead.
 * Columns with numerical parameters should contain numbers only; exception: quality flags
 * Check precision of values, i. e. number of digits after the decimal point.
 * Clearly separate method from parameter when defining parameters (send new parameter definitions to mailto:hgrobe@pangaea.de).
 * Any type of information should be in its appropriate field.
 * Include any available comments/information in the data description to ensure its understanding and complete documentation.
 * When using PangaVista a user should easily understand the content of a data set from its citation (who? when? where? what?). The set title should contain a short description of the data and the geographical area - similar to the title of a publication. Avoid technical expressions like e. g. 'event'; use original names instead, e.g.
 * Import data from real events only; PANGAEA does not held model or other spacialy interpolated or gridded data.
 * ALWAYS check data sets after import carefully in PangaVista or by using the  button in 4D.
 * Send data set DOI/link to PI and ask for proof read.

(for background understanding of relational databases see the articles about normalization in englisch and german.