Requests (UXPROD-790)

[UXPROD-2827] DRAFT: Store Recalls Associated with Borrower Created: 23/Nov/20  Updated: 07/Dec/20  Resolved: 25/Nov/20

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 REP-202 Open , and the rankings are at UXPROD-2017 Blocked . It’s more of an annual report than a daily operational report, but does have R2 rankings from several institutions.

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

Generated at Fri Feb 09 00:27:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.