Requests (UXPROD-790)

[UXPROD-2689] Enable Request Policy to Determine Allowed Pickup Service Points Created: 28/Sep/20  Updated: 08/Feb/24  Resolved: 09/Oct/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Requests

Type: New Feature Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Anne Ekblad
Resolution: Done Votes: 0
Labels: LC-priority2, loc, requests, was-quesnelia-now-poppy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File New Request Form - 6-14-2023 - no request types available.png     PNG File New Request Form - 7-7-2023 - request types available.PNG     PNG File New Request Form - Initial - 6-16-2023.png     PNG File New Request Policy - 6-15-2023.PNG     PNG File Service Point Pg. - Yes to No Confirmation Popup - Final.png     PNG File screenshot-1.png     PNG File uxprod 2689 Settings_Users_Transfer criteria .png     PNG File uxprod 2689 updated mock pattern large.png    
Issue links:
Blocks
blocks UXPROD-2694 Request: Allow Override of Prevented ... Blocked
Cloners
is cloned by UXPROD-2690 Prevent Local Page Requests Draft
Defines
is defined by CIRC-1824 Change request policy format Closed
is defined by CIRC-1825 Determining allowed service points - ... Closed
is defined by CIRC-1826 Determining allowed service points - ... Closed
is defined by CIRC-1827 Determining allowed service points - ... Closed
is defined by CIRC-1834 Request policy check should include a... Closed
is defined by CIRC-1871 Return allowed service points for all... Closed
is defined by CIRC-1875 Filter request types based on item st... Closed
is defined by CIRC-1876 Add code to error "Service point is n... Closed
is defined by CIRC-1877 Request policy check should include a... Closed
is defined by CIRC-1885 Pickup service point list shouldn't b... Closed
is defined by CIRCSTORE-424 Add Allowed service points to request... Closed
is defined by CIRCSTORE-425 Update request policies when service ... Closed
is defined by CIRCSTORE-426 Update request policies when service ... Closed
is defined by CIRCSTORE-429 Validate service points when request ... Closed
is defined by CIRCSTORE-451 Return only one error in response for... Closed
is defined by FAT-6351 Request - allowed service points Kara... Closed
is defined by FAT-7490 Request policies get updated when ser... Closed
is defined by FAT-7491 Service point validation during reque... Closed
is defined by FAT-7865 Tests for CIRC-1877 Closed
is defined by FAT-7866 Tests for CIRCSTORE-451 Closed
is defined by MODINVSTOR-1077 Publish a domain event when service p... Closed
is defined by UICIRC-963 Allowing Selection of Some Pickup Ser... Closed
is defined by UICIRC-967 Ensure proper error if a Pickup locat... Closed
is defined by UICIRC-972 Make visible selected service points ... Closed
is defined by UICIRC-981 Add informational message for Holds t... Closed
is defined by UIREQ-971 Request type dropdown Closed
is defined by UIREQ-977 Ensure Only Available Service Points ... Closed
is defined by UIREQ-978 Change Request type field to dropdown... Closed
is defined by UIREQ-981 New Request - Pickup Service Point error Closed
is defined by UIREQ-1022 New Request - "One or more Pickup loc... Closed
is defined by UIREQ-1026 Rename modal window for select reques... Closed
is defined by UITEN-251 Service Point Page - Add 'Confirm Pic... Closed
is defined by UIREQ-1005 Move request popup show available Req... Closed
is defined by UIREQ-1028 Add "operation" parameter to "allowed... Closed
is defined by UIREQ-1030 Add "itemId" parameter to "allowed-se... Closed
is defined by CIRC-1890 Allowed service points: fix move oper... Closed
Duplicate
is duplicated by UXPROD-1630 Pre-Check Request Policy When Request... Closed
is duplicated by CIRC-214 Provide an API for checking available... Closed
Gantt End to Start
has to be done after UIREQ-980 [SPIKE] Requests: Evaluate item and t... Closed
Relates
relates to UIREQ-994 [AQA] We should stable E2E tests for ... Open
relates to UICIRC-1016 Error message and cannot see or edit ... Closed
relates to UXPROD-1561 Allow Request Policy to Control Reque... Draft
relates to UXPROD-2649 Request: Allow Override of Request Po... Analysis Complete
Release: Poppy (R2 2023)
Epic Link: Requests
Front End Estimate: XXL < 30 days
Front End Estimator: Matt Connolly
Front-End Confidence factor: 90%
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Bohdan Suprun (Inactive)
Back-End Confidence factor: 80%
Estimation Notes and Assumptions: BE: Adding the new property to request policy and forwarding it from storage to circ - 5 days, applying the validation - 2-3 days. Assuming that UXPROD-2690 goes first, so there will be no API breaking changes.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 11
PO Rank: 51
PO Ranking Note: 2021-03-28 - BT: Making my PO rank the 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: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R3
Rank: Mainz (Full TBD): R3
Rank: MI State-Lib of MI (Sum 2021): R2
Rank: MO State (MVP June 2020): R3
Rank: St. Michael's College (Sum 2021): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: For each type of request allowed in a request policy, user should be able to specify which service points are allowed for pickup (from among the service points that are flagged as pickup SPs in Settings > Tenant > Service points).

