This page contains an overview over files that have been provided for import to the EBAS database, either via the submission tool or in some special cases directly through FTP.

The files provided to the data center are stored in an internal file archive.

Within ACTRIS, the data submission & curation process is tracked in an issue tracker to have traceable quality control. The issue status indicates where the submission is located in the process. The issue status also indicates who is responsible for the next step: Station/ National Facility = NF, Topic Centre = TC/Quality Control Centre, EBAS / In-Situ Data Centre:

Please be aware, Mantis has a view of workflows, and each workflow can use different files (in succession, e.g., in case of rejection or re-submissions). This tool looks only at the file archive. It provides only a view on single files within the workflows. Thus, it is not possible to infer the workflow status from the status of a single file. For example, the issue connected to a file located in the rejected file archive may appear as "closed" in Mantis (no re-submission expected), or "called" and onward (re-submission expected). The table below forms a best effort on mapping the status information of the two systems.

Curation step	Status on this page	Responsibility	Task
called		The responsible submitter at the station / NF	A new data submission is expected by the station via the data submission tool, either because a new submission period started and you submitted data for the previous reporting period, or because a previous submission contained errors that require a re-submission. The responsible person at the station / NF needs to act.
curation	curation	Data Centre/EBAS team	The DC is conducting its QC procedures on the submission. The DC needs to act.
feedback	feedback	The responsible submitter at the station / NF	An issue with the submission needs to be resolved with an answer by the NF via the issue tracker. The NF needs to act.
closed - achived	closed - archived	No action required.	The issue is closed because the submission has been accepted and is published in EBAS.
closed - finally rejected			The issue is closed because the it has been finally rejected and no re-submission is expected.
extQC	extQC (not implememted yet)	TC/Quality Control Centre/WCCAP	The submission undergoes QC at the TC (for those variables having QC review by the TC). The TC needs to act.
extQC feedback		The responsible submitter at the station / NF	Under QC review, the TC detected an issue, which needs to be resolved by an answer by the NF via the issue tracker. The NF needs to act.
extQC accepted		Data Centre/EBAS team	Under QC review, the TC has decided to accept the data submission. The submission can be processed further. The DC needs to act.
extQC rejected		Data Centre/EBAS team	Under QC review, the TC has decided to reject the submission. The DC will reject the submission without publishing it and call for a new submission. The DC needs to act.
	rejected		The file has been rejected. The related workflow might be in status 'called' or 'closed - finally rejected', or, after a new submission in any other state.

Note that the “extQC” status categories are meant only for those observations using the QC review by the TC, i.e. currently only trace gases.

If you want to find out where in this process a submission is, you can look up in the issue tracker. There, you can filter issues to search for a station or assigned person.

Comments on issues are welcome, but DON'T update the status of an issue! The DC and the TC will handle status updates for the issues. If you have questions concerning this process, e.g. because you can’t access your account on the issue tracker, please contact ebas@nilu.no.

* The table will only show files from the last 5 years