Why does check_1_b not allow renewal in OPAC?
- Product: Aleph
- Product Version: 21,22,23
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Description
The patron has a local block '06' which should allow renewal, but the renewal is nevertheless blocked in OPAC. Why?
./xxx50/tab/tab_delinq.lng
! 2 3 4 5 6
! abcdefghi
!!-!-!!!!!-!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
06 2 ##### NNNNNN N L all blocked, Renewal allowed
./xxx50/tab/tab_check_circ
RENEW-WWW check_circ_1_a
RENEW-WWW check_circ_1_b
RENEW-WWW check_circ_1_c_a
RENEW-WWW check_circ_1_c_b
RENEW-WWW check_circ_1_e
RENEW-WWW check_circ_1_f
RENEW-WWW check_circ_2_a
RENEW-WWW check_circ_2_b
Resolution
Remove check_circ_1_b from ./xxx50/tab/tab_check_circ.
If you would like to check the renew permission of the patron, use check_circ_2_b instead.
Additional Information
The header of ./xxx50/tab/tab_check_circ has the following explanation:
! 1_b: patron blocks
! Z305
! Warning according to parameters as set in tab_delinq.lng
! Note that Block Code "00" (col. 1 of tab_delinq.lng)
! - displays no warning.
That means, that if check 1_b is activated, the system will block any activity for patrons with local blocks other than '00'.
Check 1_b does not take individual setup of table tab_delinq.lng into account.
Other checks for local permissions, e.g. 2_a or 2_b allow the check of individual permissions set in tab_delinq.lng.
- Article last edited: 07-Mar-2017