Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Retrieval Service in preparation for p_cir_77

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

    Description:
    We recently had an Ex Libris web training session on deleting patrons in a multi-ADM environment. The service covered, cir-77 (Update Patron Records) works very well for pre-deleting and deleting patrons, while blocking deletion for patrons with liabilities.

    However, using cir-77 currently requires either updating each patron record individually, or using the PLIF to put "DELETE" in Global Note 2. For a small college with a few hundred patrons to delete this is not a great problem, but for a large university, which currently has about 18.000 patrons to delete, this is a difficult task. Many of our patrons are not loaded from another system via the PLIF, but are registered by hand.

    It would be very useful to have a service for patrons like p-ret-adm-01 is for items, which would allow us to create a file of patrons selected by patron status and expiration date, and another such as manage-62 to update those records. This would have uses beyond updating Global Note 2, such as changing patron status or expiration date for classes of patrons.

    Resolution:
    We may want to create an enhancement request requesting the kind of jobs you describe, but the update of the Global Note 2 to a value of "DELETE" where the Local z305_bor_status = "nn" and the z305_expiry_date is less than "yyyymmdd" can be accomplished with the following SQL....

    > s+ abc50

    SQL-ABC50> update sys00.z303 set Z303_note_2 = 'DELETE' where z303_rec_key in (select substr(z305_rec_key,1,17) from z305 where z305_bor_status = 'nn' and z305_expiry_date < 'yyyymmdd');

    {You would substitute the relevant Patron status for "nn" and the appropriate expiration date for "yyyymmdd" -- and your $usr_library for "sys00".}

    Be sure to back up the $usr_library z303 table using p_file_03 before running such SQL.


    • Article last edited: 10/8/2013