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

Patron data mismatches often become visible at the start of a school year. Grade levels may need updating. A new staff member may not yet appear in the current data. A student’s record may need review before checkout. Someone calls the district office, someone else calls technical support, and before long everyone is trying to solve a patron problem before anyone is fully sure how the data gets into Follett Destiny® Library Manager. 

If you are a Destiny Administrator or District User, that probably sounds familiar. This post is part of the six-part Patron Management in Destiny Library Manager and Resource Manager: Where to Start series, and I wanted to start here for a reason. 

Because I supported Destiny first as a school librarian and later as a district coordinator, I learned that many patron issues do not start as record problems. They start as process problems. 

Before you start fixing patron records, answer one basic question: How does patron data get into Destiny in our district? 

Why This Is the Right Place to Start 

When patron data looks wrong, the instinct is to jump straight into troubleshooting. I get it. When people are waiting for answers, it is hard to slow down. 

But if you do not know whether your district is using a scheduled CSV import, an SIS-driven scheduled update, or a OneRoster/ClassLink integration, you can end up checking the wrong process, asking the wrong person, or reviewing the wrong part of the data or support process. 

That is why this needs to come before any cleanup conversation. You do not want patron imports to become your district’s annual mystery novel. 

Start with Three Questions 

Before you troubleshoot anything, get clear on these three questions: 

• How are patron records getting into Destiny right now? 
• Where in Destiny can we confirm that? 
• Who in the district owns or supports that process? 

If you can answer those three questions, everything that comes next gets easier. 

If Your District Uses Scheduled Patron Update 

For many districts, the first place to look is Scheduled Patron Update Overview. This feature lets districts schedule automatic patron updates to keep records current, including adding new patrons, updating existing ones, and optionally inactivating or deleting records. 

Setting up or running a scheduled patron update requires a district-level user with the Manage Patrons for the District permission. If you are reviewing a setup, Schedule a Patron Update is a helpful article because it shows where to find the schedule screen, how Directory and SFTP options work, and when Full versus Incremental updates are typically used. 

In my experience, this is often the first big clue. If someone says, “I think it runs automatically every night,” this is where your district Destiny Administrator can confirm whether that is actually true. 

If Your District Uses OneRoster or ClassLink 

If your district uses Update or modify OneRoster integration, the workflow is different. The OneRoster integration is a paid service that supports scheduled automatic imports of student, teacher, and class data, and the setup is managed through the Roster Back Office after the initial configuration is completed with Follett. 

That matters because a district using OneRoster will not troubleshoot patron data the same way a district using a traditional scheduled CSV import would. If you are looking in the wrong place, everything can feel more confusing than it really is. 

If your district uses Destiny Resource Manager, the same patron import process may support resource circulation and instructional-material access. In addition to checking whether the patron record loaded, verify the patron’s Access Level and Resource Group at the applicable resource site. 

If No One Seems Fully Sure 

Sometimes the library team assumes IT owns the process. Sometimes IT assumes the SIS team owns it. Sometimes a district changed methods a while back, and the people currently supporting Destiny inherited the setup without getting the full backstory. 

If that sounds familiar, do not start by editing a large number of records manually. Start by finding the person who can answer the process question. A useful internal contact list usually includes: 

• The district Destiny Administrator 
• The person who manages SIS exports or student data 
• The district technology or data integration contact 
• The person who reviews scheduled jobs, logs, or roster configurations 

Sometimes the fastest path to solving a patron issue is finding the right owner before fixing symptoms. 

What to Look for While You Are Checking 

As you confirm how your import works, review: 

• Whether the job or integration is still active 
• Who checks results after it runs 
• Whether school mappings, roles, or fields have changed 
• Whether the timing still makes sense for beginning-of-year processing 
• Whether district and site users know who to contact when something looks wrong 

If you want a practical refresher while you do that review, the on-demand webinar Destiny Library Manager and Destiny Resource Manager: Destiny Spring Cleaning – Catalog Edition covers individual, batch, and global update options. Summer Cleanup and Beginning-of-Year Prep: Quick List provides a one-page overview of cleanup and preparation priorities. 

Your Beginning-of-Year Takeaway 

Before you troubleshoot patron records, make sure you know how patron data gets into Destiny and who in your district can support that process. 

• Confirm whether your district uses Scheduled Patron Update, OneRoster, or another supported integration, and identify whether the district uses the data for Library Manager, Resource Manager, or both. 
• Identify who owns or supports the setup. 
• Verify where that process is reviewed in Destiny. 
• Make sure district and site users know who to contact when patron data looks off. 

During the beginning of the year, having fewer mystery problems is a win. 

Read Next: 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.