wiki:3_implementation:0_pid:igsn
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| wiki:3_implementation:0_pid:igsn [2026/04/15 15:47] – created - external edit 127.0.0.1 | wiki:3_implementation:0_pid:igsn [2026/04/15 16:43] (current) – [Use Case 1: GEOMAR] esoeding | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| __Status__ | __Status__ | ||
| - | ORCID identifiers for persons | + | IGSN identifiers for samples |
| + | * Capture is currently manual | ||
| + | | ||
| - | * The system used is **EPrints** (with ORCID support) | + | __Responsibility__ |
| - | * **Responsibility**: | + | * Geosamples: Core Repositoryx Management |
| - | * Capturing: Library | + | * Biosamples: Bio Sample Management, Data Managemement |
| - | * 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 | + | __Challenges__ |
| - | * Improving | + | |
| + | There are currently no documented workflows or institutional guidelines for IGSN usage. | ||
| + | |||
| + | A key development is the ongoing implementation of API-based registration for IGSNs. | ||
| + | |||
| + | A major challenge is the unclear integration into central systems, particularly: | ||
| + | | ||
| + | * Improving **automation (via API)** | ||
| __Outlook__ | __Outlook__ | ||
| - | We strive to work with the library, administration IT, software development | + | System integration is an important step toward a more scalable and harmonized IGSN implementation. |
wiki/3_implementation/0_pid/igsn.1776268022.txt.gz · Last modified: by 127.0.0.1
