How patron records are loaded in Alma
We load patron records every day in Alma with user information received from the Identity Management office in OIT.
Records are loaded in two ways:
An “incremental” file - this is generated by OIT daily and captures users who were added, changed, or dropped from our feed from the previous day. This update file runs daily.
A “full” file - this is generated by OIT weekly and captures all users in groups that should be entitled to library service. This update file runs weekly, on Sunday mornings.
What happens when Duke patrons are “dropped” from the identity management feed?
When the identity management feed captures that a Duke patron is dropped:
We update the Duke patron’s account in Alma and set the account expiration date and patron role expiration date to that day. Their account will show as not active in an Alma search.
We add a note to the patron record indicating that they had been dropped from the data feed on a specific date: “User no longer in central data feed as of [DATE].”
How are DKU patrons who are enrolled in Durham loaded into Alma?
DKU undergraduates and graduate students are loaded into Duke’s Alma instance when we receive information in identity management that indicates that they are enrolled in a course or course(s) in Durham for that term.