Has anyone run a structured audit during a legacy migration into TMS to reconcile physical tags with records? We’re moving 12,400 objects this quarter and a 10% spot check turned up 3.2% date/number mismatches from a 2001 accession batch; I’m weighing a barcode retag with Tyvek (Code 128) against a desk-based correction to limit handling — what’s worked for you without compromising preservation?
I’d do a targeted pass on that 2001 batch: add a temporary ‘LegacyTag’ field in TMS and run a scan-to-validate cart so you scan the old tag, the TMS record, and a preprinted Code 128 Tyvek label; only mismatches get retagged. We had a ‘3.2%’ issue on a 2002 set and this cut handling to about 18% while the rest were fixed desk-side from the captured legacy values. Would you pilot that on the 2001 group before committing to a full retag across all 12,400?
Do a quick delta audit — freeze edits on the 2001 batch, run a one-off script to normalize date/number formats in TMS, then only retag items that still fail a scan-to-record match during normal handling (like flossing for data). @melissa_j84’s cart idea pairs well with a fast photo capture of the legacy tag into the record so you preserve provenance while swapping to Tyvek Code 128. If access is tight, start with desk-based normalization and defer physical retagging to move week.
Given 12,400 this quarter and “3.2% mismatches,” I’d stand up a temporary Reconcile location in TMS and run move-by-scan; anything that fails gets a barcode overlabel on the existing Tyvek in situ, no full retag… Piggybacking on @melissa_j84, add a quick photo of the legacy tag to the record when you overlabel so desk fixes stay auditable and you only handle once. If your shelves are tight, park failures in a rolling quarantine cart until the overlabel and photo are done.