Ability to batch renew loans across multiple patrons/library users
Description
Priority
Fix versions
Development Team
Assignee
Solution Architect
Parent
Parent Field Value
Parent Status
has to be done after
relates to
Checklist
hideTestRail: Results
Activity

Demian Katz April 30, 2024 at 2:27 PM
All sorted out; I’ve opened https://folio-org.atlassian.net/browse/UXPROD-4805 to continue the conversation. Please let me know if there’s anything I could have done better in my ticket creation so I can take it into account next time.

Demian Katz April 30, 2024 at 2:00 PM
Thanks, @Thomas Trutt, I’ll try that!
Thomas Trutt April 30, 2024 at 1:56 PM
@Demian Katz if you Peter Murray in the slack channel #folio-atlassian-support he should be able to get you set up with the correct permissions.

Demian Katz April 30, 2024 at 1:50 PM
@Thomas Trutt, just following up to see how I can help move this forward. Would it be helpful for me to share a proposed ticket write-up here? Otherwise, can somebody please give me UXPROD ticket permission so I can open it myself? (And apologies if there’s another way forward that I’m overlooking ).

Demian Katz April 17, 2024 at 12:30 PM
@Thomas Trutt, I apparently do not have permission to create UXPROD tickets – I get a “You cannot create issues in this project” message. If there’s a way to give me permission, I’m happy to open the ticket. If it would be easier, I’d also be happy to share some proposed ticket text here, and somebody else can copy and paste it into an actual ticket. Please let me know what makes the most sense!
Details
Details
Reporter

Current situation or problem:
Libraries need the ability to batch renew large numbers of loans at a time, including loans for more than one user at a time.
This is different than desired functionality for automatic renewal - https://folio-org.atlassian.net/browse/UXPROD-2375#icft=UXPROD-2375 - where the renewal would occur for the loan automatically if it was eligible to be renewed. Batch renewal assumes staff intervention to search for the loans they want to renew, and then execute a process to renew them.
This is also different than functionality for a bulk change of due date (supported in scripting shared in the community) in that some libraries would want to do a batch renewal rather than change due date so that items with limited renewals fail to get a new due date, as expected according to the loan policy.
In scope
Ability to search for loans based on defined criteria and then execute a renewal request for each loan returned in the search.
A UI that returns error messages for loans that were not able to be renewed in a usable fashion, so that staff can view loans that did not renew and take action as appropriate.
Out of scope
TBD
Use case(s)
At the end of an academic year, a library wants to renew all the items on loan to faculty in order to prevent them from receiving overdue notices and having items go lost.
A library has students going on an extended research trip and wants to renew their loans for them in one batch since they know those patrons won't be able to check their email and renew items themselves.
A library wishes to do bulk renewal of items on loan because a popular library / book return location will be unexpectedly closed for a period of time.
Proposed solution/stories
Batch or bulk renewal is a use case for the Bulk Edit app - https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases - and so this may be appropriate to address through bulk edit, as opposed to functionality in the Users or Checkout app. I am going to link this to the Loans epic with Vega as the dev team, but relate it to the UXPROD for Bulk Edit - UXPROD-868 - to reflect the fact that development of this may happen in that context.
Links to additional info
@(OLD ACCOUNT) Erin Nettifee added this feature to capture the use case for bulk renewals, which is something that Duke has had reason to have to do and continue to do going forward in FOLIO for some patron groups.
Questions
Uncertain about how override behavior would work in this functionality.