Library RFID Tag Replacement: Restore Item Records Without Breaking Circulation

A library does not need to replace its entire RFID system when one book label becomes unreadable. Yet replacing the physical tag carelessly can create a more troublesome failure: a book that scans correctly at one desk but points to the wrong integrated library system (ILS) record, appears as two inventory items, stays on the wrong loan account, or triggers an incorrect exit-security decision. The physical repair is often quick. The identity and transaction repair is the part that deserves a controlled procedure.

This guide is for cataloging staff, circulation supervisors, library RFID integrators and tag buyers who already have an installed library workflow. It covers individual damaged labels, unreadable tags discovered at circulation or inventory, and controlled replacement of a small number of affected book tags. The outcome is a reproducible procedure for deciding whether a tag needs replacement, preserving the correct ILS item record, validating the newly encoded label and releasing the item back into circulation. It does not replace the library's wider RFID system planning guide, which owns new deployments and full system design.

 

 

Recognize the problem before peeling off a tag

"RFID not working" is not a diagnosis. A failed read at a kiosk might be caused by a torn antenna, a bent label, interference from a particular book cover, poor presentation, a changed workstation configuration or an ILS lookup failure. Replacing the label before distinguishing these cases may introduce unnecessary new identifiers and destroy evidence that would have explained the fault.

Start by isolating the item from the normal patron or automated workflow and recording a simple service ticket. Include a visible barcode or item number, branch, date, discovery point, what the reader displayed, whether the problem occurred at a workstation, handheld device or security gate, and whether the book has an active loan, hold or transfer. The visible barcode can be the recovery anchor even if the RFID tag is unreadable, provided staff verify it against the authoritative item record.

Do not assume that a successful radio read means the ILS state is correct. A reader can see a tag while the software cannot resolve it to a current item record. Likewise, a return can fail in the ILS even if the item identifier was captured. The repair procedure should preserve this distinction from the first observation through final release.

 

Quick diagnostic triage

Triage should not become an invitation to rewrite every tag in a troublesome shelf area. If several items show the same failure after an equipment update, escalate the reader or integration change first. If a single item consistently fails on more than one approved device, replacement becomes a reasonable candidate.

 

 

Decide which identifier must survive

Most libraries need to keep the ILS item record stable during a tag change. That record carries bibliographic linkage, circulation status, holds, branch ownership and other item-specific history. The RFID tag is a way of identifying the physical item; it does not have to be the library database itself.

Three values may be involved: (1) the visible barcode or item number; (2) the primary item identifier encoded according to the library's selected RFID profile; and (3) the silicon's native UID. These are not automatically identical. A supplier might print the same number on a label and encode a different value for the ILS, while an encoder or middleware uses the chip UID only as an internal diagnostic field. Which identity is the authoritative lookup key is a local system design decision that must be documented before replacement.

A new physical label normally has its own silicon-level identifier. Staff should not assume that it is necessary-or even possible-to make the new chip UID equal the old chip UID. Instead, the project's approved encoding and ILS mapping rules determine whether the primary item identifier should be preserved on the replacement tag or whether the database must explicitly retire the old link and associate a new one. The same item must not emerge from repair as two simultaneously active inventory records.

The ISO 28560-1:2023 standard overview describes the library RFID data model and its interoperability, inventory, migration and privacy objectives. The related ISO 28560-2:2023 encoding rules are one possible deployed profile; a project may instead use ISO 28560-3 or an approved legacy specification. Do not mix encodings just because both tags operate at 13.56 MHz. System architecture and local profile determine the correct replacement, and neither this article nor a supplier's generic datasheet can certify a library's actual implementation.

 

 

Choose repair, rewrite or replacement deliberately

There are at least three distinct outcomes after triage. Keep the existing tag if a handling or reader issue was responsible and transactions now work under approved conditions. Re-encode the current tag only if the data profile and locking permissions allow it and an authorized staff workflow approves the write. Replace the tag when it is damaged, locked against necessary changes, unsuitable for the substrate, or demonstrably unreliable under the required operation.

Physically damaged adhesive, split antenna material, contamination or delamination may justify replacement even when an occasional read still succeeds. A worn label can behave inconsistently after more handling. Conversely, an apparently intact tag should not be condemned based on one handheld read at an unfavorable orientation. Test against the accepted method for that installed system, rather than inventing a universal read-distance threshold.

