Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. Outstanding hold/recall prevents deletion of bib record

    Outstanding hold/recall prevents deletion of bib record

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Question
    2. Answer
    3. Additional Information
    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    Unable to delete bib record because of outstanding hold/recall.

    Receive error: "Unable to delete bibliographic record. An outstanding hold/recall exists" when attempting to delete a bib record.

    Answer

    Voyager will allow the deletion of both an item and a MFHD, even if there is an outstanding hold.  However, it will not allow the deletion of the bib until the on hold item is charged to the patron, the hold expires, or is canceled and archived.

    To delete the bib, staff will need to wait until the on hold item is charged to the patron, the hold expires, or is canceled and archived.

    Additional Information

    The following Prepackaged Reports Access query can help determine the date after which you will be able to delete the bib record. It prompts for a bib ID and may help to determine the date the bib will be available for deletion.

    SELECT HOLD_RECALL.BIB_ID,
    IIf([VOYAGER_DATABASES].[DB_NAME] Is Null,"Local Bib",
    [VOYAGER_DATABASES].[DB_NAME]) AS HoldingDBName,
    IIf([HOLD_RECALL].[HOLD_RECALL_TYPE]="H","Hold",
    IIf([HOLD_RECALL].[HOLD_RECALL_TYPE]="R","Recall","Unknown/Other"))
    AS HoldRecallType, HOLD_RECALL.CREATE_DATE, HOLD_RECALL.CREATE_OPID,
    HOLD_RECALL.AVAILABLE_NOTICE_DATE,
    IIf([HOLD_RECALL].[AVAILABLE_NOTICE_DATE] Is Null
    And [VOYAGER_DATABASES].[DB_NAME] Is Not Null,
    "TBD: The hold expire date will be updated when the item arrives at your library" &  
    " and is discharged to put on the hold shelf for the patron.",
    IIf([HOLD_RECALL].[AVAILABLE_NOTICE_DATE] Is Null
    And [VOYAGER_DATABASES].[DB_NAME] Is Null,
    "TBD: The hold expire date will be updated when the item" &  
    " is discharged to put on the hold shelf for the patron.",
    [HOLD_RECALL].[EXPIRE_DATE] &
    ", OR, whenever the item is charged to the patron's account."))
    AS HoldClearedOn
    FROM HOLD_RECALL LEFT JOIN VOYAGER_DATABASES
    ON HOLD_RECALL.HOLDING_DB_ID = VOYAGER_DATABASES.DB_ID
    WHERE (((HOLD_RECALL.BIB_ID)=[Enter bib ID:]));

     

    Constructing custom SQL queries by request and troubleshooting unexpected results from customer-created SQL queries falls outside the scope of Support. The above has been posted for informational purposes.  Voyager-L and Developer Network are useful resources for finding helpful custom SQL or obtaining assistance from peers in troubleshooting custom queries.

     


    • Article last edited: 04-Dec-2020
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Why are all emails from hosted Voyager envrionments sent from 'exlibrisgroup.com'
      • Overcommit/expend blocks show incorrect values
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved