…example (private university)...
…Patron Library validation
- Links to web databases and online journals point to ASP scripts on our NT server that performs the following functions:
- Use a “PURL” passed to the script to look up the resource in a relational (MS Access) database; the Access record contains the actual URL for the resource, information on what patron groups are allowed access, and on what type of proxy connection is required (e.g., IP-validating vendors require proxy only if user is coming from off campus; vendors using username-password require proxy logon from anywhere).
- Check the user’s IP address to see if it is 1) on campus, and 2) an OPAC terminal accessible to the general public.
- Writes entry to log used for collecting usage statistics.
- Puts this information together and directs the user’s browser either directly to the URL for the resource or directs to Ezproxy with the vendor URL as a parameter. (Ezproxy has built-in mechanism for granting access to an IP range without requiring a front-end script, but since we need the front-end script for other purposes, we do this check in the script.)