Items and Collections

A site's contents are all represented by a single resource model, distinguished by type.

Type	Role
item	One material. The basic unit of a site, carrying images, metadata and a thumbnail
collection	A grouping of items, used to organise by theme or fonds
media	An image (facsimile) attached to an item; a child resource of the item
page	A static page within the site ("About this database", etc.)
annotation	A note on an image, stored and displayed as a IIIF annotation

Resources form hierarchies via parent_id (media → item, item → collection, …).

Metadata

Each resource can carry free-form metadata. Dublin Core dcterms:* keys (e.g. dcterms:creator) are recommended. Metadata feeds search and facets (filtering).

• metadata.thumbnail — thumbnail image for listings/cards
• metadata.lat / metadata.lng — coordinates for the map view
• body (transcription/full text) — long text that becomes full-text searchable

RDF vocabularies that assist metadata entry can be managed under "Vocabularies" in the dashboard.

Ways to register

Items are registered mainly by:

• CSV bulk import (Omeka CSVImport-compatible) — upload a CSV from the dashboard's site detail. Choose the kind — item_sets (collections) / items / media — and validate (dry-run) to preview counts and error rows before importing. Sample CSVs are downloadable
• API (programmatic) — POST /dl/{db}/resources one at a time, or POST /dl/{db}/import in bulk. See Developers

Binaries such as images are uploaded directly to S3-compatible storage using a presigned URL issued by the API.

About editing individual items

The dashboard currently has no screen for editing items one by one. Items, collections and media are created/updated through the CSV or API above (the only resource editable directly in the dashboard is News).

Public / private

Each resource has its own public/private flag (is_public). A private resource never appears in listings, search or the API, even when the site itself is public. You can keep draft items private while preparing a site before publishing.

Work in progress

The CSV column spec (Omeka CSVImport-compatible mapping), supported image formats and the IIIF derivation flow, and the TEI import procedure are yet to be documented.