Moving a library to RFID, step by step.

The most common worry we hear about RFID is not the price — it is the disruption. "Do we close for a month?" The honest answer: no, but the project has a long pole, and knowing where it is makes everything else calm. Here is the transition as it actually unfolds.

Start with the data, not the devices

Before anything is unboxed, the collection's identifiers need one honest look. Are accession numbers consistent? Do barcodes match catalog records? Every inconsistency you fix now is an alarm, a failed self-service loan, or a confusing inventory row you will not have later. RFID makes your data visible at every door and desk — it rewards clean naming and exposes sloppy naming. (This is the heart of the one-identity idea.)

The site assessment

A walkthrough with the implementation partner settles the physical questions: where gates fit the entrance, where the kiosk catches the natural flow, where the desk reader sits, what the network and power situation looks like. Hardware is specified here — for your building and your collection, as a set that is proven to work together.

Tagging: the long pole

Every item gets a tag, and the tag gets the item's identifier. This is honest, repetitive work, and its duration is driven almost entirely by collection size and how many hands you can devote. The practical pattern: tag section by section, keep circulating normally, and let the two worlds overlap — a book tagged today simply starts enjoying RFID today. Items already carrying suitable tags from a previous system can often be re-used; the assessment confirms it. Printing and encoding labels in-house means new acquisitions arrive on the shelf already tagged, so the collection never drifts back.

Connecting the library system

AtēnaOs integrates with your library system — the catalog, patron records, and loans stay exactly where they are. There is no data migration, which surprises people who have lived through system changes before: this is an addition on top of your records, not a replacement of them. The integration is verified against real records before anything goes live.

Devices, training, go-live

Installation of kiosks, desk readers, and gates is days, not weeks — the calm part of the project, if the assessment was done well. Training matters most at the desk: staff should feel that batch lending, gate permissions, and the handheld tools save them motions, because they do. Go-live is best treated as a soft event: switch on, watch the first busy day, adjust the small things (a prompt here, a gate sensitivity there), and only then announce it loudly.

What can go wrong (and how it is avoided)

• Launching with an half-tagged collection — patrons lose trust in the kiosk. Tag first, celebrate later.
• Messy identifiers — every duplicate or mismatch surfaces as noise. Clean them up front.
• Forgetting the failure paths — decide early what a patron sees when a loan cannot complete, and where staff take over.
• Treating security as separate — if gates and circulation do not share live data, you will be reconciling them by hand forever.

End to end, a typical transition is measured in weeks, with tagging setting the pace. The library stays open the whole time.

Continue reading: What a library needs for self-service · Frequently asked questions