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

    SELF: 64 message incorrect when global charged items limit met

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

    Bug Report Form for Issue 16384-16497
    Module(s): Self Check
    Server platform(s) affected: Solaris

    Release(s) replicated in: 7.2.4-8.1
    Last version without bug (if applicable): N/A

    Expected results:
    64 message should accurately reflect patron blocks.

    Actual results:
    64 message inaccurately reflects that a patron is blocked if they have the max number of charged items for all item types charged out.

    Workflow implications: Patrons cannot renew or request additional items via selfcheck.

    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

    If the patron had reached a charged item limit set in Circulation>Policy Definitions>Patron tab, Circulation>Policy Definitions>Matrix tab, or for an individual item type in Circulation>Patron groups, the above 64 message would look like this:

    RECEIVING: 64 00020110927 113137000000000003000800000000AO|AAROODOG|AERoo Mucha|CA0001|CB0003|BLY|BHUSD|BV0.00|CQY|AU65432|AU15365|AU11234|BU|AFPatron validated successfully.|PTCC|

    The difference in the two is the patron status message for the first one shows a Y in charge privileges denied, renewal privileges denied, recall privileges denied, and hold privileges denied when it should not. Also, the first message has an AF field populated, but the second accurately does not. In the second message, the patron did not have a global charged items limit set, but instead one set at the patron rules level.

    Fixed in the selfchk server for 8.1.1.

    • Article last edited: 3/5/2015
    • Was this article helpful?