Requests (UXPROD-790)

[UXPROD-2649] Request: Allow Override of Request Policy Prevented Request Created: 10/Sep/20  Updated: 28/Nov/23

Status: Analysis Complete
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: Requests

Type: New Feature Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: requests, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UIREQ-525 Permission escalation for request pol... Draft
Defines
is defined by CIRC-1105 Backend: Enable Request Override via ... Open
is defined by UIREQ-593 Create Override Denied Request Permis... Open
is defined by UIREQ-594 Present Option to Override Denied Req... Open
is defined by UIREQ-592 Present Staff the Option to Override ... Open
is defined by UICIRCLOG-56 Add "Created through override" Circ A... Closed
Relates
relates to UXPROD-2645 Permission escalation for override Draft
relates to UXPROD-2689 Enable Request Policy to Determine Al... Closed
relates to UXPROD-2690 Prevent Local Page Requests Draft
relates to UXPROD-2694 Request: Allow Override of Prevented ... Blocked
Release: Not Scheduled
Epic Link: Requests
PO Rank: 74
PO Ranking Note: 2021-03-30 - BT: Updating to calc rank.
2021-03-03 - BT: Updating PO rank to calculated rank.
2021-02-08 - BT: Updating PO rank to new calculated total rank based on new SU21 implementer R1/R2 rankings.
2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R3
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R2
Rank: Mainz (Full TBD): R1
Rank: MI State-Lib of MI (Sum 2021): R1
Rank: MO State (MVP June 2020): R1
Rank: St. Michael's College (Sum 2021): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem: Request policies can prevent requests of certain types being created by certain patron groups. There is currently no way to override this.

In scope: Override request policy that says an items is not requestable by a patron. Overrides should be flagged as such for reporting/audit trail purposes, and staff may want to enter comments about why the item had an override (assuming this affects loan structure).

Out of scope:

  • Permission escalation for overriding when you don't have permission to do so - see UXPROD-2645 Draft
  • Displaying pre-filtered view of the circ log on the Request record is out of scope for this. See UXPROD-1056 Draft
  • Distinguishing between title-level and item-level requests (e.g., allowing override for one type but not the other.)

Use case(s):

  • Scenario: Request policies are configured to disallow holds to be placed by patrons. A patron contacts the library requesting to be notified when an item is available for checkout, and asks that the item be held for pickup. Currently, there is no way to place this hold on behalf of the patron (eg. “Request not allowed for this item/patron combination”). Staff (with proper permissions) should be able to override this, similar to loan policy overrides in Checkout.
  • Scenario 2: Request policies are configured to disallow recalls by patrons. A patron contacts the library with an urgent request for an item that has been checked out by the same faculty member for three years, so the staff decides it is appropriate to allow a recall of the item for the requesting patron. Current functionality does not permit this recall to be created for the requesting patron (eg. “Request not allowed for this item/patron combination”). Staff (with proper permissions) should be able to override this, similar to loan policy overrides in Checkout.
  • Scenario 3: Request policies are configured to disallow pages by a patron for an item. A patron contacts the library to request an item to be paged. The staff member determines that the library will retrieve the item from the stacks for the patron due to a temporary accessibility accommodation. Currently, creating this page request would not be allowed. The staff member (with appropriate permissions) should able to override this, similar to loan policy overrides at checkout.

Proposed solution/stories (optional):
Solution discussed with RA SIG on 2020-10-12: https://folio-org.atlassian.net/wiki/display/RA/2020-10-12+Resource+Access+Meeting+Notes Stories:

  • Requests App: Support override of prevented request
    • Should display when request is prevented
    • Should include the ability to add a comment
  • Circ Log: Indicate that a request was created with override
  • Permission: Add permission for request override

Links to additional information:

Questions/Comments:



 Comments   
Comment by Brooks Travis [ 08/Feb/21 ]

Marc Johnson We need some estimates on this (backend and frontend), and I'm not sure enough what this entails on the backend to try and estimate that part myself. Should it be similar to what was required for loans, or are there likely to be significant differences?

