How to Build a Digital Herbarium for Angraecum Collections

Why Digitise Angraecum Specimens?

Angraecum orchids are a taxonomically rich group endemic to Madagascar and surrounding islands. Their morphological diversity and specialized pollination biology make accurate specimen data essential for taxonomy, conservation, and research. A digital herbarium preserves fragile sheets, reduces handling, and makes the information globally searchable.

Scope of This Guide

This workflow is intended for:

• Botanical institutions or university herbaria holding tens to thousands of Angraecum sheets.
• Dedicated hobbyists with a focused Angraecum collection (e.g., 100–500 specimens).
• Projects that aim to share data via platforms such as GBIF, iDigBio, or the Global Orchid Database.

All recommendations assume access to a computer, a high‑resolution camera or scanner, and basic internet connectivity.

1. Choose a Collections Management System (CMS)

The backbone of any digital herbarium is a CMS that can store specimen metadata, images, and links to external resources. Specify 7 has been adopted by several major herbaria, including the Royal Botanic Garden Edinburgh, where it supports accessioning, loans, and data exports to aggregators [1]. Its flexible data model allows you to record Angraecum‑specific fields (e.g., pollinator notes, elevation) while maintaining compatibility with international standards.

Alternative open‑source options (e.g., Symbiota, Arctos) exist, but Specify 7 offers a mature API for automated data exchange, which is valuable when linking to DNA sequences or 3D models [3].

2. Plan the Digitisation Workflow

Mapping the workflow before starting prevents bottlenecks. A modular approach separates three core pipelines: specimen handling, image creation, and data capture [5]. Each module can be performed on‑site or remotely, and the hand‑off points are clearly defined.

Scroll to explore the table →

This structure mirrors successful projects at Meise Botanic Garden and the University of Melbourne [4], [5].

3. Imaging – Capture High‑Quality Visuals

Image quality directly influences downstream data extraction. A dedicated workflow that includes built‑in image quality checks reduces re‑shooting rates [6]. Recommended steps:

1. Set up a copy‑stand with diffuse lighting (e.g., LED panels at 5000 K) to avoid glare.
2. Use a calibrated DSLR or a high‑resolution flatbed scanner capable of 24‑bit colour and at least 300 dpi; many institutions use 600 dpi for small orchids to capture spur detail.
3. Include a scale bar and colour chart in each frame for later measurement and colour correction.
4. Save files in lossless TIFF for archiving; generate JPEG derivatives (≤ 80 % quality) for web sharing.
5. Record metadata (camera settings, file hash) automatically via EXIF or a side‑car JSON file.

For small collections with limited budgets, a smartphone with a macro lens and a portable light box can achieve acceptable results, provided the images are later checked against the quality criteria outlined in [6].

4. Capture Label Data

Labels contain the taxonomic, geographic, and collector information that makes a specimen useful. Automated optical character recognition (OCR) can speed up transcription, but mixed handwriting and historic typefaces often require manual verification [2]. A practical protocol:

1. Run OCR on the label image using an open‑source engine (e.g., Tesseract) trained on botanical fonts.
2. Review and correct the OCR output; flag unreadable sections for expert review.
3. Standardise fields to Darwin Core terms (e.g., dwc:scientificName, dwc:locality, dwc:recordedBy).
4. Georeference locality strings with tools such as GEOLocate; store latitude/longitude with uncertainty.
5. Link to the image via a persistent identifier (e.g., a UUID or DOI) in the CMS.

When resources are scarce, a “minimal viable dataset” (collector, date, locality, and species name) can be entered first, with richer fields added later.

5. Adopt FAIR Data Principles

FAIR (Findable, Accessible, Interoperable, Reusable) standards ensure that your digital Angraecum specimens can be integrated with other biodiversity data. The “digital specimen” concept bundles the physical specimen, its image(s), DNA barcode, and literature citations under a single persistent identifier [3]. Implementing this model involves:

• Assigning a globally unique identifier (e.g., a UUID) to each specimen record.
• Publishing metadata in a machine‑readable format (e.g., JSON‑LD or CSV adhering to Darwin Core).
• Depositing images in an open repository that provides persistent URLs (e.g., Zenodo, GBIF’s Media Archive).
• Linking to external resources such as GenBank sequences or published taxonomic revisions.

These practices were highlighted in the digital specimen repository study, which demonstrated improved data reuse across institutions [3].

6. Quality Control (QC) and Data Validation

QC should be performed at two levels: image QC and data QC. Image QC checks focus, colour fidelity, and file integrity; data QC checks verify taxonomic names against a reference (e.g., Kew’s World Checklist) and ensure geographic coordinates fall within plausible bounds. A simple QC checklist (adapted from the Meise mass‑digitisation lessons) includes:

1. Is the image sharp and free of shadows?
2. Does the file checksum match the recorded hash?
3. Are all required Darwin Core fields populated?
4. Do the coordinates correspond to the reported locality (using a GIS tool)?
5. Has a taxonomic expert reviewed the species identification?

Automated scripts can flag records that fail any step, allowing curators to address issues before public release [4].

7. Publish and Share

Once QC is complete, export the dataset in Darwin Core Archive (DwC‑A) format and register it with aggregators such as GBIF or iDigBio. Specify 7 includes built‑in export tools that generate DwC‑A bundles and assign DOIs [1]. Publishing not only increases visibility but also satisfies funding agency requirements for open data.

Consider creating a project webpage that displays a gallery of Angraecum images, links to the specimen records, and provides download options for researchers interested in phylogenetics or pollination ecology.

8. Ongoing Maintenance

Digitisation is not a one‑time event. New field collections, taxonomic revisions, or additional media (e.g., DNA sequences) should be added to the digital herbarium. Schedule periodic audits (e.g., annually) to verify that links remain functional and that taxonomy is up‑to‑date. The modular workflow described in [12] makes it easy to insert new modules without overhauling the entire system.

9. Special Considerations for Angraecum

Angraecum specimens often include delicate floral parts that are prone to damage during handling. Use gloves and a soft brush when removing dust, and photograph flowers before any destructive sampling (e.g., DNA extraction). Because many species are pollinated by long‑tongued hawkmoths, high‑resolution close‑ups of the spur and nectar column are valuable for future functional studies; allocate extra imaging time for these structures.

Summary Checklist

• Select a CMS (e.g., Specify 7) and configure Angraecum‑specific fields.
• Map a three‑module workflow: specimen prep → imaging → data capture.
• Capture 300 dpi+ colour‑accurate images with scale bars.
• Transcribe labels using OCR + manual review; store data in Darwin Core.
• Assign persistent identifiers and publish under FAIR principles.
• Run QC checks before uploading to GBIF or similar portals.
• Plan for regular updates as new material arrives.

Following these steps will produce a robust, searchable digital herbarium that safeguards Angraecum biodiversity information for taxonomists, conservationists, and pollination researchers alike.