wiki:3_implementation:0_pid:raid
Differences
This shows you the differences between two versions of the page.
| wiki:3_implementation:0_pid:raid [2026/04/15 15:48] – created - external edit 127.0.0.1 | wiki:3_implementation:0_pid:raid [2026/04/15 16:55] (current) – [Use Case 1: GEOMAR] esoeding | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| __Status__ | __Status__ | ||
| - | 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** | + | Not yet recommended by HMC, but on the wish-list |
| - | + | ||
| - | * 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 | + | |
| - | * 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 | + | |
wiki/3_implementation/0_pid/raid.1776268080.txt.gz · Last modified: by 127.0.0.1
