Describes a project in which EZproxy authentication was implemented in the Sierra Library System with setup information, documentation process and cataloging practices.

1. EZproxy Implementation
in Sierra
Presented by JoelTonyan, Stephanie Spratt, Mary Beth Chambers
University of Colorado-Colorado Springs
Rocky Mountain Region IUG Meeting July 31, 2015

2. Objectives
• What is EZproxy and why did UCCS migrate to it?
• Identifying Electronic Resources in Sierra that needed to be “proxied”
• Updating electronic resource links in Sierra
• Proxying incoming electronic resource records in Sierra

3. What is EZproxy?
• Authentication software that identifies authorized users of online resources
and provides them with off-campus access to these resources
• Developed by OCLC
• Configured with a list of restricted domains (for instance, ebscohost.com),
and then a method of authentication (campus credentials, library barcode,
IP address, etc.).
• A user clicks on a “proxied” link, which points the user’s browser to the
proxy server, and then they are authenticated. Once authenticated, they
are given access to the restricted resource.

4. Why EZproxy?
Previously, the Kraemer Family Library provided off-campus access to our
resources through aVPN connection. However, because theVPN required setup
on the user’s end, we received many questions at our reference desk about
setting up theVPN. We wanted to reduce these types of questions and simplify
off-campus access to our resources.
We decided upon EZproxy for several reasons:
• It is the most widely-used authentication program in the academic library
world
• I had experience configuring and managing an EZproxy server at a previous
institution

5. What was involved in the setup?
Began initial setup in January 2015 and launched the service in June 2015
What was involved:
• Purchase EZproxy and install it onWindows Server virtual machine
• Configure and test authentication (we used LDAP/Active Directory)
• Configure security parameters
• Add all restricted resources the library subscribes to
• Test all resources off and on campus
• Update all links on the library website, LibGuides, etc.
• Update all electronic resource records within Sierra

6. Implementing EZproxy in Sierra
• Identifying Resources to Proxy
• Updating Existing Records
• Proxying Incoming Records via a Loader

7. Identifying Resources to Proxy
• Use existing lists/tools to compile a list of all resources needing proxied
• ERM
• Catalog
• Various tracking spreadsheets (for example, we built our initial list of electronic resources
needing proxied from a spreadsheet created to track costs over time for all of our electronic
resources)
• If nothing else, work through your active licenses to gather a list of resources which require
authorization to access
• Identify stragglers
• Create Lists in Sierra

8. Compiling a Resource List,Tracking Progress
• Use Sierra, library website to gather details
• Resource name, provider, access points, URL, etc.
• Share the list with others for collaboration
• Google Sheets - https://docs.google.com/spreadsheets/d/10LT4dhOGwbmANtjhjM4l-
LmrGDGFPEj7F8I-3CShBSU/edit#gid=1271861828
• Build in additional columns to track progress
• Catalog link updated, link resolver updated, tested off campus, etc.

9. Testing withTeamViewer
• Since we’re using EZproxy’sAutoLoginIP command to IP authenticate users
on campus, bypassing the login screen, we needed a method to test off
campus while still on campus
• We usedTeamViewer (https://www.teamviewer.com)
• Allowed us to use our home computers remotely for testing, without the
need for a static IP address

10. Updating existing records
• Create a list of bib records for the e-collection that needs to be “proxied.”
• Use the Global Update feature to add the proxy script to the URI.
• Select “ChangeVariable-length Field” option; make sure “Use Displayed Field” is not
checked.
• Find/Replace 856 field |u (URI) data:
Preview  Check for problems.
Process  Records with no changes? -- Create a list of records, based on the existing list, that
have 856s without the proxy script.

11. Proxying Incoming Records via a Loader

12. eBook Load Profile

13. ProxyTranslation Map

14. ProxyTranslation Map, contd.
@delimiter=:
@bar_subfield=true
@case=true
^(.*)$0|u(.*)$0|u(.*)$1:0|uhttps://libproxy.uccs.edu/login?url=1
• Everything prior to “|u” is copied and stored in memory bank “0”
• Everything after “|u” is copied and stored in memory bank “1”
• The contents of memory bank 0 are then pasted into the 856 field, followed
by |u our EZproxy referring URL (https://libproxy.uccs.edu/login?url=), and
then the contents of memory bank 1 are pasted after the referring URL

15. So how does this work in practice?
856 Field Before Being Run through Load/Translation Map
856 40 |uhttp://iopscience.iop.org/book/978-1-6270-5481-2|zview eBook at IOP
Science
856 Field After Being Run through Load/Translation Map
856 40|uhttps://libproxy.uccs.edu/login?url=http://iopscience.iop.org/book/978-1-
6270-5481-2|zview eBook at IOP Science

16. Conclusion
The process went smoother than expected, and our “soft launch” proved so
successful that we have very little to do to finalize settings and records for our full
launch next month.The key to our success? Lots of documentation.
Additional considerations
• Expect to run into numerous broken links within your catalog, both at the database
level and individual resource level
• Use a collaborative document to indicate problem resources
• Ensure that your Create List Review Files are large enough to capture all the batch-
loaded records, by vendor
• Watch for data inconsistencies such as spaces in front of “http:”

17. Thank you! Any questions?

18. Contact Information
JoelTonyan – Systems and User Experience Librarian
jtonyan@uccs.edu
Stephanie Spratt – Electronic Resources and Serials Librarian
sspratt@uccs.edu
Mary Beth Chambers - Director of Cataloging and Metadata Services
mchamber@uccs.edu