How to Clean Up Library Barcodes Before a K-12 System Migration
Library Resource
What Cleaned Up Library Barcodes Before a System Migration Includes
Barcode cleanup is the process of reviewing, correcting, and documenting item and patron barcode data before it is transferred from one library system to another. It is a data-preparation task, not a substitute for the broader migration plan.
For a K-12 district, cleanup may involve multiple schools, barcode formats, site prefixes, legacy records, withdrawn materials, duplicate copies, and inconsistent exports. The goal is to give the migration team a reliable source file and a clear explanation of exceptions before test data is loaded.
At a glance
- Start with a complete export of item, title, patron, site, and circulation data, not a partial barcode list.
- Identify duplicate, missing, invalid, reused, and inconsistently formatted barcodes before mapping data to the new system.
- Separate records that should migrate from obsolete, withdrawn, duplicate, or out-of-scope records.
- Preserve site and collection context so barcodes remain useful for circulation, inventory, reporting, and accountability.
- Validate a test migration with district and school library staff before approving the final data load.
K-12 districts should clean up library barcodes before migration by creating a complete inventory of barcode-bearing records, applying consistent rules, resolving exceptions, and validating the results in a test environment.
Begin by exporting the data from the current system. Include item or copy records, title identifiers, barcode values, owning site, collection or category, status, and relevant circulation or patron relationships. Do not assume that a barcode report alone contains enough context to identify problems.
Next, profile the export. Look for duplicate barcodes, blank values, unexpected characters, different lengths or prefixes, barcodes assigned to more than one copy, and records that no longer represent active materials. Review whether separate schools use overlapping ranges or whether a site prefix has changed over time. Keep a log of every rule and exception so district staff can explain what changed.
Decide what should happen to each exception. Some records may need a corrected barcode. Others may need to be excluded because they are withdrawn, obsolete, duplicated, or outside the migration scope. Avoid renumbering active materials unless the district has approved the change and understands the effect on labels, circulation history, inventory, and local procedures.
Finally, provide the cleaned export and exception log to the migration team, review a test conversion, and compare representative records from elementary, middle, and high school sites. Confirm that staff can find, scan, circulate, inventory, and report on migrated items before approving the final load. In a Destiny Library Manager implementation, this validation should be completed with the district’s agreed barcode and site rules, not treated as a last-minute scanning exercise.
K-12 Use Cases
District Librarian
A district librarian coordinating a move across several elementary, middle, and high school libraries may discover that each site uses a different prefix and numbering convention. They can document the conventions, identify overlaps, and agree on a district-wide handling rule before the test migration.
School Librarian
A school librarian preparing a legacy export may find duplicate copy records, withdrawn books, and items with unreadable or missing labels. Rather than correcting records one at a time without a plan, they can classify the exceptions, confirm which materials are in scope, and provide samples for migration validation.
IT Lead
An IT or data migration lead may be responsible for transferring files while library staff understand the operational meaning of each field. A shared data dictionary and exception log allow both roles to review barcode mappings, site assignments, and status values before go-live.
Decision Points
Common Questions
Should active barcodes be renumbered?
Usually, no. Preserve active barcode values when they are usable and unique. Consider renumbering only when the district has approved the change and can update labels, procedures, and related records.
What belongs in the migration scope?
Define whether the district is moving active collections only or also withdrawn, lost, archived, textbook, equipment, or other non-library records. Scope decisions should be documented before cleanup begins.
How should different school barcode formats be handled?
First determine whether the formats are valid, unique, and meaningful for district reporting. Standardization may be helpful, but changing formats can create relabeling and staff-training work.
Who approves cleanup rules?
District library leadership should approve policy decisions, school library staff should validate operational impact, and the migration or IT lead should confirm that the rules can be represented in the target system.
Destiny Library Manager has everything I need in one program. All the report options help me see where my collection is, allow me to see stats and usage of books, and let me keep track of books that students have checked out.
Librarian
Supporting Data and Evidence
A Journey of Innovation and Impact
Blake Hopper, the librarian at Tazewell-New Tazewell Primary School, has a unique perspective on Follett Destiny® Library Manager. “I have used Destiny Library Manager for 14 years, going back to my senior year of high school,” Hopper said. “I was a library intern that year and later went on to automate three libraries in the district and re-automate my current library – all with Destiny Library Manager.”
Located near the Kentucky border, Hopper’s elementary school is part of a district that has successfully integrated Destiny Library Manager across all its schools. Hopper explains, “Using Destiny is an easy way to help manage your library. It is designed well, has a lot of functionalities, and is so user-friendly.”
Making the Transition to Better Accountability
Use this resource to support pre-migration data review, accountability, and the need to resolve exceptions before a system change.
Practical Guidance
Create a source-of-truth export.
Record the export date, source system, included sites, included record types, and fields supplied. Preserve the original file before making changes.
Build a barcode exception report.
Flag duplicates, blanks, invalid formats, reused values, missing site assignments, and records that appear withdrawn or out of scope. Add an owner and disposition for each exception category.
Agree on rules before editing.
Document how the district will handle active duplicates, legacy prefixes, missing labels, withdrawn materials, and records that cannot be matched confidently. Obtain approval from library leadership and the migration team.
Test representative records.
Review sample records from each school level and site. Confirm search, scanning, circulation, inventory, reporting, and label workflows before signing off on the final migration.
Run A K–12 Library Without Spending the Day on Manual Work
Barcode preparation is one part of a broader effort to standardize workflows, reduce manual rework, and keep daily library tasks manageable across a district. See Simplify library operations for the related solution context.
FAQ
-
Some corrections can be made after loading, but postponing cleanup increases the risk of duplicate records, incorrect circulation history, and confusing reports. Resolve as many source-data issues as possible before the final migration.
-
No. Usable, unique barcodes can often be retained. The decision depends on the quality of the existing data, the target system’s requirements, and the district’s labeling and inventory policies.
-
Only if the district has a documented reason to retain them. Separate active materials from withdrawn, obsolete, duplicate, or archived records so the migration team can apply the approved scope consistently.
-
Treat it as an exception requiring review. Confirm which physical copy and record should retain the value, then decide whether the other record needs a corrected barcode, a merge, or exclusion from the migration.
-
Use a test migration and compare records from every participating school level and site. Staff should verify that representative items can be found, scanned, circulated, inventoried, and included correctly in reports.
-
No. Barcode cleanup focuses on identifiers and their relationships to items, sites, and patrons. Catalog cleanup may also include bibliographic records, call numbers, subjects, MARC fields, and collection metadata.
Summary
Clean barcode data gives a K-12 migration team a clearer starting point and gives library staff a practical way to validate the converted system. Treat cleanup as a documented data-preparation phase, with approved rules, tracked exceptions, and test-migration sign-off.
