1. Third Party Applications: EZproxy
Meghan Weeks
Loyola Marymount University
2013 SCIUG Conference
Wednesday, Oct. 23
Cal Poly Pomona

2. Loyola Marymount University
6,000+ undergraduates and 2,200+ graduates
~200 library databases
~43,300 e-journals
~134,000 e-books
Became III customer in 1990
Upgraded to Millennium in 1999
Upgraded to Sierra in Nov. of 2012
Turnkey site and house our servers on campus

3. Third Party Applications at LMU
EBSCO Discovery Service (EDS)
Serials Solutions 360 Core, 360 Link & 360 MARC Update
DDA records & purchases from YBP
Boopsie Mobile App
ILLiad from OCLC
OCLC Navigator (Camino)
EZproxy from OCLC
360 Core – knowledgebase
360 Link – link resolver
360 MARC updates – MARC records

4. Why switch proxy servers?
Goals
Improve the patron experience
Reduce staff time troubleshooting
Reduce staff time configuring new resources

5. Internal & External Support
No support from III necessary
Campus IT department
Provided a virtual server to host EZproxy
Provided a static external IP address and added host name to DNS server
Opened ports on campus firewall
Purchased a SSL certificate
Systems librarian installed and configured EZproxy and resource configurations

6. Product Selection Process
EZproxy – most commonly used Proxy product
Demo license obtained in May
Setup 16 databases for initial test
Long-standing issues
Unique type of content (streaming)
Popularity of the resource
More than 4,000 institutions in over 60 countries have purchased EZproxy software. (Source:
WAM: only Millennium or Sierra users can use this module of the ILS (Innovative has over 1400 systems installed. Source:

7. Title List for Ezproxy Testing
Gale Biography in Context
CQ Researcher Plus Archive
Gale Business Insights
OneSearch+ (EDS)
Gale Directory Library
Ebrary
Gale Opposing Viewpoints in Context
SAGE Research Methods
Gale Virtual Reference Library
Academic Search Complete
American History in Video
JSTOR
Counseling and Therapy in Video
Proquest Research Library
ARTstor
LexisNexis Academic

8. Implementation Plan
Created a project plan with tasks, timeline, and responsibilities
Configured all of our current resources
Testing
Updated or reloaded records in Sierra
More testing
Updated links on our website, LibGuides, Discovery Service, etc.
Even more testing!
Went live in August

9. WAM vs. EZproxy WAM EZproxy Authentication
LMU username and password (LDAP)
Name and Barcode (Sierra)
No additional LDAP servers can be configured
Local account in EZproxy
Additional LDAP servers can be configured (Law School)
Integration with ILS
Patrons blocks available; Ptype can be used to segment users
No Integration
Access by non-LMU users
Create patron record
Create local EZproxy account

10. WAM vs. EZproxy WAM EZproxy Cost Possibly a small maintenance fee
$500/year
Reliability
Inconsistent
Good
Support from Proxy Vendor
Haven’t needed it yet
Support from Database Vendors with regard to proxy issues
Reports
Limited customization
Troubleshooting
Must be off campus or use 3rd party tool to test
Can set specific workstations to act as if off campus

11. Lessons Learned
Make sure you budget enough time in your project plan for initial configuration and testing
Keep or create a list of places outside the catalog and LibGuides that use a proxied link

12. Lessons Learned
Clean up your LibGuides so that a major change like this is as painless as possible
Even though WAM wasn’t being turned off, everything needed to be migrated during implementation

13. Questions?
Contact Info:
Meghan Weeks