Differences

This shows you the differences between two versions of the page.

--- wiki:3_implementation:0_pid:pidinst [2026/04/15 15:46] – created - external edit 127.0.0.1
+++ wiki:3_implementation:0_pid:pidinst [2026/04/15 16:37] (current) – [Use Case 1: GEOMAR] esoeding
@@ Line 7: / Line 7: @@
 __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**
+PIDInst identifiers for instruments are currently not captured at GEOMAR
+  * There is no established process or system in place for assigning or managing PIDInst identifiers
+  * Potential responsibility is unclear, but likely involves technical and data management staff (e.g. Claas and others)
+  * There are currently no documented workflows or institutional guidelines for PIDInst usage
+A key challenge is the lack of initial implementation and system integration. This includes missing connections to:
+  * Instrument registries
+  * Internal systems (e.g. OSIS or repositories)
-  * The system used is **EPrints** (with ORCID support)
+__Outlook__
-  * **Responsibility**:
-    * Capturing: Library
-    * Maintenance: Individual researchers
-  * 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**
+Establishing a clear responsibility structure, workflows, and technical integration is a necessary first step toward 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.