📋 Metadata Standards and Open Data Practices for Apiary Research

About this simulation

Every hive-inspection sheet, weight-scale reading or Varroa count is only as useful to future researchers as the metadata attached to it. This pipeline turns that abstract idea into something you can watch: raw data packets stream out of a field hive, pass through three metadata "gates," and either join a glowing FAIR archive crystal or drop away as orphaned, unusable data.

How it works

• Gate 1 — Field completeness checks whether a record carries the core fields a reader needs: timestamp, location, apiary ID, method. Packets missing fields glow dim and are more likely to fail.
• Gate 2 — Vocabulary conformance checks the record against a controlled vocabulary / schema (e.g. Darwin Core-style terms) at the strictness you set. Higher strictness rejects more loosely-tagged records but raises overall data comparability.
• Gate 3 — Open license checks whether a machine-readable open license (like CC BY) is attached — a hard requirement for the record to be truly "open," independent of how well-formed it is.
• Records that clear all three gates spiral up into the FAIR archive, which grows a facet for every accepted record. Rejected records fall into the grey orphaned data pile beneath the pipeline.

Controls

• Field completeness — the average share of required metadata fields real incoming records actually carry (0–100%).
• Vocabulary conformance — how strict the schema/vocabulary gate is; higher values demand cleaner, more standardized tagging.
• Record sampling rate — how many records per second the field station emits.
• Open license toggle — whether new records are published with a machine-readable open license attached.
• ↺ Reset archive — clears the archive and orphan pile. Drag to rotate, scroll to zoom.

Did you know?

The FAIR principles — Findable, Accessible, Interoperable, Reusable — were published in 2016 specifically to make data machine-actionable, not just human-readable. For apiary research, that means a Varroa count from one country's hives can be automatically compared with another's only if both used compatible field names, units and licensing metadata from the start.