Comment by Marc Johnson [ 09/Feb/21 ]

Brooks Travis

We need some estimates on this (backend and frontend), and I'm not sure enough what this entails on the backend to try and estimate that part myself.

Given that the Vega team have been actively working on changing how overrides work during 2021 R1, Holly Mistlebauer is this feature likely to be done by Core Functional or Vega?

Should it be similar to what was required for loans, or are there likely to be significant differences?

That work was done some time ago, those estimates may not make sense for this work.

Comment by Holly Mistlebauer [ 09/Feb/21 ]

Marc Johnson: I'm not sure that Vega will automatically work on everything overrides. I have cc'd Darcy for her input. It probably does make more sense to have Vega provide the estimates. Darcy, is that possible? Thanks...
cc: Darcy Branchini, Brooks Travis

Comment by Marc Johnson [ 10/Feb/21 ]

Holly Mistlebauer Thanks

It probably does make more sense to have Vega provide the estimates.

If they do, and the work is allocated to the Core Functional team, that might invalidate the estimate.

Comment by Brooks Travis [ 04/Mar/21 ]

Marc Johnson Holly Mistlebauer Darcy Branchini Just wanted to check in on this. Any update on who to ask for estimates?

Comment by Marc Johnson [ 04/Mar/21 ]

Just wanted to check in on this. Any update on who to ask for estimates?

Not that I am aware of

Comment by Brooks Travis [ 05/Mar/21 ]

After talking to Darcy Branchini, I'm assigning this ticket to Vega for now, and we'll work on grooming stories and getting some estimates.

Comment by Erin Nettifee [ 26/Jan/22 ]

Brooks Travis Stephanie Buck is there any chance this could make Morning Glory or Nolana? Duke will absolutely have to have this for go-live if UXPROD-2689 Closed doesn't make it - we are go-live Summer 2023, likely on Nolana.

Comment by Erin Nettifee [ 16/Feb/23 ]

Hi Tim Auger - do you have a sense as to when this might be assigned a release? Duke is engaged in a gap analysis and this is one of our gaps for go-live.

Comment by Thomas Trutt [ 13/Mar/23 ]

Tim Auger Echoing Erin Nettifee, any update as to which release this may be added to?

Comment by Tim Auger [ 08/May/23 ]

Erin Nettifee Thomas Trutt Howdy. I've added this to the Ramsons release.

Comment by Molly Driscoll [ 17/Jul/23 ]

Tim Auger this question was just raised by the University of the Arts, who is excited to see this development for cases in which they override non-pageable collections for select faculty.

Comment by Tim Auger [ 19/Jul/23 ]

Molly Driscoll Thanks. Good to know. It sounds like we should get Stephanie Buck in the mix here. 

Stephanie – I think I took this a while back when we were still figuring out who would take on what in circulation. I've unassigned it from myself. I think Volaris could fit it into the Q release, but not Poppy due to DCB. Or do you think Vega would have time to take it on sooner? The work looks pretty straight forward to me. 

Comment by Stephanie Buck [ 19/Jul/23 ]

Hi Tim Auger and Molly Driscoll. I don't think this is a current priority for Q and it won't be on Vega's list for a bit. 

Comment by Tim Auger [ 20/Jul/23 ]

Stephanie Buck Thank you. Molly Driscoll Team Volaris occasionally takes on issues a little bit outside of our domain but we are stacked up for work in Poppy and probably will extend through Q. If we were to pinch hit for Vega, I think the earliest would be the "R" release.

Comment by Molly Driscoll [ 20/Jul/23 ]

Thank you for the additional info, Stephanie Buck and Tim Auger . So the Ramsons target (currently assigned) is possible, but not quite "likely" yet?

 

EDIT: This comes up fairly regularly as a question on the projects I'm involved in. Should I be commenting each time I receive the question?

Comment by Tim Auger [ 20/Jul/23 ]

Molly Driscoll Yes, not sure. For the time being, we've removed Team Volaris as the assigned dev team.

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