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

Description:
We notice that some photocopy requests are immediately determined by the system to be "Waiting" requests, and we are not sure why. On our production system I just placed a request on the following item:

ADM - 850511
Barcode - 39029030858843

It sent me a Waiting letter notice but I cannot figure out why the request wasn't considered to be available. The item is not on loan, in transit, or Misshelved. I suspect there would be many more like this in the system.

Can you please advise why this request was handled as Waiting?

Resolution:
I was *not* able to reproduce this problem on our server. Below is the usm50 tab_photo_request. Please change your values to these:

! 1 2 3
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
PRE check_photo_request_a
PRE check_photo_request_b
!*
POST check_photo_request_c
!POST check_photo_request_f
POST check_photo_request_r
!*
CIRC check_photo_request_a
CIRC check_photo_request_b
CIRC check_photo_request_c
CIRC check_photo_request_r
!*
INFO check_photo_request_k
INFO check_photo_request_k1
INFO check_photo_request_v

<end suggested tab_photo_request entries>


Note: Before commenting out:

POST check_photo_request_f

I was getting “Patron has already placed a photocopy for this item” trying to place a hold on different item for the same title. But after commenting it out, I was able to place a hold on the other volume -- and it has a z38_status of "A".

[From site:] I changed the values and tested another request. Previously it would have gone to Waiting after running p-cir-22 because there was already an open request for the title, but now it went to Active.

• Article last edited: 10/8/2013