Data submission

From PangaWiki
(Redirected from Ticket System)
Jump to: navigation, search

Data submissions and technical requests are administered through a Ticket System (JIRA issue and project tracking made by ATLASSIAN). For each request or submission an issue is created which is tracked during the workflow until it is resolved.

NEW to PANGAEA? Learn how to submit data with our videotutorial in just 5 minutes.


PANGAEA is an archive for any kind of data from earth system research and thus has no special format requirements for submissions. Data might be submitted in the authors format and will be converted to the final import and publication format by the PANGAEA editors. The data provider is kindly requested to keep the following points in mind to minimize the preparatory work prior to upload.

  • For samples, observations and measurements made somewhere on earth, the provision of position(s) is mandatory (latitude/longitude in decimal degree).
  • If data are supplementary to a publication, the (preliminary) citation with journal title and abstract (a specific abstract to the dataset) must be added.
  • Submit ONE issue per publication supplement; several files can be attached to one issue (max. size per file = 100 MB)
  • Ideally provide titles for all your submitted datasets. A dataset title should not be the same as the title of the related publication, but should reflect what was measured, where and when
  • If data are related to a project (where PANGAEA is the designated archive) add the project acronym as label.
  • Date/Time must be provided in ISO-format (e.g. 1954-04-07T13:34:11).
  • Parameters are always accompanied by a unit.
  • Abbreviations should be explained.
  • Extended documentations may be added as plain text or pdf-file.
  • Submit data tables as excel or tab-delimited text files; specific formats (e.g. shape, netCDF, segy ...) may be added in zip-archive.
  • ... submit via the PANGAEA ticket system

Additional recommendations

  • Preferred format for data tables is TAB-delimited TEXT-files (ASCII), submitted as ZIP-archive, or excel-format.
  • Several tables with different format should be provided on different sheets.
  • Several tables with identical format may be provided in one file (one data set below the other, event label in the 1. column).
  • Parameter name with unit must appear in the header line (or PANGAEA parameter ID).
  • Use proper event/site/sample labels, e.g. as defined during an expedition (if appropriate).
  • Format for positions (lat/long) should be decimal degree (-65.1234) (S and W are negative).
  • Provide references by its DOI or (even better) as pdf; documentations should also be provided as pdf (documents will be stored in ePIC and linked via a handle).
  • Numeric parameter columns must contain numbers only; exception see quality flags.
  • If the result of a scientific analysis is zero, the corresponding field in the data table must be filled with 0 (and not left empty).
  • Fields without data should be left empty (and NOT filled with '-', 'n/a', 'NaN', -9999 or '*' etc).
  • Multiple values separated by '-', '±', '()' (ranges, values with errors, uncertainties, or alternative values in brackets) withing a single cell should be avoided. Instead, multiple columns need to be used.
  • Remove empty lines and columns; those will not be imported.
  • Avoid abbreviations.
  • Avoid redundant information.
  • Use standards as far as available
  • Care for proper geocodes
  • Use the decimal point.
  • Use the English language.

Data publication workflow - RESPONSIBILITIES

For documentation of the data publishing process, the workflow and related communication should go through the ticket system only.

  1. Submission of data + metadata via the Ticket System - AUTHOR
  2. Assignment to curator (project/institute) or editor (journals) - EDITOR-in-CHIEF
  3. Quality control for consistency, completeness, standards - EDITOR/CURATOR
  4. Parameter definitions (on request of editor/curator; if applicable) - DATA LIBRARIAN
  5. Adjustment of formats, storage of files in related systems (ePIC, hs), import of tables with editorial system (4D) - EDITOR/CURATOR
  6. Password protection on request of the author - EDITOR/CURATOR
  7. Inform author about availability of data by sending the DOI and ask for proofread - EDITOR/CURATOR
  8. Proofread, reply with approval or corrections - AUTHOR
  9. Iteration of format/content of data publication until approval of author - EDITOR/CURATOR
  10. Add dataset DOI to publication - AUTHOR
  11. After final publication inform editor by sending the paper-DOI and ask for removal of protection - AUTHOR

Supervision of workflow - EDITOR-in-CHIEF & DATA LIBRARIAN


In case data are submitted through a project which has publication costs as part of the funding, PANGAEA would appreciate a financial contribution of 500.- € (net) per data supplement of a publication. Other forms/amounts of data contributions can be negotiated (not obligatory at this stage).

Examples of data publications

The following examples may give a first impression about the required information for data from specific scientific fields. The export formats may differ slightly. Please keep in mind, that the export format is dynamicaly produced by the relational database behind PANGAEA and thus it is NOT required to provide data submission in exactly this technical format; the content is the important part of the data submission.