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/03/30 13:54] – ↷ Page moved from wiki:2_implementation:0_pid:orcid to wiki:3_implementation:0_pid:orcid jwurz | 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 ==== | ||
| - | What is the current status? | + | __Status__ |
| + | |||
| + | ORCID identifiers for persons are already captured at GEOMAR, but not yet in a fully systematic way. Capture | ||
| + | |||
| + | * The system used is **EPrints** (with ORCID support) | ||
| + | * **Responsibility**: | ||
| + | * Capturing: Library | ||
| + | * Maintenance: | ||
| + | * There are currently **no documented workflows or institutional guidelines** for ORCID usage | ||
| + | * A key challenge is the **lack of system integration** across central infrastructure | ||
| + | * In particular, ORCID information is not yet consistently propagated from: | ||
| + | |||
| + | * **SAP → Active Directory (AD) → OSIS applications → OceanRep** | ||
| + | * 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.1774878877.txt.gz · Last modified: by jwurz
