Long-overdue processing
Bug #1169193 reported by
Bill Erickson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Add support to Evergreen for automated processing of long-overdue circulations. Processing will be very similar to automated LOST processing. It is effectively a step between overdue and LOST and is particularly useful for libraries that reserve LOST for items which the patron has declared lost, i.e. where automated LOST processing makes no sense.
See tech specs at http://
Changed in evergreen: | |
status: | New → Triaged |
Changed in evergreen: | |
milestone: | 2.5.0-m1 → 2.5.0-m2 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
assignee: | nobody → Jason Stephenson (jstephenson) |
status: | Triaged → In Progress |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Changed in evergreen: | |
assignee: | Jason Stephenson (jstephenson) → nobody |
To post a comment you must log in.
Branch pushed to working => user/berick/ lp1169193- long-overdue -- with release notes, etc.
There was no significant departure from the tech specs linked above, so they (and the included release notes) still provide an accurate summary of what the code is doing.