Use cases:

  1. Delivering items with restrictions on access. For example, special collections libraries may store items at an off-site facility, and want those items to only be requestable to one specific service point on campus.
    1. For example, at LoC, only select patron groups (yet to be nailed down) can select “Adams Charge Station” as the pick up location. Items with a Loan Type of “Special material” can only be served in the Adams Building Reading Room; i.e., patron cannot select a different pick up service point. These are commonly items with fold outs or multiple pieces, and the Adams Reading Room has the most robust security controls.
  2. Managing unstaffed pickup service points. Libraries may have unattended service points for pickup / drop-off - esp. campuses that have broad geographic footprints. For example, at Duke, we have a full academic program (Physicians Assistant) housed in a building about two miles from campus with no regular transit to campus. So they can request library items to be delivered to their building. But in those cases, libraries may want to restrict some materials from going to unstaffed pickup service points, such as high-value textbooks or microfiche.
  3. During the COVID response, our (Duke) Law, Medical, and Business libraries have restricted their buildings so that they are only accessible to their faculty, staff and students. Accordingly, we want to be able to restrict people who are not part of those schools from requesting book delivery to those schools, since they can't get into the libraries themselves.
  4. Routing to service points with limited access.
    1. For example, say you have a library system with faculty, staff and students, and 15 service points. 3 of those service points are in administrative areas generally only accessible to staff. You want to prohibit students from being able to request routing to those service points since they won't easily be able to pick up their items. You could set these service points to "Pickup service point = No" in Tenant settings but then you wouldn't be able to allow staff to pick their items up there.
    2. For LC: "A user in the staff patron group can request delivery to any of 3 staff-only pick-up service points. For the same item, a user in the public patron group can request delivery to several public pick-up service points."
  5. Another example; some groups can only request a specific pickup service point as that service point is the one that mails items out of the Library and that capability does not exist at all service points
  6. Interlibrary loan: Interlibrary Loan patron groups can only request ILL staff service points to ensure proper check outs and tracking

User experience: follow the pattern established in Settings. See "uxprod 2689 Settings_Users_Transfer criteria" and "uxprod 2689 updated mock pattern large" attached 

In scope:

  • Request Policy: Specify allowed pickup service points for each allowed request type
  • Request Policy and New Request Form: Prevent selection of disallowed pickup service points when requesting
  • When a request is moved to a different item, the request policy should be rechecked to ensure it is allowed

Out of scope:

  • Override UXPROD-2694 Blocked
    • Request: Allow override of prevented service point.
    • Override permission (need to decide whether we need a specific permission for this kind of policy override or if there can be a general "request policy override permission")
  • Permission escalation for policy override UXPROD-2645 Draft
  • Preventing local page requests. We have libraries that, for example, would be willing to route page requests to other schools for grad students but don't want to do local pages for them (since the perception is that if they are local they should just go get the book.) The functionality described in this feature could be used to prevent local page requests, but it would require more policies and circulation rules to be created than the feature described in UXPROD-2690 Draft
  • Differentiating open and closed stacks: in Mainz, we have two campuses and only allow page requests to the other campus for open stacks. This is similar to "preventing local pages" ( UXPROD-2690 Draft ) but on a campus level instead of location. In addition, we have closed stacks on both campuses with an elaborate set of rules what can be picked up where.

Additional information:
This feature arose out of discussions around preventing local page requests. Here are a couple of documents that provide context for the discussion:



 Comments   
Comment by Cate Boerema (Inactive) [ 01/Oct/20 ]

Bohdan Suprun and Matt Connolly could you please provide FE and BE estimates for this feature? Let me know if you don't understand the feature write-up. Thanks!

Comment by Bohdan Suprun (Inactive) [ 02/Oct/20 ]

Cate Boerema, it is ~10 days with assumption that UXPROD-2690 Draft goes first, so all breaking changes will be handled.

Comment by Cate Boerema (Inactive) [ 05/Oct/20 ]

Hi Matt Connolly, I realized that the title of this feature also referred to the Request policy so I wondered if you might have assumed all that was in scope was work in the request policy itself (similar to your initial assumption on UXPROD-2690 Draft ). In fact, this is intended to represent all the work needed to make this feature function end-to-end. So there is work in the request policy but then we also need to do work in the request itself: "Request: Prevent selection of disallowed pickup service points when requesting" in scope"

Please revise your estimate if needed. Thanks!

Comment by Matt Connolly [ 05/Oct/20 ]

Cate Boerema I bumped it up a little bit. Thanks!

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