Long Overdue processing needs org unit settings separate from Lost Processing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 2.5.5
This report is related to the Long-overdue processing functionality using Action Triggers which was introduced in Release 2.5:
https:/
The original tech specs for the development:
http://
as well as the release notes for Release 2.5:
http://
and the Evergreen Documentation:
http://
all indicate that billing the patron as part of the automatic long overdue processing is optional, controlled by Org Unit Settings. But in reality the documentation is wrong.
In the current functionality, there are no org unit settings that apply exclusively to automatic Long Overdue processing. The org unit settings that apply are the same as those for automatic Lost processing. We would like to use both the Long Overdue processing functionality as well as automatic Lost processing functionality.
Below is a use case that could employ the Long Overdue processing in conjunction with Lost Processing:
1. Automatic Long Overdue processing would happen at approximately six weeks after the due date. This would:
- Mark circulations as Long Overdue
- Assign associated items the status of Long Overdue.
- The cost of the item would not be applied to the patron record at that time.
- The PATRON_
Marking circulations long overdue would help staff members easily distinguish between mildly overdue and severely overdue items. It would also allow blocking of some patron transactions.
2. Automatic Lost processing would happen at a much later date, for example, one year. This would:
- Mark circulations Lost
- Assign associated items the status of Lost.
- Apply the cost of the item to the patron records.
- The PATRON_
When enough time passes making it is likely that items will not be returned, the bill for the item can be applied to the patron record and the patron blocked.
Below are references to an email thread and IRC log with more background information:
http://
Changed in evergreen: | |
assignee: | nobody → Liam Whalen (whalen-ld) |
tags: | added: signedoff |
Changed in evergreen: | |
assignee: | Liam Whalen (whalen-ld) → nobody |
importance: | Undecided → Wishlist |
milestone: | none → 2.next |
status: | New → Confirmed |
tags: | added: test-writing-day-1 |
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
tags: | added: billing |
tags: | removed: pullrequest |
tags: | removed: test-writing-day-1 |
tags: |
added: circ-billing removed: billing |
tags: | added: orgunitsettings |
Changed in evergreen: | |
milestone: | 3.next → none |
To be clear, there are many settings that apply exclusively to long-overdue processing. There are 9 of them ,in fact, but it sounds like we're missing one important one:
The request as I understand it is that we need a setting which determines whether the cost of the item should be billed to the user when a circulation is marked as long-overdue? Ditto lost. I can confirm this is not configurable at the moment. Is this the sum of it?
---
For reference, OpenILS: :Application: :Cat::AssetComm on::set_ item_long_ overdue / set_item_lost