<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>MetaLib vs. MetaLib+: Case Studies from Université du Québec à Montréal (UQAM)and Harvard University&#13;
</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:name type="personal"><mods:namePart type="given">Alexander</mods:namePart><mods:namePart type="family">Jerabek</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract> During the implementation  of Primo version 3 that included MetaLib+, the UQAM libraries’ implementation  committee  evaluated  the utility of this new functionality.  Due to enough significant problems  and missing functionality when compared to normal MetaLib we made the decision not to implement  MetaLib+ until the bugs could be ironed out and it could be more fully developed. This presentation  will describe the use of MetaLib within the libraries’ context and explain in detail why we  could  not  implement   MetaLib+.   Harvard  University  currently   is  running  both MetaLib and MetaLib+  in parallel.  Although  we would  like  to offer  our users  a single  solution for aggregated searching  of licensed  electronic  resources,  we have  found  that  MetaLib+  lacks  certain features present  in MetaLib,  and therefore  offer both options.  This presentation  will discuss these features and their importance to our research community.</mods:abstract><mods:classification authority="lcc">MetaLib</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2013-05-03</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>