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

Description:
We created a library user to allow holds on fast cataloged items. We defined this user ID in tab100 FAST-CAT-HOLD-ID. We tested this out on our development server and found out that it works, but not quite the way it says it should.

The documentation says that "the request will become active at a later date so as not to interfere with the loan process". We found this to be not true--the hold caused the loan to need to have the override done, so the loan could proceed, because it detected the hold on the item immediately.

Our libraries would prefer the loan to be able to proceed without needing an override done, which is how we are interpreting the documentation. Is the documentation wrong? Or is there something else that is causing this that we don't have set up correctly? We wouldn't want to not have the circ check that looks for holds at time of loan, because we normally want that check.

Resolution:
The following pc_server_defaults value controls this:

setenv circ_cataloger_request_date nnn

[where "nnn" is the number of days you want to add to today's date in creating the z37_request_date for CATALOGER (or FAST-CAT-HOLD-ID) holds].

For instance, if you want the hold request to be in effect the day after the hold is placed, you would specify:

setenv circ_cataloger_request_date 001