Archives deserve better tools.

Not more powerful ones, necessarily. Ones a small institution can actually run.

The problem

Good software nobody can staff.

The established archival platforms are serious pieces of software, built by people who understand the domain. They also assume an institution with a server administrator, a migration plan, and time to spare. Plenty of collections have none of those, and the software that would describe their holdings properly is therefore the software they cannot use.

What they reach for instead is a website builder. It produces something handsome in an afternoon and gives them nowhere to put a scope and content note, a conditions governing access statement, or an authority record. The result looks finished and describes nothing, and the description work either never happens or happens twice.

Between capable-but-unstaffable and attractive-but-empty there was nothing. Quirow is an attempt at the middle: archival description that would satisfy a professional, a publishing layer that produces something an institution is glad to link to, and no server to maintain.

Decisions

The parts that are hard to undo.

Most of what makes archival software awkward to live with was settled early and cheaply. These were settled early and carefully instead.

Three layers, never mergedDescription records, the digital objects beneath them, and the pages that present them are separate things with separate jobs. Collapsing any two is the decision that makes archival software impossible to evolve later, and it is the one this system will not make.
Description stays canonicalPresentation never writes back. However many pages feature a record, there is exactly one description of it, and editorial framing lives on the page instead — so telling a story about a collection never quietly edits the collection.
Strict storage, computed inheritanceA record stores only what is asserted at its own level. Everything inherited is resolved when the record is read, which is why a correction at the top of a hierarchy is a single edit rather than a hundred.
Themes never touch contentA page’s appearance resolves from a token layer, never from values written into the page itself. Re-theming a site is a change of theme, not a rebuild of its pages.

Refusals

What it won’t do.

There is no automated transcription, no OCR, and no machine-generated description. Description is an act of professional judgment and the words should belong to whoever is accountable for them. The software’s job is to make that work faster to record, not to do it badly on someone’s behalf.

It is also not trying to be everything. Accessioning, location and container tracking are on the roadmap rather than in the product, and the feature list stays deliberately short until each addition has a collection actually asking for it.

See how it works → · Get in touch