Patron blocking by lost items and include lost as items out

Bug #1154258 reported by Kyle Tomita on 2013-03-12
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

This feature has two main parts, patron blocking by number of lost items and include lost items as items out. A group penalty threshold will be added for lost items. This will restrict patrons who have lost too many items. The inclusion of lost items as items out will be an optional setting, like claimed returned items. This will allow libraries to set what type of item statuses count toward the total items out. Lost transactions that have been closed are not included in the items out.

These features arose from a need to restrict patron access based on lost items. The librarians also wanted to be able to either include or exclude lost items from total items out. The inclusion of the display of lost items on the patron page lends itself to better reporting practices by having everything on their records show up.

Ben Shum (bshum) on 2013-03-12
Changed in evergreen:
importance: Undecided → Wishlist
status: New → Triaged
Kyle Tomita (tomitakyle) wrote :

Branch on working is user/catalystit/lp_1154258_lost_items_modifications

tags: added: pullrequest
Ben Shum (bshum) wrote :

Small suggestions for the branch:

1) The release note doc seems to be using Windows carriage returns; probably need to convert the file
2) The upgrade SQL contains an entry to insert a default patron penalty for org unit 1 (usually CONS) and set a max lost penalty of 10. This might be bad for sites performing the upgrade and suddenly finding themselves with an unexpected new default block entry.

Hi,

On Wed, Mar 13, 2013 at 8:26 PM, Ben Shum <email address hidden> wrote:
> 2) The upgrade SQL contains an entry to insert a default patron penalty for org unit 1 (usually CONS) and set a max lost penalty of 10. This might be bad for sites performing the upgrade and suddenly finding themselves with an unexpected new default block entry.

Agreed -- IMO, this must be changed before the patch can be merged.
Note that it's OK for the new default patron penalty to be present in
the seed data, it just shouldn't automatically part of the upgrade.

Kyle Tomita (tomitakyle) wrote :

I am currently working on the changes and hope to have them up later today. Thanks for the input.

tags: removed: pullrequest
Kyle Tomita (tomitakyle) wrote :

Made the changes outlined by Ben and pushed back.

Branch on working is user/catalystit/lp_1154258_lost_items_modifications

tags: added: pullrequest
Ben Shum (bshum) on 2013-03-17
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Kyle Tomita (tomitakyle) on 2013-03-29
Changed in evergreen:
assignee: Kyle Tomita (tomitakyle) → nobody
Ben Shum (bshum) on 2013-04-18
Changed in evergreen:
milestone: 2.4.0-rc → 2.5.0-alpha
Ben Shum (bshum) wrote :

Picked to master with some minor changes to the release notes to fit the new structure we're using in 2.5+.

Thanks Kyle!

Changed in evergreen:
status: Triaged → Fix Committed
Ben Shum (bshum) on 2013-11-11
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers