Differences

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

--- wiki:m3.0 [2025/06/17 08:32] – [Recommendation] esoeding
+++ wiki:m3.0 [2025/06/17 14:29] (current) – [Recommendation] apoersch
@@ Line 16: / Line 16: @@
 =====Recommendation ====
-For organizations this means:
+It is recommended that everyone in the Helmholtz Association use PIDInst to identify instruments in data infrastructures wherever and whenever possible.
-   * 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:
-   * 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: =====
@@ Line 55: / Line 41: @@
 ====1. Explanation of the Background and Benefits of the Recommendation ====
-In today's data-driven world, effective data management is crucial for organizational success. One key aspect of this is the deployment of Persistent Identifiers for Instruments (PIDINST), which can significantly enhance data management infrastructures and workflows. Here’s why your organization should support PIDINST deployment:
+In today's data-driven world, effective data management is crucial for organizational success. One key aspect of this is the deployment of Persistent Identifiers for Instruments (PIDINST), which can significantly enhance data management infrastructures and workflows.
 Enhanced Data Traceability and Integrity:
@@ Line 102: / Line 88: @@
 ====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====
@@ Line 138: / Line 139: @@
 ====8. Further Information====
-===References===
+Research Data Alliance (RDA)
+Persistent Identification of Instruments (PIDINST)
+working group output report, Version: 1.0a2, 19 April 2021
+https://docs.pidinst.org/en/1.0a2/white-paper/index.html#white-paper
-===Relevant Community Recommendations===
+RDAs 24th Plenary - Persistent Identification of Instruments WG: Working with PIDs in Tools IG, recording: https://youtu.be/CjgnGKJ_XEc
-https://docs.pidinst.org/en/1.0a2/white-paper/index.html#white-paper
 ====9. History of this document====