wiki:m3.0
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:m3.0 [2025/05/28 16:41] – [5. Naming of communities that have already implemented the recommendation] apoersch | wiki:m3.0 [2025/06/17 14:29] (current) – [Recommendation] apoersch | ||
---|---|---|---|
Line 16: | Line 16: | ||
=====Recommendation ==== | =====Recommendation ==== | ||
- | PIDINST | + | It is recommended that everyone in the Helmholtz Association use PIDInst |
- | + | ||
- | + | ||
- | For organizations this means: | + | |
- | * employ measures | + | |
- | * make a person responsible to maintain the PIDINST for each instrument (e.g. lab technicians). | + | |
- | For technicians: | + | |
- | * register a PIDINST for instruments which weren’t registered yet. | + | |
- | * keep the PIDINST related metadata of your instruments current. | + | |
- | * Keep a written record of the PIDINST on every instrument, where possible | + | |
- | * share the PIDINST with the customer with any measurement data you deliver. | + | |
- | For researchers it means: | + | |
- | * record an PIDINST with any measurement. You should find it on the instrument. | + | |
- | For data infrastructures: | + | |
- | * record a PIDINST with instruments registered in data infrastructures. | + | |
- | * treat PIDINST metadata as the primary source of truth and update your own metadata accordingly. | + | |
- | * inform the responsible person if you think the PIDINST metadata is not accurate. | + | |
=====Binding Convention: ===== | =====Binding Convention: ===== | ||
Line 44: | Line 27: | ||
=====Related Recommendations ===== | =====Related Recommendations ===== | ||
- | Parent: | + | Parent: |
- | Dependent: | + | Dependent: |
- | Other: | + | Other: |
=====Contributors===== | =====Contributors===== | ||
Line 58: | Line 41: | ||
====1. Explanation of the Background and Benefits of the Recommendation ==== | ====1. Explanation of the Background and Benefits of the Recommendation ==== | ||
- | In today' | + | In today' |
Enhanced Data Traceability and Integrity: | Enhanced Data Traceability and Integrity: | ||
Line 80: | Line 63: | ||
====2. Possible alternative solutions==== | ====2. Possible alternative solutions==== | ||
+ | |||
+ | DataCite can also be used to identify instruments by assigning DOIs to them. This allows for the unique identification and citation of instruments in research publications . | ||
+ | |||
+ | electronic Persistent Identifier for eResearch (ePIC) is a PID service that provides persistent identifiers for various types of research objects, including instruments. It is designed to support the unique identification of instruments and other research entities, facilitating better data management and sharing. The ePIC infrastructure has been used for prototypical implementation of PIDINST metadata properties. | ||
+ | |||
+ | International Geo Sample Number (IGSN) is a persistent identifier for physical samples, particularly in the geosciences. While primarily focused on samples, the IGSN framework can be adapted to identify instruments used in geological and environmental research. This helps in tracking the provenance and usage of instruments in field studies. | ||
+ | |||
+ | Open Researcher and Contributor ID (ORCID) is primarily used to uniquely identify researchers and contributors, | ||
+ | |||
+ | The Handle System is a widely used persistent identifier system that provides unique identifiers for digital objects. It can be used to assign persistent identifiers to instruments, | ||
+ | |||
+ | [Andrea: Dieser Inhalt ist Mistral AI erzeugt - zu prüfen und zu kürzen.] | ||
====3. Consideration of the advantages and disadvantages of implementing the recommendation==== | ====3. Consideration of the advantages and disadvantages of implementing the recommendation==== | ||
Line 93: | Line 88: | ||
====4. The Recommendation==== | ====4. The Recommendation==== | ||
- | [Format: Wer! macht was! wo! wann! unter welchen Voraussetzungen!] | + | It is recommended that everyone in the Helmholtz Association use PIDInst to identify instruments in data infrastructures wherever and whenever possible. |
+ | |||
+ | For organizations this means: | ||
+ | * employ measures and incentives to register instruments with PIDINST at acquisition. | ||
+ | * make a person responsible to maintain the PIDINST for each instrument (e.g. lab technicians). | ||
+ | For technicians this means: | ||
+ | * register a PIDINST for instruments which weren’t registered yet. | ||
+ | * keep the PIDINST related metadata of your instruments current. | ||
+ | * Keep a written record of the PIDINST on every instrument, where possible | ||
+ | * share the PIDINST with the customer with any measurement data you deliver. | ||
+ | For researchers it means: | ||
+ | * record an PIDINST with any measurement. You should find it on the instrument. | ||
+ | For data infrastructures: | ||
+ | * record a PIDINST with instruments registered in data infrastructures. | ||
+ | * treat PIDINST metadata as the primary source of truth and update your own metadata accordingly. | ||
+ | * inform the responsible person if you think the PIDINST metadata is not accurate. | ||
====5. Naming of communities that have already implemented the recommendation==== | ====5. Naming of communities that have already implemented the recommendation==== | ||
Line 129: | Line 139: | ||
====8. Further Information==== | ====8. Further Information==== | ||
- | ===References=== | + | Research Data Alliance (RDA) |
+ | Persistent Identification of Instruments (PIDINST) | ||
+ | working group output report, Version: 1.0a2, 19 April 2021 | ||
+ | https:// | ||
- | ===Relevant Community Recommendations=== | + | RDAs 24th Plenary - Persistent Identification of Instruments WG: Working with PIDs in Tools IG, recording: |
- | + | ||
- | https://docs.pidinst.org/en/ | + | |
====9. History of this document==== | ====9. History of this document==== | ||
wiki/m3.0.1748450465.txt.gz · Last modified: by apoersch