Age Hold Protection TPAC field doesn't change when expired
Bug #1251761 reported by
David Green
This bug affects 11 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
In the TPAC, the Age Hold Protection field continues to display its interval (e.g. "6 months") after that interval has ended. This can lead staff to assume that an item is still protected when it may not be. Perhaps at the end of the interval, that display could change from the interval to something like "expired". Included a screen snippet of the TPAC as an example.
Found both while using Evergreen 2.3 and testing 2.4.
Revision history for this message
| David Green (david-green) wrote | #1 |
| Changed in evergreen: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in evergreen: | |
| status: | Triaged → Confirmed |
| tags: | added: bitesize |
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote | #2 |
Revision history for this message
| Jennifer Pringle (jpringle-u) wrote | #3 |
To post a comment you must log in.
Bob Wicksall posted some code that Pioneer Library System uses to fix this issue to the general list. A good starting point.
http://
Needs to be able to handle a few more situations to be generic.
- The "Use Active Date for Age Protection" YAOUS.
- Public message should be excluded or should be based on the Age Hold Protection Allowed Proximity settings.
- 0 = "Can only be picked up at this branch"
- 2 = "Can only be picked up in the same system"
- Or maybe the message should just be left out of a generic solution.
Josh