There are several different methods to authenticate users – Basic Authentication, ILLiad Exclusive Authentication, LDAP, implementing a User Gateway, etc. Whichever way your library chooses to clear users for interlibrary loan privileges, it is important to keep on top of verifying, merging, and disavowing. Of particular importance is the routing rule that prohibits un-cleared users’ requests from automatically going through Direct Request.
The routing rule prevents un-cleared users from requesting items they potentially may not be able to request due to their status at your institution. Various authentication methods can help expedite your patrons’ requests and decrease the amount of time between request submission and receipt of item.
Lightweight Directory Access Protocol (LDAP) is a local network directory service. If available at your institution, ILLiad can use it to automatically authenticate your users. When a user attempts to login to the ILLiad webpages, it will check against your institution’s user directory using LDAP. If the username exists, then the user is granted access. Otherwise the user will not be able to logon to ILLiad.
There are many benefits to using LDAP, which is utilized at many institutions:
For information about LDAP at your institution, contact your information technology department.
In the Customization Manager, go to System|Routing|Routing. From your list of routing rules, select the rule with the description “Default Direct Request Rule.”
Append the following to the end of the MatchString:
and u.Cleared = ’Yes’
This will send all ‘Unclear’ customer requests into your Awaiting Request Processing queue for staff to process once authentication has occurred.
Deleting records using the Database Manager is permanent. Always backup your data first. If you are hosted by OCLC, then contact them if you are considering deleting patron records.
Patron Authentication -