One description, everywhere it’s needed.
Most tools make you describe your material once for the finding aid and again for the website. Quirow treats the archival description as canonical and reads everything else from it.
The workflow
From a box of scans to a published site.
01
Describe the material
Describe to Describing Archives: A Content Standard, with full Part I and Part II support. Build real multilevel hierarchy — collection to series to file to item — where each level stores only what is set at that level and inherited values are computed when the record is read, so correcting a collection-level statement corrects everything beneath it.
Name access points come from live Library of Congress lookups rather than retyping, and controlled vocabularies are real tables, not free-text fields you hope stay consistent.
02
Attach the files
Digital objects hang beneath the records that describe them — images, audio, video, PDFs, or pointers to material hosted elsewhere. Uploads go straight from your browser to object storage, so file size is not bounded by what a web form will tolerate, and every institution’s files live in their own bucket.
03
Curate the pages
Compose a landing page, an about page, and narrative exhibitions by dragging blocks into place. An item card points at a record you have already described, so what a visitor reads is the description you maintain — editorial framing lives on the page, never written back into the description.
Themes read from a token layer rather than from the content, so re-theming a site does not mean rebuilding its pages.
04
Publish and be found
Your site goes live at your institution’s own address with your logo, navigation, and colors. Alongside the curated pages sits a faceted research view, so a scholar who wants to browse the collection at every level can do that instead of reading the exhibit you happened to build.
Under the hood
Decisions that are hard to change later.
The parts a migration would be painful to undo, settled deliberately rather than by accident.
Not yet
What it doesn’t do.
Quirow is in development, and the feature list is deliberately short. Accessioning, location and container tracking are on the roadmap rather than in the product. Machine interfaces for harvesting and exchange are planned but not built. There is no automated transcription, no OCR, and no machine-generated description — the words belong to whoever is accountable for them. Sign-up is not self-service; institutions are onboarded directly.
If something here matters to you and falls on the wrong side of that line, that is useful to know. Get in touch, or read more about the project.