Differences

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

--- wiki:m1.3 [2023/11/15 17:17] – [Recommendation] mabbrent
+++ wiki:m1.3 [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-**Recommendation M1.3**
-======Recommendation to Helmholtz data stewards, repository maintainers and developers to implement personal  ORCID as a reference to people in technical infrastructures======
-=====Description=====
-[Status: Under development, Date: 2023-08-25, Version: 003]
-=====Motivation for this Recommendation:=====
-The Helmholtz Association is determined to make their data available
-according to the FAIR principles, thus making it findable, accessible,
-interoperable and reusable. In order to achieve interoperability of
-datasets among various data infrastructures (DIS) within the Helmholtz
-Association, a common and agreed procedure to **refer to people** within
-and across the DIS is needed.
-In order to be able to uniquely and sustainably identify both
-researchers and employees in data infrastructures and repositories in
-the Helmholtz Association, the respective person should always be
-referenced with a persistent identifier (PID) (see recommendation M0).
-For the Helmholtz Association we recommend to use ORCID to refer to
-people and contributors to resources in data infrastructures and
-repositories of the Helmholtz Association wherever possible (see
-recommendation M1.0).
-To be able to implement this measure, several activities need to be
-conducted by different stakeholder groups. This recommendation M1.3.
-calls for activity of the data stewards, repository maintainers and
-developers.
-=====Recommendation=====
-It is recommended that data infrastructures (data repositories, data
-bases) should:
-  - record an ORCID with any person registered in conjunction with the metadata of datasets, publications, instruments and alike where possible.
-  - treat ORCID metadata as the primary source of truth and update their own metadata accordingly.
-  - Optionally inform persons if they think the metadata registered with the ORCID is not accurate, or request permission to update the ORCID metadata (see also M1-1).
-  - consider ORCID as an attribute in identity and access management systems (IAM), authentication and authorisation infrastructures (AAI) or community attribute services
-=====Binding Convention:=====
-^                         ^ mandatory  ^ conditional	          ^ optional ^
-^ Helmholtz FAIR Principle|if ORCID is available            | |          |
-=====Precondition for Implementation:=====
-[__Precondition 1__]: The ORCID Registry is available for all
-researchers, maintained and further developed.
-=====Related Recommendations=====
-Parent: M1.0
-Dependent: none
-Other: M1.1, M1.2
-=====Contributors=====
-Names of contributors to this recommendation
-=====Content=====
-=====1. Explanation of the Background and Benefits of the Recommendation=====
-=====2. Possible alternative solutions=====
-=====3. Consideration of the advantages and disadvantages of implementing the recommendation=====
-=====4. The Recommendation=====
-=====5. Naming of communities that have already implemented the recommendation=====
-=====6. Documentation of the test to validate correct implementation=====
-=====7. Examples of Instances=====
-=====8. Further Information=====
-====References====
-[12] ORCID Terms of use: https://info.orcid.org/terms-of-use/
-====Relevant Community Recommendations====
-=====9. History of this document=====