! Keep consistence ! Avoid abbreviations ! Avoid redundancies !
- Keep labels (campaign, event) unique but short. do not use blanks; use underline _ instead.
- One event is related to one to many data set(s). (example for event PS1431-1).
- Two-dimensional, horizontal data distributions may include many events; e.g. doi:10.1594/PANGAEA.52534 .
- If parameters occur more than once in a data set, the difference must be visible through the method, the PI and/or the data series comment (e.g. doi:10.1594/PANGAEA.78746 ).
- An empty cell in a data matrix means not analyzed or not determined. If the result of the analysis is zero, the cell must be filled with a '0' (e.g. doi:10.1594/PANGAEA.78037 ).
- In range charts of microfossils, using text parameters, a dash - may be used instead doi:10.1594/PANGAEA.63404 .
- Columns with numerical parameters must contain numbers only; exception: quality flags.
- Check precision of values (as defined by the method), i.e. number of digits after the decimal point.
- Any type of information must be in its appropriate field. For any other individual information, the comment fields for data series and/or data sets can be used.
- Any available information should be included in the data description to best ensure its understanding and complete documentation.
- When reading a data set, the user should easily understand its content: who? produced what? kind of data when? and where?. The dataset title should reflect the type of data and the geographical area. It should be written similar to the title of a publication. Avoid the word data. Avoid technical expressions like event; use original names instead, e.g. doi:10.1594/PANGAEA.50184 .
- Import observational or analytical data only; in principle PANGAEA does not hold interpolated or gridded data (the exception proves the rule).
- ALWAYS check data sets after import carefully in Internet view.
- ALWAYS send data set DOI to the PI and request for proofread.