Loans (UXPROD-788)

[UXPROD-3651] Ability to batch renew loans across multiple patrons/library users Created: 28/Apr/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: bulk-edit-loans, enettifee-reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-868 Bulk Edit In Progress
relates to UXPROD-2375 Automatic renewals Draft
Epic Link: Loans
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

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 - UXPROD-2375 Draft - 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 In Progress - to reflect the fact that development of this may happen in that context.

Links to additional info

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.


 Comments   
Comment by Thomas Trutt [ 14/Jul/22 ]

If the API endpoint for the function was also available this would be a helpful function for discovery layers. Maybe the same function could be implemented in the user loan view to speed up renewals there as well. 

Comment by Erin Nettifee [ 10/Aug/22 ]

I believe pretty strongly that the bulk edit app should not handle things that are really bulk actions like this Magda Zacharska - down that road lies madness.

Renewing loans isn't as simple as changing a due date on the record, you have to use the circulation rules, you have to be able to handle errors that appear. It's not clean and it really has the potential to make the bulk edit app much, much, much too complicated.

Comment by Thomas Trutt [ 26/Aug/22 ]

Should this then be moved form Bulk edit over to part of one of the circulation modules? I feel this is a need not only for institutions that want to do bulk renewals from semester to semester but would also be useful for the current frontend and edge APIs to speed up renewal times. 

Comment by Erin Nettifee [ 23/Sep/22 ]

I am talking to the Circ POs about whether this should be part of the bulk edit app in addition to changing due dates.

Comment by Thomas Trutt [ 13/Mar/23 ]

Erin Nettifee just looping around. Any word on if this will be in Bulk edit or should remain separate. I Still feel it is needed, but agree with your original concerns of this being in Bulk edit. 

Comment by Erin Nettifee [ 13/Mar/23 ]

There was not a firm consensus. The one piece of feedback was a sense that the project needed to be able to do bulk renewals in the way that UChicago has built outside of FOLIO but no one else felt as strongly as me that Bulk Edit shouldn't be the tool to do it. The issue I think is that if Bulk Edit repurposes the existing 1-1 APIs than we introduce additional performance concerns. We really need the functionality for bulk renewal APIs.

Comment by Thomas Trutt [ 13/Mar/23 ]

In general i am on the same page as you when it comes to any circulation tasks is Bulk edit. I'm worried on multiple leaves; performance issues, not following circ rules / bypassing policies, etc. Im not framiler with how UChicago is doing this. 

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