<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>Secure Exit, or, Shortening that Line to Leave the Library</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Hank</mods:namePart><mods:namePart type="family">Sway</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Several libraries at Harvard University have security desks at their entrances. Guards routinely check each Harvard-owned item leaving the library to make sure that it has been properly checked out. In this past, this was done by checking the due-date stamp in the back of each book. However, with several libraries recently installing self-checkout kiosks, we can no longer assume that each legitimately checked-out item has such a stamp. This year, Harvard Library Technology Services developed an application called Secure Exit that allows guards to scan item barcodes into a simple web interface to see if the item is checked out in Aleph. The application queries Aleph via the X-Server; checks a variety of configurable criteria (loan status, item status, patron status); and presents a simple "go / no go" message to the guard. This presentation will describe the features of the application in detail and delve into its technical underpinnings.</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2014-05-02</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>