HMC
Earth and Environment
Community Wiki

User Tools

Site Tools

Trace:
wiki:m4.4

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
wiki:m4.4 [2025/05/22 22:19] – [Recommendation to data infrastructures, to allow to assign IGSNs to data records] esoedingwiki:m4.4 [2025/05/28 20:28] (current) – [Contributors] esoeding
Line 5: Line 5:
 =====Description===== =====Description=====
  
-Status: +Status: 23.5.2025
  
 =====Motivation for this Recommendation: ===== =====Motivation for this Recommendation: =====
  
-[shortened from below]+Integrating IGSNs into data infrastructures enhances the quality, consistency, and interoperability of sample metadata. When systems support the capture and exposure of IGSNs—along with parent-child sample relationships—sample-based data becomes more discoverable, reusable, and reliably linked to other research outputs. Making IGSNs part of harvestable metadata allows for better integration across repositories and platforms, while treating them as authoritative identifiers helps maintain accurate and up-to-date records. This contributes to a more robust, transparent, and FAIR-aligned data ecosystem.
  
 =====Recommendation ==== =====Recommendation ====
Line 15: Line 15:
 It is recommended, that data infrastructures: It is recommended, that data infrastructures:
  
-   - allow to record an IGSN to identify samples and parent samples and make this data part of the metadata available for harvesting. +   - allow to record an IGSN to identify samples and parent samples within their data systems, and make this data part of the metadata available for harvesting. 
-   - treat IGSN metadata as the primary source of truth and update the internal metadata accordingly as neccesary.+   - treat IGSN metadata as the primary source of truth within their data systems, and update the internal metadata accordingly as necessary. 
 + 
  
 =====Binding Convention: ===== =====Binding Convention: =====
Line 26: Line 28:
 =====Precondition for Implementation: ===== =====Precondition for Implementation: =====
  
 +IGSNs need to be registered with samples. 
 +Staff needs to be aware of IGSN procedures. 
 =====Related Recommendations ===== =====Related Recommendations =====
  
-Parent:+Parent: [[m4.0|Recommendation to use IGSN as the standard reference in technical infrastructures to samples where appropriate]]
  
-Dependent:+Dependent: none
  
 Other: none Other: none
Line 36: Line 40:
 =====Contributors===== =====Contributors=====
  
-Names of contributors to this recommendation+Emanuel Soeding (lead)
  
 +* Please keep the lead author informed about any possible changes in this wiki. 
 =====Content===== =====Content=====
  
 ====1. Explanation of the Background and Benefits of the Recommendation ==== ====1. Explanation of the Background and Benefits of the Recommendation ====
  
-__About__+Today, IGSNs are supported by a growing international infrastructure, including allocating agents and resolving services, and are already in use by major repositories and infrastructures such as SESAR2, PANGAEA, and GFZ Data Services. Operational procedures and tools now exist to automate IGSN registration and integrate it into data workflows (see [1] Baldewein et al. (2023). FAIR WISH D7 -Standard Operating Procedure for automatic IGSN registration. Zenodo. https://doi.org/10.5281/zenodo.10401380).
  
-__History and structure__ 
  
-__Current Use of ...__+For data infrastructures, enabling the recording and harvesting of IGSNs strengthens metadata quality and ensures the persistent identification of samples and their relationships. Treating IGSN metadata as the authoritative source improves consistency, facilitates interoperability across systems, and enhances discoverability of sample-based data. This contributes to a more connected and sustainable research data ecosystem. 
 +====2. Possible alternative solutions====
  
-__Motivation__ +See [[m4.0#possible_alternative_solutions|a brief discussion of alternative identifiers which could be used instead of IGSNs.]]
- +
-====2. Possible alternative solutions====+
  
 ====3. Consideration of the advantages and disadvantages of implementing the recommendation==== ====3. Consideration of the advantages and disadvantages of implementing the recommendation====
  
-(quality of content, limitations, interoperability, sustainability: +See [[m4.0#consideration_of_the_advantages_and_disadvantages_of_implementing_the_recommendation|the general discussion of advantages and challenges implementing IGSNs in the recommended way.]]
-expected future dissemination / technical availability / funding)+
  
 ====4. The Recommendation==== ====4. The Recommendation====
  
-[Format: Wer! macht was! wo! wann! unter welchen Voraussetzungen!]+It is recommended, that data infrastructures: 
 + 
 +   - allow to record an IGSN to identify samples and parent samples within their data systems, and make this data part of the metadata available for harvesting. 
 +   - treat IGSN metadata as the primary source of truth within their data systems, and update the internal metadata accordingly as necessary. 
 + 
  
 ====5. Naming of communities that have already implemented the recommendation==== ====5. Naming of communities that have already implemented the recommendation====
Line 72: Line 79:
  
 ===References=== ===References===
 +
 +[1] Baldewein et al. (2023). FAIR WISH D7 -Standard Operating Procedure for automatic IGSN registration. Zenodo. https://doi.org/10.5281/zenodo.10401380
 +
  
 ===Relevant Community Recommendations=== ===Relevant Community Recommendations===
wiki/m4.4.1747952392.txt.gz · Last modified: by esoeding