<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>EZ come, EZ go: User-triggered error reporting in EZproxy</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Alevtina</mods:namePart><mods:namePart type="family">Verbovetskaya</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Off-campus access to library resources is easy with EZproxy. But what happens when users hit broken links--which happens much more frequently with a discovery layer in place? Whom do the students contact? How do you get notified of the troublesome links?&#13;
&#13;
Using Google Forms and some Javascript, you can ensure that users having problems accessing e-resources remotely have a way to report the errors, allowing you to fix problems as they are submitted. This presentation will provide a step-by-step tutorial for setting up user-triggered error reporting in EZproxy, as well as provide examples of actual user submissions. Ideas for future development will also be discussed and questions entertained.</mods:abstract><mods:classification authority="lcc">General Topics</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2016-05-06</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>