Core + Extension

One event, with the right evidence attached.

A bird sighting, a quartz sample, a plankton tow, and an SEM image need different fields. They still share a who, when, where, provenance, and licence. Clio’s planned architecture keeps that common spine intact.

Event core

Every submission starts here.

eventID
platform-minted UUID v4
eventDate
ISO 8601 date or date-time
decimalLatitude
WGS84 decimal degrees
coordinateUncertaintyInMeters
required, including deliberate fuzzing
recordedByID
ORCID iD, where available
license
CC0, CC BY, or CC BY-NC

Extensions

Domain-specific evidence joins the event.

biology
Darwin Core Occurrence
geology
ABCD-EFG, IGSN where retained
media
Audiovisual Core, EXIF
microscopy
REMBI, OME-TIFF, OME-Zarr
sampling
Humboldt Extension
packaging
EML, Darwin Core Archive

Verification is data

The latest identification is never the whole story.

The planned record retains the verbatim submission, normalized values, and every identification event. A status is a queryable state with evidence behind it.

Unverified

As submitted. The original contributor’s words and media remain visible.

Community-verified

At least two independent, agreeing identifiers from established contributors.

Expert-verified

Confirmed by a credentialed curator with an ORCID iD and affiliation on file.

Identity + evidence foundations

Clio keeps the control plane close to the museum.

The repository contains local DID/OIDC and Clio Local Evidence v1 foundations. They are not deployed as production services, and the local evidence protocol must not be confused with the Maatara Veritas protocol.

Clio-owned identities

Clio is designed to mint and resolve contributor did:web identities and hold the keys where possible, with recovery and rotation still required before launch.

Preferred Maatara path

Maatara is the preferred hard-dependency target after portable SDK, licensing, conformance, security, and support gates. Hosted Maatara services remain optional.

Honest evidence status

Local commitments are tamper-evident and designed for future external anchoring. DOI registration is disabled; dataset DOI integration is planned.

The academic handshake

Projection, not translation.

The intended export path is a projection from standard-shaped internal fields into a Darwin Core Archive: meta.xml, eml.xml, and occurrence, event, and media tables. That makes future repository review simpler, but it is not a claim that an export pipeline is live today.

Record layerPlanned outputPurpose
Eventevent.txtWho, when, where, and sampling context
Occurrenceoccurrence.txtOrganism identity and verification history
Mediamultimedia.txtImages, access URIs, and file metadata
Dataseteml.xmlScope, methods, attribution, and licence