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

    p_cir_06: "DELETE-ACTION A" fails to put item in-transit to pickup library

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 19.01

    Description:
    In running p_cir_06, when Delete Action “A” (“Delete Current Holds and Notify Next Requester”) is specified and the current hold is expired (“lapsed”) and the next requestor’s request has a pickup library different than the library the book is in, rather than sending the book in-transit to the pickup library, it produces a hold request slip.

    Resolution:
    Short answer: p_cir_06 doesn't handle this case properly. If hold requests can specify a different library as the pickup library, then specify Delete Action “Y” (“Delete Current Holds”) in running p_cir_06 *not* Delete Action “A”. The p_cir_06 hold shelf report will list this item as a stale hold which has been deleted, and then when you discharge the item, it will (correctly) be placed in transit to Library B. When it arrives at Library B and is discharged, the item available notice will be sent to the (next) patron and the hold slip will be produced.

    Long answer:

    These are the parameters site was using previously:

    setenv p_active_library "ABC50"
    setenv p_output_file "pred.holdreport.01"
    setenv p_letter_name "pred.holdletters.01"
    setenv p_sub_library ""
    setenv p_pickup_location "PRED"
    setenv p_item_status ""
    setenv p_update_rec "A"
    setenv p_print_letter "Y"
    setenv p_date_x "20100221"
    setenv p_sort_key "NM"
    setenv p_date_filter_x "02"
    setenv p_letter_format_x "00"
    setenv p_form_no "01"
    setenv p_req_letter_fmt_x "00"

    As a workaround to the problem, they have changed p_update_rec to "Y"….

    Here are the results of our test using delete action Y - delete stale hold only.

    The process works properly using Y. The stale hold is removed by p-cir06; and the item when discharged from the hold shelf tells the staff member that the item is needed at another library (Library B), and then prints the in-transit slip. When the item is discharged after arrival at Library B, the email is sent to the user and a hold shelf slip printed.

    So the only problem is that the hold shelf report isn't at all helpful indicating the pickup library. I realize that we added this column to the report, but looking at the raw XML, the Z37 in the report is the original one, not the new one:

    From the report - sequence #2:

    <z37-doc-number>002679497</z37-doc-number>
    <z37-item-sequence>000010</z37-item-sequence>
    <z37-sequence>0002</z37-sequence>
    <z37-id>000426858</z37-id>
    <z37-status>S</z37-status>
    <z37-expand>N</z37-expand>
    <z37-priority>30</z37-priority>
    <z37-open-date>November 30 2009</z37-open-date>
    <z37-open-hour>14:43</z37-open-hour>
    <z37-request-date>November 30 2009</z37-request-date>
    <z37-end-request-date>January 30 2011</z37-end-request-date>
    <z37-hold-date>February 16 2010</z37-hold-date>
    <z37-letter-status>02</z37-letter-status>
    <z37-letter-date>February 16 2010</z37-letter-date>
    <z37-alpha>L</z37-alpha>
    <z37-author />
    <z37-title />
    <z37-pages />
    <z37-note-1 />
    <z37-note-2 />
    <z37-print-status>P</z37-print-status>
    <z37-requester-id />
    <z37-cataloger-name />
    <z37-cataloger-ip />
    <z37-hold-sequence>000</z37-hold-sequence>
    <z37-pickup-location>Library A</z37-pickup-location>

    The "new" hold:
    01 z37_hold \
    02 z37_rec_key \
    03 doc_number ..................002679497
    03 item_sequence ...............000010
    03 sequence ....................0003
    02 z37_id ........................0000062448
    02 z37_status ....................W
    02 z37_expand ....................Y
    02 z37_priority ..................30
    02 z37_open_date .................20100216
    02 z37_open_hour .................1326
    02 z37_request_date ..............20100216
    02 z37_end_request_date ..........20100416
    02 z37_hold_date .................00000000
    02 z37_letter_status .............
    02 z37_letter_date ...............00000000
    02 z37_alpha .....................L
    02 z37_author ....................
    02 z37_title .....................
    02 z37_pages .....................
    02 z37_note_1 ....................
    02 z37_note_2 ....................
    02 z37_print_status ..............
    02 z37_requester_id ..............
    02 z37_cataloger_name ............JONES
    02 z37_cataloger_ip ..............REDP
    02 z37_hold_sequence .............000
    02 z37_pickup_location ...........LIBB

    It would be great if, along with the next requester name and ID, the pickup library for the next requestor could be added to this report. So that is our request out of all of this!

    Jerry replied as follows:

    Two different z37’s are involved here: the old (stale) request and the new (now-current) request. To differentiate them, p_cir_06 prefixes the data coming from the new request with “NEXT-REQUESTER-”.

    Two such pieces are: NEXT-REQUESTER-ID and NEXT-REQUESTER-NAME.

    The other z37 fields which are included in the hold-shelf-report.xsl form are all coming from the old request.

    It’s possible that a “NEXT-REQUESTER-PICKUP-LOCATION” could be added, but it would seem that that would be an enhancement request.

    • Article last edited: 10/8/2013