wiki:m2.0
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:m2.0 [2023/11/06 17:50] – [1. Explanation of the Background and Benefits of the Recommendation] apoersch | wiki:m2.0 [2025/05/26 09:19] (current) – [2. Possible alternative solutions] esoeding | ||
---|---|---|---|
Line 5: | Line 5: | ||
=====Description===== | =====Description===== | ||
- | [Status: Under development, | + | [Status: Under development, |
=====Motivation for this Recommendation: | =====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, | + | 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, |
In order to be able to uniquely and sustainably identify the responsibilities and the context of cooperation within data infrastructures and repositories in the Helmholtz Association, | In order to be able to uniquely and sustainably identify the responsibilities and the context of cooperation within data infrastructures and repositories in the Helmholtz Association, | ||
Line 22: | Line 22: | ||
- | Binding Convention: | + | =====Binding Convention===== |
- | ^ ^ mandatory | + | | ^ mandatory |
^ Helmholtz FAIR Principle| | ^ Helmholtz FAIR Principle| | ||
Line 59: | Line 59: | ||
__Current Use of ...__ | __Current Use of ...__ | ||
+ | |||
+ | Over the recent years numerous repositories and initiatives have recommended the use of ROR. Among them e.g. Arbeitskreis Forschungsdatenmanagement (AK FDM) in Baden-Württemberg [1] | ||
__Motivation__ | __Motivation__ | ||
Line 68: | Line 70: | ||
The database can be accessed via the official website, an open API or as a downloadable database dump. All ROR identifiers and metadata are provided under the CC0 licence. | The database can be accessed via the official website, an open API or as a downloadable database dump. All ROR identifiers and metadata are provided under the CC0 licence. | ||
====2. Possible alternative solutions==== | ====2. Possible alternative solutions==== | ||
+ | |||
+ | Several alternatives exist: | ||
+ | |||
+ | 1. GRID (Global Research Identifier Database) [Deprecated, | ||
+ | |||
+ | Status: No longer maintained, but still used in legacy systems. | ||
+ | |||
+ | Scope: Global research institutions, | ||
+ | |||
+ | Use case: May be used if your system still relies on GRID identifiers, | ||
+ | |||
+ | Note: Since ROR is a community-led continuation of GRID, migrating to ROR is generally encouraged. | ||
+ | |||
+ | |||
+ | 2. ISNI (International Standard Name Identifier) | ||
+ | |||
+ | Scope: Broad—covers not only research institutions but also other organizations and individuals involved in creative or intellectual work. | ||
+ | |||
+ | Managed by: ISNI International Agency. | ||
+ | |||
+ | Use case: Useful for linking to authority records in library or publishing systems (e.g., for institutions in MARC21 authority data). | ||
+ | |||
+ | |||
+ | 3. National or Domain-Specific Authority Files | ||
+ | |||
+ | Examples include: | ||
+ | |||
+ | * GND (Gemeinsame Normdatei) – German National Authority File. | ||
+ | |||
+ | * LCNAF – Library of Congress Name Authority File (U.S.). | ||
+ | |||
+ | * SUDOC – French academic institutions (Abes). | ||
+ | |||
+ | Use case: Often used in library, archival, or bibliometric infrastructures. | ||
+ | |||
+ | Limitation: Coverage and update frequency vary; may not be globally interoperable. | ||
+ | |||
+ | 4. Internal Institutional IDs | ||
+ | |||
+ | Scope: Local or consortium-level identifiers for partner institutions or affiliates. | ||
+ | |||
+ | Use case: When working within a closed or federated system (e.g., within Helmholtz or NFDI), organizations may assign internal codes or URIs. | ||
+ | |||
+ | Caution: Not globally resolvable unless made publicly accessible. | ||
====3. Consideration of the advantages and disadvantages of implementing the recommendation==== | ====3. Consideration of the advantages and disadvantages of implementing the recommendation==== | ||
Line 75: | Line 121: | ||
====4. The Recommendation==== | ====4. The Recommendation==== | ||
+ | It is recommended that all data infrastructures and repositories of the Helmholtz Association use ROR to identify organizations to resources in data infrastructures wherever and whenever possible. | ||
- | [Format: Wer! macht was! wo! wann! unter welchen Voraussetzungen!] | + | ==== 5. Naming of communities that have already implemented the recommendation==== |
- | + | ||
- | ====5. Naming of communities that have already implemented the | + | |
- | recommendation==== | + | |
====6. Documentation of the test to validate correct implementation==== | ====6. Documentation of the test to validate correct implementation==== | ||
Line 90: | Line 134: | ||
===References=== | ===References=== | ||
+ | |||
+ | [1] Entwicklung in Baden-Württemberg: | ||
===Relevant Community Recommendations=== | ===Relevant Community Recommendations=== |
wiki/m2.0.1699293011.txt.gz · Last modified: by apoersch