• Article Type: General
• Product: Voyager
• Product Version: 8.1.1

Description:
Bug Report Form for Issue 16384-16801

Module(s): Self check
Server platform(s) affected: Solaris/all
PC OS (if applicable): n/a
Browser & version (if applicable): n/a
Release(s): 7.2.4-8.1.0
Last version without bug (if applicable): n/a

Expected results: Even if a patron is blocked from any activity, self check should send the accurate counts for charged items, overdue items, holds/recalls and items ready for pickup.

Actual results: If a patron hits the Global Max Items Charged limit, the 64 message is sent with all the counts set to 0, regardless of whether the patron has counts of greater than 0.

Workflow implications: If the self check machine in use is capable of displaying these counts, patrons in this scenario see incorrect information.

Replication steps:
1. Set SysAdmin>Circulation>Patron Groups>Global Borrowed Item Limits tab> "Charged Items limit for all item types" with a value, we’ll use 3 for an example.
2. In Circulation, charge 3 items to a patron with the same patron group from step 1.
3. Via Self Check, send a 63 message to view this patron’s record and get the below 64 message in response:

BEGIN Login
SENDING: 9300|CNself|COcheck|CPSELF
RECEIVING: 941
SENDING: 9900802.00
RECEIVING: 98YYYYYN99800320110929 1125472.00AO|BXYYYYYNYYYNYNNNYN|
END Login

BEGIN Stanza Loop
SENDING: 6300120110927 121515 Y AO|AAROODOG|AC|AD|BP|BQ|
RECEIVING: 64YYYY Y 00020110929 112547000000000000000000000000AO|AAROODOG|AERoo Mucha|BLY|BHUSD|BV0.00|CQN|AU33939|AU33982|AU99839|BU|AFPatron is blocked.|AFPatron has reached the charged item limit|AFPatron barcode valid(active)|PTCC|
END Stanza Loop

Resolution:
Fixed in the selfchk server for 8.1.1.

• Article last edited: 3/5/2015