Requests
(UXPROD-790)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Cate Boerema (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Requests |
| Development Team: | Prokopovych |
| Description |
|
DRAFT - DO NOT RANK. STILL DISCUSSING WHETHER WE NEED THIS OR NOT Current situation or problem: We have libraries that want to look at recalls according to who is receiving the recall, rather than who is requesting the recall, and right now there is not way to connect a recall to the exact loan that was active when the request was placed. We have the item id in the request, but of course an item has many loans, so we’re left filtering the loans by the date of the request. I wanted to check with requests experts to make sure we’re not missing something about the data model. In scope Out of scope Use case(s) Many libraries run reports on how many recalls are received by different user groups. Having a book recalled is a pretty negative experience, and reporting on this is common and used to make purchasing decisions, decisions about recall policy, decisions about how to communicate the differences between recall and ILL, etc. So this data is needed for reporting. The original report request is
Use case provided by Angela Zoss Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Cate Boerema (Inactive) [ 25/Nov/20 ] |
|
Decided we could use the "dueDateChangeByRecall" flag. This flag is set when a recall is first applied to a loan and it’s the presence of this flag that determines things like whether the due date is changed, whether a patron notice goes out etc. The logic of the flag is explained in this JIRA, if you are interested: https://folio-org.atlassian.net/browse/CIRC-1003 |