Enhancements to RTAC to improve performance and support patron empowerment functionality (UXPROD-2423)

[UXPROD-2758] Discovery Integrations - Expose Circulation Rules Regarding Renewal Options Created: 16/Oct/20  Updated: 22/Dec/22

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Enhancements to RTAC to improve performance and support patron empowerment functionality

Type: New Feature Priority: P3
Reporter: Kelly Drake Assignee: Khalilah Gambrell
Resolution: Unresolved Votes: 0
Labels: round_iv, rtac, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-2422 Discovery Integrations - Expose Circ... Open
Relates
relates to UXPROD-1630 Pre-Check Request Policy When Request... Closed
Epic Link: Enhancements to RTAC to improve performance and support patron empowerment functionality
Front-End Confidence factor: Low
Back End Estimator: Martin Tran
Estimation Notes and Assumptions: This feature requires lots of technical analysis and designing on the back end. There are many possible solutions, but I don't think any solution could be quick or easy to implement.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 3
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Once a patron has logged into a FOLIO-Integrated Discovery layer, the Discovery layer should have the ability to 'know' and indicate to the patron whether an item is renewable

Currently this information is not known by the discovery layer until the patron tries to activate a renewal. After placing a renewal, the patron is then denied (if the item is not eligible to be renewed) - resulting in a bad patron experience.

Current Discovery layers that are requesting this are EDS and VuFind.



 Comments   
Comment by Tod Olson [ 16/Oct/20 ]

For us, renewals are very important.

In our current system, there's a renewal counter which we use in our rules, and in our Discovery Layer, we just base the renewal options on the renewal count. It's not a perfect prediction, but it's good enough.

Maybe that could be a lightweight solution here: keep a renewal counter on the item (or loan?) and publish it in the API. The RA SIG might go for that.

Comment by Karen Newbery [ 26/Oct/20 ]

Duke has a custom app for our current discovery interface that will be updated to use FOLIO rules, and we'll need patrons to be able to renew through that app, especially if bulk renewals by staff can not be done. https://folio-org.atlassian.net/browse/CIRC-545 is marked as "won't do".

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