<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>Getting the Pieces to Work Together: Implementing Alma without Implementing Primo</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Steven</mods:namePart><mods:namePart type="family">Shadle</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Jennifer</mods:namePart><mods:namePart type="family">Ward</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>The University of Washington Libraries migrated to Alma in June 2013 while keeping its WorldCat Local discovery service. It is common for a library discovery and management systems to come from different vendors, but because of the newness of Alma, few libraries have done this using Alma as the management system. This presentation will provide an overview of the rationale for this decision and will provide technical information on how to get Alma to work with the discovery service of another vendor.</mods:abstract><mods:originInfo><mods:dateIssued encoding="iso8601">2014-05-02</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>