wiki:3_implementation:0_pid:orcid
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:3_implementation:0_pid:orcid [2026/04/15 15:32] – [Use Case 1: GEOMAR] esoeding | wiki:3_implementation:0_pid:orcid [2026/04/15 15:53] (current) – [0-ORCiD] esoeding | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ====Use Case 1: GEOMAR ==== | ====Use Case 1: GEOMAR ==== | ||
| - | Sure — here is the same content in clear bullet points: | + | __Status__ |
| + | |||
| + | ORCID identifiers for persons are already captured at GEOMAR, but not yet in a fully systematic way. Capture | ||
| - | * ORCID identifiers for persons are already captured at GEOMAR, but not yet in a fully systematic way | ||
| - | * Capture is currently **manual**, primarily within the publication repository **OceanRep** | ||
| * The system used is **EPrints** (with ORCID support) | * The system used is **EPrints** (with ORCID support) | ||
| * **Responsibility**: | * **Responsibility**: | ||
| - | |||
| * Capturing: Library | * Capturing: Library | ||
| * Maintenance: | * Maintenance: | ||
| Line 21: | Line 20: | ||
| * Improving this integration is an important step toward a more **automated and harmonized ORCID implementation** | * Improving this integration is an important step toward a more **automated and harmonized ORCID implementation** | ||
| + | __Outlook__ | ||
| + | |||
| + | We strive to work with the library, administration IT, software development and personnel department to develop proper workflows to capture and store ORCID within GEOMAR data systems. | ||
| - | Where shall we go? | ||
wiki/3_implementation/0_pid/orcid.1776267167.txt.gz · Last modified: by esoeding