Editor: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
((via JWB)) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{construction}} | {{construction}} | ||
Data '''editor'''s (also known as data curators) are employed in projects or institutes to archive their data output. There are also general Data editors in PANGAEA working on Data Submissions from external sources. In the [[Data submission]] workflow, the data editor plays the key role in the archiving process. In the beginning, editors are trained in the use of the editorial system, the [[workflow]], regulations and [[data policy|policy]] by the editor in chief. Editors are responsible for data ingest only and are not operators of the PANGAEA system itself. Active editors are listed on the ''[ | Data '''editor'''s (also known as data curators) are employed in projects or institutes to archive their data output. There are also general Data editors in PANGAEA working on Data Submissions from external sources. In the [[Data submission]] workflow, the data editor plays the key role in the archiving process. In the beginning, editors are trained in the use of the editorial system, the [[workflow]], regulations and [[data policy|policy]] by the editor in chief. Editors are responsible for data ingest only and are not operators of the PANGAEA system itself. Active editors are listed on the ''[https://www.pangaea.de/about/team.php personnel]'' page. | ||
Editors | Editors | ||
| Line 8: | Line 8: | ||
* keep the project members informed about data policy and workflow, | * keep the project members informed about data policy and workflow, | ||
* promote a sustainable data flow, | * promote a sustainable data flow, | ||
* publish new data products, compiled from the project deliverables, such as data reports (e.g. [http://www.wdc-mare.org/reports WDC-MARE Reports]) or data publications (e.g. in [[ESSD]]), | * publish new data products, compiled from the project deliverables, such as data reports (e.g. [http://www.wdc-mare.org/reports WDC-MARE Reports]) or data publications (e.g. in [[Intern:ESSD]]), | ||
* assure the documentation of the ''data deliverable'' in the project's final report via a citation list that contains DOIs to the datasets. | * assure the documentation of the ''data deliverable'' in the project's final report via a citation list that contains DOIs to the datasets. | ||
Editors are responsible for: | Editors are responsible for: | ||
* data flow from the project partners | * data flow from the project partners/work packages/authors/investigators, | ||
* completeness of [[metadata]], i.e. the documentation for each dataset, | * completeness of [[metadata]], i.e. the documentation for each dataset, | ||
* assure data consistency, validity, and availability on the Internet, | * assure data consistency, validity, and availability on the Internet, | ||
Latest revision as of 2021-02-26T17:37:56
 This page is under construction.
|
Data editors (also known as data curators) are employed in projects or institutes to archive their data output. There are also general Data editors in PANGAEA working on Data Submissions from external sources. In the Data submission workflow, the data editor plays the key role in the archiving process. In the beginning, editors are trained in the use of the editorial system, the workflow, regulations and policy by the editor in chief. Editors are responsible for data ingest only and are not operators of the PANGAEA system itself. Active editors are listed on the personnel page.
Editors
- should be scientists with an expertise in the scientific field of the data source,
- keep the project members informed about data policy and workflow,
- promote a sustainable data flow,
- publish new data products, compiled from the project deliverables, such as data reports (e.g. WDC-MARE Reports) or data publications (e.g. in Intern:ESSD),
- assure the documentation of the data deliverable in the project's final report via a citation list that contains DOIs to the datasets.
Editors are responsible for:
- data flow from the project partners/work packages/authors/investigators,
- completeness of metadata, i.e. the documentation for each dataset,
- assure data consistency, validity, and availability on the Internet,
- the accuracy of a data set in terms of technical quality (the scientific quality is in the responsibility of the authors).
After import, the editor has to
- inform the Data Submitter about data availability,
- ask for proofread,
- make corrections until the data set is in agreement with the Data Submitter requirements,
- define a password protection on request for a moratorium period.