For staff planning a replacement order, the existing RFID book-tag buying guide owns product selection, frequency and label construction. Here, procurement matters only to the extent that the replacement must match a previously approved tag and data profile. Changing from HF to UHF, for example, would amount to a system redesign rather than a like-for-like repair.

 

 

Prepare the service desk and protect the ILS record

A workable procedure assigns a cataloging or RFID administrator as the person authorized to create or modify RFID associations. The item should be put into a local hold-for-repair status if the ILS supports it. The library should determine what to do with an active loan, pending return, hold request or transit status before any write is attempted; these are circulation decisions, not RFID hardware instructions.

Before work starts, gather the visible barcode, the ILS item record, the prior RFID record if readable, the authorized encoding profile, known security-state rules, and an approved blank replacement label. Confirm that the replacement stock belongs to an accepted lot and that the encoder is configured for the correct library profile. Use an internal service ticket or work-order reference, not a patron's identity, to trace the repair.

A prudent process does not place patron names, addresses or loan histories onto the item tag. Keep that information where the ILS privacy and retention controls apply. The IFLA Statement on Privacy in the Library Environment and the American Library Association RFID privacy guidelines emphasize minimization and confidentiality: repair records should contain only what technicians need for the task, with access restricted to authorized roles.

If the existing physical tag is readable, capture its approved diagnostic attributes before removal without exporting secrets or patron data. If it is unreadable, the absence of a prior RF value should be recorded instead of guessed. Staff must not fabricate a former tag ID to make the form look complete. The authoritative barcode/ILS linkage becomes especially important in such cases.

 

 

Replacement workflow: identify, encode, validate, then release

The following sequence is a recommended operational model, not a claim about Syntek's installed systems or a single mandatory library standard. Each library should adapt it to its ILS, vendor instructions and privacy policy.

1. Quarantine the physical item. Remove it from unattended circulation and note any active hold, loan or transfer. Create a service ticket with the visible item identifier.
2. Verify the source item record. Confirm title, copy, branch and physical book against the ILS. If the barcode refers to the wrong record, resolve that discrepancy first.
3. Document the prior tag state. Record whether the old tag reads, whether data is corrupt or simply unmapped, and which reader settings were used in triage.
4. Approve the replacement stock. Use the same specified frequency, air interface, data profile, IC/memory capability, label form factor and placement instruction as the installed environment, or open a formal compatibility review.
5. Remove or retire the failed tag. Follow book-conservation rules and label-vendor guidance. Prevent any remaining active old tag from being interpreted as a second item where the technology and placement make that a risk.
6. Encode the new tag under an authorized profile. Use the library's supported workstation application to apply the approved item identifier and other permitted fields. Do not substitute the chip UID for the system's configured lookup key.
7. Verify the written data. Read back the encoded value, confirm its item-record mapping and ensure only the intended label responds in the controlled station read zone.
8. Validate complete circulation. Run staff checkout and return, self-check if applicable, inventory or shelf read, and the actual security-state workflow under the library's approved test method.
9. Close the record. Register old/new mapping or retired identifier as required; record operator, date, device, result, failure actions and final authorization before the item is returned to service.

The order matters. A staff member who sticks on a new tag first and only then asks which ILS item it should reference risks a split record. Recording the expected mapping before encoding is a modest control with significant value during later troubleshooting.

 

 

Handling the old label: physical and digital retirement

A damaged tag is not just rubbish if it can still be read somewhere else. Some tags have intermittent performance: a bench may fail while a nearby high-gain inventory device still detects the old identifier. If both an old and a new readable tag remain on one book, a shelf inventory reader may produce duplicate detections or misleading item associations. The correct physical treatment depends on preservation needs, the tag position and vendor instructions; never damage rare books to remove a label without conservator approval.

Digitally, the system should make clear whether the old encoded identity is retired, retained as a historical alias or retained unchanged while a new chip replaces the physical tag. This decision should not be improvised at the staff desk. Define which software owns the association, whether audit history is preserved, whether a duplicate identifier causes a hold, and how a subsequent scan of the old label would be handled.

A simple audit entry can contain: service ticket, ILS item number, previous RFID identifier if known, new RFID identifier or new chip UID where the local system records it, encoding profile version, technician, device, test results and disposition. It should also record why a different identifier was selected if the library normally preserves a stable item number. Keep sensitive details inside access-controlled systems.

