The quiet persistence of the small team rebuilding a public library catalogue
Field notes on the people, places, and systems that keep things moving.
The background
Communities often solve technical problems with social agreements before they reach for new software. A shared rule about response times can outperform an expensive dashboard.
The context matters because the small team rebuilding a public library catalogue sits inside a larger system. A decision that looks local often has consequences three rooms away.
“Maintenance is where ambition meets reality.”
Where the friction shows up
The lifecycle of a device matters more than its launch day. Repairability, spare parts, and clear documentation determine whether a tool becomes infrastructure or landfill.
The strongest version of the small team rebuilding a public library catalogue leaves room for the person who arrives late, the one who is unsure, and the one who has done it before.
A sensible next step
There is a difference between automation that removes a task and automation that hides a task. The first creates time. The second creates a new kind of checking.
There is a difference between improving a system and replacing its memory. The second is much easier to do by accident.
The lesson of the small team rebuilding a public library catalogue is not that everything can be fixed. It is that small, repeated attention is usually where useful change begins.