Skip to main content
ExLibris

  • Subscribe by RSS
    • Back
    Voyager
    Ex Libris Knowledge Center

    Basic overview of catalog record batch deletion and suppression in Voyager

    1. Last updated
    2. Save as PDF
    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    Basic overview of batch deleting and suppressing records in Voyager cataloging.

    Answer

    All record deletions occur in the following basic order: item records (if present) – empty holdings records (if present) – empty bibliographic records. Voyager does not allow holdings with items still attached to be deleted. Similarly, Voyager does not allow bibliographic records with holdings still attached to be deleted. This safeguard protects other items or holdings attached within the record hierarchy from accidental deletion. When configuring batch tools for a delete project, be cautious not to override this protection. Configure the tools to run on data following this basic delete order so that the batch tool is starting from the most specific record type (such as item IDs or barcodes if items are present).

    When a bibliographic record is suppressed with the “Suppress from OPAC” flag on its MARC tab, the bibliographic record plus any attached holdings are also suppressed from view in the the OPAC. When a holdings record is suppressed with the “Suppress from OPAC” flag on its MARC tab, only the specific holding is removed from view in the OPAC. The bibliographic record associated with the suppressed holding plus any other holdings records attached to the bibliographic record remain visible in the OPAC.

    Voyager will block records from being deleted if linked purchase orders are present, items are on reserve, or if items have active circulation transactions. Additional steps may be taken to identify these scenarios ahead of a batch delete:

    • Items that have been requested, checked out or items with outstanding fines/fees are examples of active circulation transactions. These items cannot be deleted until the transaction concludes.
    • Items on reserve cannot be deleted during a batch delete. If possible, remove items from the reserves lists ahead of time.
    • Bibliographic records with linked purchase orders (POs) cannot be deleted during a batch delete, but if processed by a batch delete tool, their item records and sometimes holdings records can be unintentionally deleted. It is best to identify and manage linked POs ahead of time.