Core Architecture
A normalized data layer for collections: canonical object schemas, controlled vocabularies (Getty AAT/TGN), LIDO-to-database mapping, and secure collection APIs.
Open Core Architecture →Museum Collection Management & Digital Asset Workflow Automation
Standards-aligned, automation-focused engineering for cultural-heritage collections — built for collections managers, museum tech staff, and Python automation engineers.
This is a practical resource for teams building the data backbone of modern museums. It focuses on the engineering that turns heterogeneous accession records, scanned finding aids, and legacy exports into clean, standards-compliant collection data — modeled against canonical schemas, validated at the boundary, and published through interoperable delivery endpoints.
Every guide is grounded in real cultural-heritage standards — LIDO, Dublin Core, IIIF Presentation API 3.0, Getty AAT/TGN, and RightsStatements.org — and in production-grade Python 3.9+ patterns: Pydantic validation, asynchronous ingestion pipelines, OCR extraction, and deterministic rights routing. The emphasis is on idempotent, observable workflows that scale without sacrificing preservation guarantees.
Explore the three pillars below. Each section opens with an architectural overview and links down into focused, code-first deep dives you can adapt directly to your collection management system.
Ingestion & Sync
Deterministic, event-driven pipelines for high-volume ingestion and sync — async workers, CSV upserts, OCR extraction, and Pydantic schema validation.
Open Ingestion & Sync →Rights & Licensing
Machine-actionable rights metadata — copyright status checks, public-domain thresholds, Creative Commons routing, and embargo workflows.
Open Rights & Licensing →