Difference between revisions of "Standards compliance dashboard"
From CETAF Identifiers Wiki
m (+technical notes (added 303 vs. 302 problem)) |
Peter Grobe (Talk | contribs) (Level 3 for ZFMK CETAF IDs) |
||
| Line 54: | Line 54: | ||
! ZOOLOGISCHES FORSCHUNGSMUSEUM ALEXANDER KOENIG (Bonn) | ! ZOOLOGISCHES FORSCHUNGSMUSEUM ALEXANDER KOENIG (Bonn) | ||
! ZFMK | ! ZFMK | ||
| − | ! style="background: yellow;"| | + | ! style="background: yellow;"|L3 |
! | ! | ||
! | ! | ||
Revision as of 09:16, 7 January 2020
Contents
Introduction
The goal of this webpage is to provide an overview of the use of different (biodiversity) standards within the institutes. The dashboard is created in the framework of work package 4 of Synthesys+.
List of standards
- CETAF persistent identifier
- IIIF
- Darwin Core (DwC)
- Access to Biological Collection Data v2.06 (ABCD2)
- Access to Biological Collection Data v3.0 (ABCD3)
- Audubon Core (AC)
- Biological Collections Ontology (BCO)
- DEscription Language for TAxonomy (DELTA)
This list of standards is not exhaustive. A larger overview of the different standards can be found at FAIRsharing.org. In case another standard is supported and missing from the list, don't hesitate to propose an addition.
Dashboard
| Institute | Acronym | CETAF ID | IIIF | DwC | ABCD2 | ABCD3 | AC | BCO | DELTA |
|---|---|---|---|---|---|---|---|---|---|
| NATURAL HISTORY MUSEUM (London) | NHM | L2 | |||||||
| NATURHISTORISCHES MUSEUM WIEN (Vienna) | NHMW | ||||||||
| ZOOLOGISCHES FORSCHUNGSMUSEUM ALEXANDER KOENIG (Bonn) | ZFMK | L3 | |||||||
| HELSINGIN YLIOPISTO (Finland) | LUOMUS | L1 | |||||||
| MUSEUM NATIONAL D'HISTOIRE NATURELLE (Paris) | MNHN | L3 | |||||||
| THE HEBREW UNIVERSITY OF JERUSALEM (Israel) | HUJI | ||||||||
| NATURHISTORISKA RIKSMUSEET (Stockholm) | NRM | L0 | |||||||
| AGENTSCHAP PLANTENTUIN MEISE (Meise) | BGM | L3 | v2.1 | N/A | N/A | ||||
| FREIE UNIVERSITAET BERLIN | BGBM | L3 | v2.1? | ||||||
| AGENCIA ESTATAL CONSEJO SUPERIOR DE INVESTIGACIONES CIENTIFICAS (Madrid) | CSIC | ||||||||
| MUSEUM FUR NATURKUNDE (Berlin) | MfN | L3 | |||||||
| ROYAL BOTANIC GARDEN EDINBURGH | RBGE | L3 | v3.0 | ||||||
| ROYAL BOTANIC GARDENS KEW | RBGK | L3? | |||||||
| INSTITUT ROYAL DES SCIENCES NATURELLES DE BELGIQUE (Brussels) | RBINS | ||||||||
| MUSEE ROYAL DE L'AFRIQUE CENTRALE (Tervuren) | RMCA | L3 | |||||||
| SENCKENBERG GESELLSCHAFT FUR NATURFORSCHUNG (Frankfurt) | SGN | ||||||||
| STAATLICHES MUSEUM FUER NATURKUNDE STUTTGART | SMNS | L1 |
Adoption of the CETAF stable identifier
In the table above, the level of adoption of the CETAF stable identifier is indicated. The levels are defined as follows:
- Level 0: Identifier syntax chosen
- Level 1: Web page for each specimen, identifier redirects to it[1]
- Level 2: Machine readable representation for each specimen, accept-type aware redirection
- Level 3: Machine readable representation is CSPP conform
Extra information
This section will provide the possibility to detail more on the adoption of the different standards.
NHMW
- IIIF: implemented through the JACQ system
BGM
- CETAF-ID: http://www.botanicalcollections.be/specimen/<barcode>
- IIIF: an exemplar implementation is made. An instance of the Mirador viewer can be found here. A RESTful API is developed to generate the IIIF manifests on the fly: http://iiif-manifest.oxalis.br.fgov.be/specimen/<barcode>/manifest. At the moment, manifests are only generated based on the barcode. The IIIF 2.1 APIs (image and presentation) are implemented. The image API is provided by the Loris server and the source images are in JPG format.
- DwC: this standard is used to publish data to e.g. GBIF
BGBM
- CETAF-ID: [herbarium.bgbm.org/object/B200012401 herbarium.bgbm.org/object/<barcode>]
- IIIF: https://herbarium.bgbm.org/data/iiif/<barcode>/manifest.json
RBGE
- IIIF: Specific webpage provides a summary on the IIIF work
Technical Notes
- ↑ If a redirect is implemented it should be the HTTP response status code 303 “See Other” instead of the sometimes used 302 code “Found” or “Moved Temporarily” which is hard to tell how the client would interpret it
