Conservation & Fieldwork·Guide
Why open standards (Darwin Core)
“We speak Darwin Core” is not a badge. It is an architectural answer to a concrete failure mode: when every lab invents its own species columns and habitat vocabularies, combining camera-trap datasets across institutions becomes functionally impossible, and export becomes a private dialect, not a shared language.
What open standards buy you
Four reasons the schema is shaped this way
Combinable exports
Camtrap DP and Darwin Core exist because Smithsonian, WCS, Conservation International, and others hit the wall of incompatible names and habitats. A partner package should mean something outside your tenancy.
Stable species identity
GBIF-backed suggest stores a scientific name and a taxon key, not freestyle spelling that silently breaks your own filters six months later.
One photo, many animals
Observations are rows linked to media, not fixed columns on the file. Zero, one, or several animals in a frame is a first-class case, not a spreadsheet mashup.
Hidden when unused
Wedding and commercial tenants see zero field UI unless the conservation capability is on. Complexity stays opt-in.
Fragmentation before the standard
Researchers across major institutions independently found that inconsistent species-name authorities and incompatible habitat vocabularies made it functionally impossible to combine camera-trap datasets. That pain is what drove Camtrap DP, not a desire for prettier CSV headers. Aligning to Darwin Core and Camtrap vocabulary is how ArtInStack stays honest with that history instead of inventing a private “bio fields” dialect.
When you export a Camtrap DP package from a survey, the field names are meant to be recognizable to partners who never logged into your account. That is the difference between “technically downloadable” and “genuinely combinable.”
What “speaking the language” means in practice
In the Media Library, species entry prefers GBIF-backed autocomplete: scientific name, vernacular when available, and a stable taxon key. Free text is the exception, not the design center, because typos become filter ghosts.
Export follows the same spine: deployments, media, and observations as separate tables with Camtrap-shaped headers. The observation is the shared record the two-stack problem was missing, not a caption scribble on the JPEG.
Why observations are not columns on the file
A single frame can contain no animals, one animal, or several. A rigid “species” column on media cannot represent that without lying: merging animals, inventing a primary, or forcing one-row-per-file fiction. Observations live as their own records linked to media so N detections stay honest, reorderable, and exportable.
That is the tradeoff a technical evaluator should see defended: slightly more structure in the model, far less damage when the photo is a multi-species event or an empty trigger.
What other tenants never see
If the conservation capability is off, there are zero observation rows to manage and no field-survey chrome in the dashboard. The same media spine serves weddings and wildlife; the science surface stays dormant until you need it.
For how to create surveys, tag species, and export a package, start at Tag species and observations and Export a Camtrap DP package. For the privacy judgment when those observations go public, continue to Publishing sensitive species.
Standards first, then judgment
Open vocabulary makes collaboration possible. Careful publishing decides what the public path is allowed to show. Read the sensitive-species guide before you flip public panels on for elevated taxa.
Also in Guides: Publishing to GBIF: endorsement first · Publishing sensitive species · Field conservation’s two stacks