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

[UXPROD-2422]  Discovery Integrations - Expose Circulation Rules Regarding Requests Created: 06/May/20  Updated: 06/Dec/23

Status: Open
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
is cloned by UXPROD-2758 Discovery Integrations - Expose Circu... Draft
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 Estimate: XXL < 30 days
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): R2
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: Mainz (Full TBD): R1
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R3

 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 or not specific items are, or are not requestable (Hold, Page, or Recall)

Currently this information is not known by the discovery layer until the patron places the request. After placing the request, the patron is then denied - resulting in a bad patron experience.

Current Discovery layers that are requesting this are EDS, VuFind, and Blacklight (Duke/Cornell).



 Comments   
Comment by Kelly Drake [ 07/May/20 ]

This might be related to this: https://folio-org.atlassian.net/browse/UXPROD-1630?

Comment by Marie Widigson [ 11/May/20 ]

I think that this is a very interesting feature. More important for us, that could also partly serve as a workaround for this, is to display the item loan types in discovery layer. This could give the user a clue to why something is not requestable. See https://folio-org.atlassian.net/browse/EDGRTAC-17 & https://folio-org.atlassian.net/browse/MODRTAC-22 (description in https://folio-org.atlassian.net/browse/CHAL-117)

Comment by Tod Olson [ 09/Oct/20 ]

For us, the biggest reason would be to support renewals in our MyAccount feature, to know that something is or is not renewable before we offer the option to the user.

Comment by Khalilah Gambrell [ 16/Oct/20 ]

Tod Olson, Brooks Travis, Marie Widigson, Kelly Drake, and Anya, I split this feature. This feature will focus on providing a response that indicates a title can be requested. UXPROD-2758 Draft will focus on providing a response that indicates if a title can be renewed. Can you re-rank this feature and UXPROD-2758 Draft ?

Comment by Tod Olson [ 16/Oct/20 ]

Can there be a lightweight solution, such as exposing the item type or loan type, and let the discovery layer decide base on that?
Not perfect, but could be good enough.

Comment by Holly Mistlebauer [ 26/Feb/21 ]

Loan type has been exposed.

Comment by Kelly Drake [ 26/Feb/21 ]

Khalilah Gambrell.  If this were to be developed on the back end, how much more work would be required to get the information in rtac?

Comment by Holly Mistlebauer [ 03/Mar/21 ]

Update:  This feature is planned to be started in Juniper, but cannot be finished until Kiwi due to the limited back-end capacity of the Prokopovych (formerly Core: Functional) team.  This feature will be part of the pointing process, so its priority is subject to change.

Comment by Holly Mistlebauer [ 11/Mar/21 ]

@Khalilah Gambrell:  Hi!  Will you be writing the user stories for this feature?  My team is slated to start this feature in Juniper.  Thanks...

Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ]

Khalilah Gambrell This was assigned to Prokopovych. Should it be assigned to Vega now? See UXPROD-2758 Draft

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