If a book has moved between branches or institutions, the library may have additional interlibrary loan and ownership metadata to preserve. Do not assume that changing an RFID field is equivalent to changing a catalog record. Confirm who owns the item and which database is authoritative before releasing it to another branch.

 

 

Acceptance testing must cover transactions, not only radio reads

A workstation saying "write succeeded" is a necessary technical event when writing, but it is not proof that the book can be borrowed safely. Use a test account and designated staff procedure where appropriate; verify actual ILS transactions and the system's intended exit-security behavior. Do not change patron accounts solely to test a label.

The threshold for a successful pilot is project-specific. Libraries should agree on the required scenarios, representative books, device configuration and failure response before declaring the repair approach acceptable. A one-time successful scan in clear air is too narrow for an item that lives on crowded shelves and moves through kiosks and returns stations.

 

 

 

When one damaged label is actually a wider problem

Several failures in the same place or on the same day often point beyond individual tags. A changed reader firmware version may handle a profile differently; adhesive application errors may affect a particular tag lot; nearby metal structures can change the read zone; a backend interface failure can make every tag look "unknown"; and a barcode-to-RFID import error can map otherwise sound tags to wrong records.

Treat a pattern of failures as a potential incident in the conversion or circulation process. Compare affected branches, label lots, reader configurations, workstation software and when the issue first appeared. Preserve a few failing items for controlled analysis rather than replacing everything and discarding the clues. If a system-wide encoding mismatch is discovered, pause replacement activity until the correct profile is restored.

This is also why quality evidence should be captured per replacement batch. Receiving inspection can compare approved samples, lot labeling, adhesive construction, encoding support and functionality with actual installed devices. Supplier factory claims about "100% tests" or long read range do not by themselves prove a library's end-to-end workflow.

 

 

Exceptions that deserve explicit decisions

A recovered missing book may have an old circulation event unresolved. A withdrawn item may have been mistakenly reintroduced into inventory. A donated copy may carry another library's readable tag. A multi-volume set may use multiple item records and special label placement. A book with a metallic cover may require the approved alternate label location. A security alarm that persists after a successful return may be a software transaction or security-state problem rather than bad adhesive.

For each exception, define the responsible department and next action. Cataloging staff should not unilaterally delete loan history to make a repair test pass. A branch should not overwrite another institution's tag without a defined ownership policy. A tag supplier should not infer a reader malfunction from photos alone. Good incident notes make follow-up by the ILS vendor or RFID integrator materially faster.

The most useful question is: Which authority must accept the item before circulation resumes? The RFID workstation validates the physical label and data; the ILS owner validates the record; the circulation team validates service status; the security integration must behave as configured. A repair is complete only when all applicable layers agree.

 

 

Specifying replacement-tag stock for repeat orders

Procurement can reduce future repair complexity by freezing a replacement-tag specification. Identify the actual library RFID standard/profile in use, air interface, IC capacity requirements, inlay geometry, label size, approved placement, print/barcode relationship, delivery packaging and acceptable sample verification. Record who approves alternates, what change triggers a new reader or kiosk test, and how defective labels are returned or quarantined.

A supplier RFQ for replacement stock should be shorter and more precise than a system-wide tender. It should say which installed system and profile the stock must support, how samples will be verified against an approved reference, and what records the library expects with each lot. It should not imply that the brand of a chip alone guarantees compatibility, or that a label with a different frequency is automatically a replacement.

For organizations considering a full new RFID deployment, broader questions about checkout stations, ILS integration and tag sourcing belong to the existing system owner page. For a replacement stock quotation, the buyer can use the approved product specification as a purchasing baseline, then specify the local repair acceptance rules here.

 

 

The release decision

A book can return to service when it has the right physical label for the installed system, the approved data profile has been written and verified, the ILS item record remains unambiguous, the appropriate circulation and security transactions succeed, and the old tag association is accounted for. If one of those conditions is unresolved, the safer outcome is a documented repair hold, not silent circulation.

Done properly, a single damaged RFID tag becomes a small controlled service task rather than a source of hidden data corruption. The visible barcode, a trustworthy item record and a disciplined test sequence provide the continuity. RFID supplies the electronic observation; the library's ILS and staff remain responsible for the service decision.