<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>Virtualizing your ILS client</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Anthony</mods:namePart><mods:namePart type="family">Dellureficio</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Zach</mods:namePart><mods:namePart type="family">Stephens</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>As libraries shift more towards hosted and SaS (Software as Service) ILS applications, there is an increasing expectation that the clients will behave like web-based software. At The New School we still work with primarily self-hosted ILS components (centered around Aleph), however we have begun using AppsAnywhere to create virtualized clients for our self-hosted applications. In our presentation, we will talk about what a virtualized client is, how it behaves differently from a locally installed client, and generally investigate the benefits and challenges of virtualized clients.</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:classification authority="lcc">General Topics</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2016-10-26</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>