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

    Primo hold request cancellation

    • Article Type: Q&A
    • Product: Aleph
    • Product Version: 20


    How can cases where hold requests have been canceled by the patron in Primo be located?


    1. There's no z35 (Event) record for a hold-request deletion.

    2. SQL could be used to identify z37h records with a z37h_status of "A" (Active). These are requests which were either deleted by the patron or by a batch job (due, for instance, to the end-request-date being expired). But there is no indication whether such a deletion came from Primo.

    3. The $LOGDIR/www_server log can be scanned for occurrences of "DLF SERVICE: DEL-PAT-HOLD". (DLF indicates an action involving by Primo.) See example in Additional information below.

    Additional Information

    Some z37h records have a *blank* z37h_status. It's unclear just what this indicates, but such records might also be checked.

    Sample "DEL-PAT-HOLD" www_server log entry:

    ip address: 409
    request: "/P?op=del-pat-hold&patid=ETS-44090&id=ETS500000470670000300002&institution=&type=&view=&con_lng=fre&rest_uri="

    Category: Circulation (500)

    Subject: Hold requests (500)

    • Article last edited: 10/8/2013