<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>The Move to Hosted EZprozy Experienced by Texas Tech University</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Justin</mods:namePart><mods:namePart type="family">Daniel</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Lynne</mods:namePart><mods:namePart type="family">Edgar</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>OCLC EZproxy provides access to off-campus users via IP address authentication. It acts as an intermediary between a libraries’ network and secure online resources, such as subscription databases. Texas Tech University Libraries moved from a locally maintained EZproxy server to a hosted instance at OCLC in the summer of 2014. We will talk about the challenges and issues we faced, and offer several recommendations for those considering a move to or a new implementation of a hosted EZproxy service.</mods:abstract><mods:classification authority="lcc">General Topics</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2016-05-04</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>