Requests (UXPROD-790)

[UXPROD-2694] Request: Allow Override of Prevented Pickup Service Point Created: 29/Sep/20  Updated: 28/Nov/23

Status: Blocked
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Cate Boerema (Inactive) Assignee: Brooks Travis
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-2689 Enable Request Policy to Determine Al... Closed
is blocked by UXPROD-2690 Prevent Local Page Requests Draft
Relates
relates to UXPROD-2649 Request: Allow Override of Request Po... Analysis Complete
Epic Link: Requests
Development Team: None
PO Rank: 15
PO Ranking Note: 2021-03-05 - BT: Making PO rank same as the calculated total rank for now.
2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R3
Rank: MO State (MVP June 2020): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: Once we have implemented Prevent Local Page Requests in Request Policy ( UXPROD-2690 Draft ) and/or Specify Allowed Pickup Service Points in Request Policy ( UXPROD-2689 Closed ), there will be situations in which you are prevented from selecting a pickup service point when creating a request. The purpose of this feature is to allow this to be overridden byt staff with appropriate permissions.

Use cases:

  • Normally local page requests are prevented but I want to allow a patron to make one because they have a short-term injury or a longer term disability

Thoughts on design:

  • Discussed in RA SIG meeting on 2020-09-28
  • Normally an override would be offered in the context of request creation (e.g. an override button on the "this service point isn't allowed" popup) and we may still want to offer that
  • But, in this case, you might want the ability to indicate in the user record if the user should be allowed local pages or other exceptions (because, for example, they are disabled or injured). Setting something in the user record would remove the need to do an override at the point of request creation (which may require the patron to call to the library - as overrides can't be done by patrons via discovery layer).
  • IF we decide to implement an Override capability from within the Request creation workflow, SMEs think it would be okay if the permission to do this override is bundled with other request override permissions (see UXPROD-2649 Analysis Complete ).

Potential workaround: Create a patron group that could be selected for patrons that should get special exceptions and then tie that patron group to a less restrictive request policy in circ rules. This could balloon the number of patron groups and circ rules needed.


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