SIP Patron Status Too Many Charged and Lost Fields Never Set

Bug #1980978 reported by Jason Stephenson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Medium
Unassigned
3.11
New
Undecided
Unassigned
3.12
New
Undecided
Unassigned

Bug Description

Evergreen SIP never sets the "too many itmes charged" and "too many items lost" fields in the Patron Status field in a SIP 64 Patron Information response. This information is available to the SIP software, so we should set these fields when appropriate.

This has actually tripped up one vendor who was expecting at least one of these field to be set on a blocked patron who exceeded the lost item count.

Additionally, the too many overdue items check only looks for the PATRON_EXCEEDS_OVERDUDE_COUNT penalty. The equivalent penalty for long overdue items should be includded in this check as well.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Here's a branch with 1 commit to reslove this issue. It adds 3 constants for penalties to the Const.pm module and then checks for these in the appropriate functions of the SIP Patron module.

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

Changed in evergreen:
milestone: none → 3.10-beta
assignee: Jason Stephenson (jstephenson) → nobody
tags: added: pullrequest
Changed in evergreen:
importance: Undecided → Medium
Changed in evergreen:
assignee: nobody → Chris Sharp (chrissharp123)
Changed in evergreen:
milestone: 3.10-beta → 3.10-rc
Changed in evergreen:
milestone: 3.10-rc → 3.10.0
Galen Charlton (gmc)
Changed in evergreen:
milestone: 3.10.0 → 3.10.1
Galen Charlton (gmc)
no longer affects: evergreen/3.8
Changed in evergreen:
milestone: 3.10.1 → 3.10.2
Changed in evergreen:
milestone: 3.10.2 → none
no longer affects: evergreen/3.10
no longer affects: evergreen/3.11
no longer affects: evergreen/3.9
Changed in evergreen:
assignee: Chris Sharp (chrissharp123) → nobody
Revision history for this message
Jason Stephenson (jstephenson) wrote :

C/W MARS has been using this code in production for over a year.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.