<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>Automating MARCit! for a single-record approach</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Beth</mods:namePart><mods:namePart type="family">Brennan</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Christine</mods:namePart><mods:namePart type="family">Moulen</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Batch loading records is a huge time saver, we all know that. But how can you maintain a single record approach when your batch only describes your online holdings? Come and find out how MIT has set up out MARCit! processes: the loading, including merging with records for print; the deleting, including the untangling of print and e; and the updates, focusing on holdings updates and upgrading stub records. While we use MARCit with Aleph, we will not be focusing on Aleph-specific setup.</mods:abstract><mods:classification authority="lcc">General Topics</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2013</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>