• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
We recently tested the new items deletion features available in Version 19. This feature in p-item-11 allows the user to not only delete items, but the corresponding holdings records, and BIB records as well, provided that no other items or holdings are attached. This feature allows us to delete items and holdings for one ADM while not affecting the items and holdings for other ADMs; something that is important in our single-BIB, multi-ADM environment.

In testing, we found that the process worked as expected in all instances except one. If there are multiple items attached to a holdings record, and we want to delete some but not all of the item records, the system deletes the item records AND the holdings record even though other items are still attached to it. After the process is finished the item records that remain are still linked to the deleted holdings record, which causes problems.

Aleph needs to recognize when other item records are attached to the holdings record and not delete it. In a manual process, a user cannot delete a holdings record without deleting or unlinking the corresponding items. This batch process needs to do the same.

Resolution:
With the following lines active in the abc60 check_doc:

BATCH-DELETE check_doc_delete_lkr
BATCH-DELETE check_doc_delete_item

and with the following lines commented out:

!BATCH-DELETE check_doc_delete_copies
!BATCH-DELETE check_doc_delete_loan
!BATCH-DELETE check_doc_delete_hold

p_item_11 works as desired.

[Note: If you have just a single 852, for just a single library, in your HOL records, the preceding should not be an issue.]

• Article last edited: 10/8/2013