<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>What to Do With OPAC-Era E-Resource Records in a Primo World?</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Joan</mods:namePart><mods:namePart type="family">Kolarik</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Have you fully transitioned from OPAC to Primo? Is your catalog full of e-books and other e-resources from different sources which date from before the time of Primo Central Index? Are they duplicated by Primo Central? This is a challenge at any library. When you're part of a large consortium and there are multiple copies of those e-resource records in the catalog, the problem is compounded. This presentation will discuss techniques and strategies used at CUNY to handle e-resource records, with a goal of improving Primo results (while keeping OPAC fans happy a little longer).&#13;
* What metadata goes into the Primo record: Aleph vs PCI?&#13;
* Will an Aleph record provide a View Online tab?&#13;
* Conditional proxying of Aleph 856 links for Primo&#13;
* Finding broken links in the Aleph 856 field: GUI-based and batch&#13;
* Duplicate e-resource suppression: Which record to use? PCI, Aleph, both?&#13;
* In PCI, not in PCI: Getting availability right</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:classification authority="lcc">MetaLib</mods:classification><mods:classification authority="lcc">Primo</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2016-05-04</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>