Integrating Specify in broader Science infrastructure
Niels Klazenga · Meeting Biodiversity Data Standards Using Specify Software
The short versionSpecify works best at RBG Victoria as one component of a wider hub-based science infrastructure, with custom tools filling its gaps.
What this was about
Niels Klazenga described how RBG Victoria, a Specify user for over 16 years, embeds Specify as a 'collections hub' among other hubs: a Canto digital asset management system, VicFlora, a documentation hub, a traits hub of Lucid keys, KeyBase, and the Australasian Virtual Herbarium within the Atlas of Living Australia, which is its only dissemination channel. A separate 'bystander' application and a GraphQL API provide what Specify lacks or does differently, such as ZPL label printing, duplicate labels, partial loan returns, an event system and taxonomy syncing. He noted that moving from ABCD to Darwin Core felt like a step back and that a more structured model will help. He also called for Specify to support linking identifications to taxon concepts.
Why it matters. Real-world integration patterns, such as a taxon tree as backbone for other systems, a GraphQL API feeding a IIIF image portal, and IPT-to-ALA-to-GBIF delivery, show how a CMS fits into institutional infrastructure and where CMS vendors could improve.
In the room
- RBG Victoria started with Specify 6.0.1 and chose Specify mainly to deliver high-quality data to AVH.
- Hubs: Specify (collections), Canto (media/DAMS), VicFlora (flora of Victoria and horticultural flora of south-eastern Australia), a documentation hub, a traits hub (Lucid keys) and KeyBase (pathway keys).
- Specify is not used for dissemination; all data go through AVH/ALA via the IPT, and ALA passes them on to GBIF as Australia's GBIF node.
- A bystander app handles things Specify cannot, e.g. starting label printing mid-sheet on sheets of 30, ZPL labels for new printers (PDF quality too low), duplicate labels, partial loan returns and an event system.
- The Specify taxon tree is the taxonomic backbone for other applications such as the image portal and living collections database, synced via a GraphQL API that predates Specify's own API.
- A IIIF-compliant image portal is under development; Specify data populates the IIIF Presentation API.
- Seed bank germination tests and orchid conservation data do not fit Specify and will get separate databases.
Notable moments
Transcript
Automatically generated captions can contain mistakes, especially in names and technical terms. Times are relative to the room recording.
Read the transcript ↓
Related talks.
Applying Data Standards at the Royal Botanic Garden Edinburgh
Identifiers are how RBGE is standardising legacy herbarium data and reconnecting items spread across four separate collection management systems.
SpecifyaaS: Managing Ephemeral Repositories in Collections-Based Research
Giving researchers their own lightweight Specify instances early in the research process standardises data from the start and eases later exchange with the institutional collection.
Meeting Biodiversity Standards with Specify 7
Specify's new built-in Darwin Core mapping tool aims to make publishing from highly customised databases straightforward without giving up local flexibility.