From a shoebox of lists to an archive you can trust.
Three volunteers, three ways of typing a box list. Archival Index turns them into consistent records, makes two different people check each one, keeps the history of every change, and publishes only what passed.
- Role
- Data standards, records QA, product
- Platform
- Web app, plus a SQLite export
- Built with
- JavaScript, SQL (SQLite), Python
- Status
- Concept study · working app
01 / The problem
Same archive, three volunteers, three formats.
Small archives run on volunteers, and every volunteer writes a box list their own way. Before anyone can search the collection, those lists have to agree, and someone has to be able to say who checked what.
"c.1968", "1972-74", "1970s", "05/06/1974". People can read them; a search box can't.
Whoever typed the list also checks it, so their mistakes go straight into the catalogue.
When a title changes, nobody can say who changed it, when, or what it said before.
A concept study, honestly framed. The Millbrook Arts Council, its volunteers and its records are invented, and there was no formal research. The workflow follows common archival practice: controlled vocabularies, two-person checking and recorded provenance.
02 / The normaliser
Type a line the way a volunteer would.
This runs the app's own normaliser. It reads all three formats, builds a call number, cleans the title, picks a record type from a controlled list, turns the date into something a computer can sort, and raises the checks a cataloguer has to deal with.
03 / The workflow
Four stages, and nobody checks their own work.
Every record moves from a raw line to the public finding aid, and every step is recorded in its history.
DraftIntake
Preview a list as written beside the normalised records. Nothing is added until you confirm, and unreadable lines are named.
CataloguedFirst pass
A cataloguer fixes each record against its source line. Every check must be fixed or acknowledged with a note.
VerifiedSecond pass
A different person compares record and source, then verifies it or returns it with a reason.
PublishedFinding aid
Only verified records appear, arranged by series, box and folder, ready to search or print.
04 / Standards
Dates people can read and computers can sort.
Each date keeps a readable form for the finding aid and a start and end for searching and sorting. This table is produced live by the same code as the app.
| As typed | Shown as | Machine range | Flags |
|---|
05 / The data layer
A database that enforces the same rules.
The workbench exports a SQLite script: series, records and every history event. Its constraints repeat the app's rules, and a short Python script reads it to produce a QA report.
status TEXT NOT NULL CHECK (status IN ('draft', 'catalogued', 'verified', 'flagged')),
catalogued_by TEXT,
verified_by TEXT,
-- Two-pass QA: a verified record names a verifier who is not its cataloguer.
CHECK (status <> 'verified' OR (verified_by IS NOT NULL AND catalogued_by IS NOT NULL AND verified_by <> catalogued_by)),
CHECK (date_start IS NULL OR date_end IS NULL OR date_start <= date_end)
CREATE VIEW finding_aid AS
SELECT s.title AS series, r.box, r.folder, r.call_number, r.title, r.date_display, r.extent
FROM records r JOIN series s ON s.id = r.series_id
WHERE r.status = 'verified'
Archival Index QA report: 36 records
Status
verified 16 ###########.............
catalogued 8 #####...................
flagged 1 #.......................
draft 11 #######.................
Boxes (verified / listed)
Box 1 5 / 5 ############
Box 2 3 / 5 #######.....
Box 3 4 / 5 ##########..
…
Dates: 3 undated, 7 approximate
Two-pass rule: OK
Work by person
maya catalogued 23 verified 0 returned 0
sam catalogued 2 verified 16 returned 1
Finding aid: 16 of 36 records published
06 / Screens
The workbench, captured from the app.
Select any screen to see it larger.
07 / Try it
The real workbench, with the sample collection.
Switch between Maya, the cataloguer, and Sam, the verifier, at the top right. This demo starts fresh each time; the full app keeps your work in your browser.
- 1
Import box list C. Intake → Preview, then add it, and spot the duplicate folder.
- 2
Catalogue a record. Fix or acknowledge its checks, then mark it catalogued.
- 3
Try to verify it as Maya. You can't. Switch to Sam and verify it, then find it in the finding aid.
Everything stays in your browser. Export a SQLite file from the Data page whenever you like.
Open the full app08 / How it's built
Rules in small pure modules, a thin interface on top.
The normaliser, the workflow and the exporters know nothing about the page, so the same code runs the workbench, the demo above, and the script that generated the sample export.
- ~1,390lines across JavaScript, CSS and Python
- 3box-list formats read without being told which
- 8checks a cataloguer must fix or acknowledge
- 0records published without two people
- A normaliser with no side effectsnormalize.js reads lists, parses dates, guesses types from a controlled vocabulary and lists checks. Text in, records out.
- One door for every changeworkflow.js is the only code that edits a record, and each edit adds a history event with who, when, and before and after.
- Checks that block, not nagA record can't be catalogued while a check is open. Acknowledging one needs a note, which is saved in the history too.
- Rules repeated in the databaseThe SQLite schema's CHECK constraints match the app, so an export edited by hand still can't publish an unchecked record.
- Standard library Pythonqa_report.py loads the export into an in-memory SQLite database and needs nothing installed.
- Searchable finding aidSearch covers every field, including the volunteers' original wording, and the finding aid prints cleanly.
09 / What I'd test next
What a real archive would teach it.
The workflow is built on common practice, but it hasn't met real volunteers or real boxes yet.
Collect real box lists and measure how often the type, date and extent come out right first time.
Test: a corpus of real listsSmall archives may have one regular volunteer. A lighter rule, such as sample checking, might be needed.
Test: interviews with archive managersEight checks catch real problems, but too many acknowledgements could become box-ticking.
Test: time-on-task with and without checksEAD or a catalogue system's import format would let records move into a real collection system.
Next: an EAD export
