<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>Preparations for Using p-manage-33 for Batch Record Deletion</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Steve</mods:namePart><mods:namePart type="family">Thomas</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract> Steve R. Thomas, Local Systems Development Coordinator, University of Tennessee, Knoxville.&#13;
&#13;
The ALEPH cataloging client provides a utility (p-manage-33) that will process a list of bibliographic document numbers and delete those bib records as well as all related admin, holdings, and item records. But, how is this input list to be prepared? This presentation outlines a way to determine, in a semi-automated fashion, which items within a given collection may be deleted in batch mode and which must be examined individually because of their relationships with items in other collections. </mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2008-07-31</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>