<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>How to Make Primo Play Nicely with EAD (Encoded Archival Description) Records</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Bill</mods:namePart><mods:namePart type="family">Bodine</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Beck</mods:namePart><mods:namePart type="family">Locey</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Shelley</mods:namePart><mods:namePart type="family">Neville</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>We have been working with a custom EAD tool for the past 2 years and have done a few ELUNA presentations on this. What's new with us is that we've finally accomplished the ability to harvest EAD data using a custom file splitter which integrates EAD component level data into a Primo search result set. We built facets based on the component level data which makes it much easier to navigate all this fabulous metadata as well as linking EAD component records back to circulation in Aleph. This session discusses how we did this.</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:classification authority="lcc">Primo</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2014-04-30</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>