Part of the six-part Patron Management in Destiny Library Manager and Destiny Resource Manager: Where to Start series.  

By the time duplicate patron records show up, someone is usually already frustrated. A transfer does not land where it should. A student has trouble checking out. An update runs, and the Job Summary is full of messages no one was hoping to see. 

If the first posts were about understanding your process and checking your records, this one is about one of the most common headaches that shows up next: duplicate patron records and barcode conflicts. 

In my school and district roles, I saw that duplicate issues are rarely random. Usually, there is a reason they happened, and once you understand the pattern, they get much less intimidating. 

Why These Issues Happen 

Most barcode conflicts happen when Destiny is trying to add, transfer, or associate a patron record, but the barcode number already exists for another patron at that site. 

Patron barcode numbers must be unique at each site, so an add or update that would create duplicate barcode numbers within a site is blocked. A common cause is a manually added patron record with a missing or mismatched District ID. When the incoming update cannot match that manual record correctly, the update may treat the incoming record as new, and that is when the conflict appears. 

The problem may look like a barcode issue, but the underlying problem is often a matching issue. 

What a Barcode Conflict Usually Means 

If a patron update fails because of a barcode conflict, the Update Patrons Job Summary: Resolve Barcode Conflicts Help Article is one of the best places to start. 

Barcode conflicts can occur when an incoming patron record does not align with an existing record or site association. 

In one scenario, the District ID in the incoming data does not match an existing manually added record, so the update treats the incoming record as new. Because that barcode is already assigned at the site, Destiny prevents a duplicate record from being created. 

In another scenario, the District ID matches an existing patron record and the update processes the change as a transfer or additional site association. If the barcode is already assigned at the destination site, Destiny prevents the duplicate assignment. 

In both cases, the Job Summary helps identify how the incoming data and existing patron records need to be reconciled. The appropriate next step depends on whether the update was attempting an add, transfer, or site association. 

If the affected site uses Follett Destiny® Resource Manager, also review the patron’s Access Level and Resource Group at the target site. Correcting the barcode or District ID may resolve the import conflict, but the patron’s resource access should still be verified separately. 

Why Deleting is Usually Not the Best First Move 

When trying to clean things up quickly, it is tempting to delete the record that seems to be in the way. I would not start there. 

One recommendation would be not deleting the existing blocking record in these scenarios because it may have outstanding checkouts or transactions attached to it. Taking the faster path can easily create more work later. 

What to Do Instead 

If the issue is a failed add, the recommended fix is to edit the existing record, update the District ID to the correct value shown in the Job Summary, and then reload the XML file. 

If the issue is a failed transfer or association, the recommended fix is usually to merge duplicate patrons, then reload the XML file. The merge process keeps the complete preferred patron record and its current transactions and statistics, and it adds current transactions, statistics, and other information from deleted duplicate records. 

That is a much better outcome than deleting a record and hoping nothing important was attached to it. 

Habits That Help Prevent Repeat Issues 

A few small habits can prevent a lot of duplicate cleanup later: 

Require District ID for patron records if that fits your district’s process. 

• Be consistent about how incoming records are matched during imports. 
• Compare incoming barcodes or patron IDs with patron barcodes already in Destiny to help prevent duplicate patrons from being added. 
• Review how the import is configured to handle duplicates: skip, merge, or replace. 
• For Destiny Resource Manager sites, confirm that the incoming patron data and site configuration support the correct Resource Group. 
• Be careful with manual edits when your district has an automated update process, because those changes may be overwritten when the update runs. 

What I Would Check First 

If I were reviewing duplicate issues, I would: 

• Read the exact wording in the Job Summary. 
• Identify whether the problem is a failed add or failed transfer. 
• Compare the District ID on the existing record to the incoming data. 
• Decide whether the fix is updating the blocking record or merging duplicates. 
• Reload the update only after the underlying record issue is fixed. 

That approach is slower than guessing, but much faster than fixing the same problem twice. 

Your Beginning-of-Year Takeaway 

If duplicate patron records or barcode conflicts appear, do not assume the quickest fix is deleting a record. 

• Read the Job Summary closely. 
• Identify whether the problem is a failed add or failed transfer. 
• Update the blocking record when the District ID is the issue. 
• Merge duplicate patrons when the records truly need to be combined. 
• Reload the update only after the record issue has been resolved. 

Read Next: Make Scheduled Patron Updates Work for You in Destiny Library Manager and Resource Manager 

Read Previous: Start the Year Strong with Up-to-Date Patron Records in Destiny Library Manager and Resource Manager 

This post is part of the six-part Patron Management in Destiny Library Manager and Destiny Resource Manager: Where to Start series. 

About the Author 

Richelle O’Neil spent a decade serving schools as both a librarian and district administrator before bringing that firsthand experience to Follett Software. As a Customer Success Manager specializing in the Follett Software Library Suite, she understands the day-to-day realities schools face and what it takes to support them well. At home in Texas, she is usually trying to keep up with her two rescue dogs, Ben and Gracey.