Comment 3 for bug 1980978

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

Tested this feature, and it seems to work correctly.

Rebased to master and working signoff branch at user/stompro/lp1980978-sip-patron-status-improvement-signoff

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1980978-sip-patron-status-improvement-signoff

I added a release note tag to the commit message also.

Testing Notes:

01234567890123
YYYY YY YYY <-- All related penalties set
YYYY Y YYY <-- Removed Exceeds checkout count (05 unset)
YYYY Y YY <-- Removed EXCEEDS_LOST_COUNT (09 unset)
YYYY Y YY <-- Removed Patron Exceeds Lost , but still has Patron Exceeds Longoverdue (No change)
YYYY YY <-- Removed Patron Exceeds LONGOVERDUE Count (06 unset)
YYYY Y YY <-- Applied PATRON_EXCEEDS_CHECKOUT_COUNT (05 set)
YYYY Y YYY <-- Applied PATRON_EXCEEDS_LOST_COUNT (9
YYYY YY YYY <-- Applied PATRON_EXCEEDS_LONGOVERDUE_COUNT

patron status 14-char, fixed-length field. This field is described in the preliminary NISO standard Z39.70-
199x. A Y in any position indicates that the condition is true. A blank (code $20) in this position
means that this condition is not true. For example, the first position of this field corresponds to
"charge privileges denied" and must therefore contain a code $20 if this patron’s privileges are
authorized.
Position Definition
0 charge privileges denied
1 renewal privileges denied
2 recall privileges denied
3 hold privileges denied
4 card reported lost
5 too many items charged
6 too many items overdue
7 too many renewals
8 too many claims of items returned
9 too many items lost
10 excessive outstanding fines
11 excessive outstanding fees
12 recall overdue
13 too many items billed