Requests (UXPROD-790)

[UXPROD-113] Fulfilling delivery requests Created: 18/Jan/18  Updated: 16/Sep/20  Resolved: 11/Dec/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Requests

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: cap-mvp, po-mvp, requests, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-542 Some staff slip tokens are missing fr... Closed
is defined by UIREQ-369 Disallow editing Fulfillment preferen... Closed
is defined by CIRC-508 Implement "Awaiting delivery" and "Op... Closed
is defined by CIRC-509 Expiration of Delivery Requests Closed
is defined by CIRC-511 Update request whitelist to handle ne... Closed
is defined by UICHKIN-109 Route for delivery check in modal + d... Closed
is defined by UICHKIN-146 {{requester.country}} token not popul... Closed
is defined by UICIRC-316 View/edit request delivery slip Closed
is defined by UICIRC-319 Tokens for request delivery slip Closed
is defined by UICIRC-320 Request delivery slip preview Closed
is defined by UIIN-798 Include New "Open - Awaiting delivery... Closed
is defined by UIIN-799 Allow "Awaiting delivery" items to be... Closed
is defined by UIREQ-312 Use user's fulfillment preference to ... Closed
is defined by UIREQ-355 Don't Set Hold Shelf Expiration Date ... Closed
is defined by UIREQ-356 Actions on "Open - Awaiting delivery"... Closed
is defined by UIREQ-357 Add Filter in Requests for New "Open ... Closed
is defined by UIREQ-358 Include New "Open - Awaiting pickup" ... Closed
is defined by UIREQ-359 Update request whitelist to handle ne... Closed
is defined by UIREQ-375 Test: Make sure delivery requests wor... Closed
is defined by UIREQ-380 Wrong delivery address selected when ... Closed
is defined by UITEN-54 Service point: Print by default for R... Closed
is defined by UIU-1302 Include New "Open - Awaiting delivery... Closed
Duplicate
is duplicated by UXPROD-4 Assign Patron default service point f... Closed
Relates
relates to CIRC-436 [Spike] Delivery requests: support re... Closed
relates to MODKBEKBJ-303 BE: Review UXPROD-113 Closed
relates to UIEH-779 FE: Review UXPROD-113 Closed
relates to UXPROD-1561 Allow Request Policy to Control Reque... Draft
relates to CIRC-437 [Spike] Delivery requests: request pr... Closed
relates to CIRC-579 Open requests in snapshot with no que... Closed
relates to CIRCSTORE-150 Delivery requests: add new staff slip... Closed
relates to UICHKIN-138 Checking in of a canceled delivery re... Closed
relates to UICHKOUT-563 Include New "Open - Awaiting delivery... Closed
relates to UICHKOUT-584 Item barcode not auto-populating when... Closed
relates to UIREQ-384 Duplicate not working when have "Requ... Closed
relates to UIREQ-385 Wrong menus showing when duplicating ... Closed
relates to UIREQ-386 Attempting to duplicate request as us... Closed
relates to UIREQ-387 Creating request as user other than d... Closed
relates to CIRC-441 [Spike] Delivery requests: support to... Closed
relates to UIU-1404 Address type displaying as UUID when ... Closed
Requires
requires UIREQ-377 Strange behavior when editing request... Closed
requires CIRC-454 Delivery requests: support tokens for... Closed
requires CIRCSTORE-154 Delivery requests: Store request pref... Closed
Potential Workaround: Cate Boerema: As far as I know, for institutions that do delivery requests (many), there is no workaround (aside from discontinuing those requests). For this reason, I have increased the rank and labeled po-mvp
Epic Link: Requests
Analysis Estimate: Medium < 5 days
Analysis Estimator: Tania Fersenheim
Front End Estimate: Medium < 5 days
Front End Estimator: Matt Connolly
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: assumes simplest case, & similar to Holds
Development Team: Spitfire
PO Rank: 96.3
PO Ranking Note: 2019-07-10: As far as I know, for institutions that do delivery requests (many), there is no workaround (aside from discontinuing those requests). For this reason, I have increased the rank and labeled po-mvp.
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R2

 Description   

Purpose: To implement fulfillment of requests that have a fulfillment preference of Delivery, including:

  1. Settings in User record to determine defaults for fulfillment options
  2. Automatic check out of a requested item to the requester
  3. Alerts at checkin, checkout and renewal that an item is wanted for a request with fulfillment preference "Delivery"
  4. Delivery slips and notices to the patron ("on its way" patron notice may come in separate UXPROD)

Out of scope:

  • Permission to create delivery request for users who are not normally allowed delivery (this will require action based permissions and, possibly, override functionality) CB: Moved from UXPROD-236 Closed

Mockups for fulfillment preference setting on user record: https://drive.google.com/drive/folders/1lqjdblpO_3wFLYcZdR4jabGCmp0iFsmC



 Comments   
Comment by Tania Fersenheim [ 03/Oct/18 ]

Front end estimate revised to account for folding in alerts at checkin, checkout, renewal (see UXPROD-95 Closed , UXPROD-518 Closed , UXPROD-519 Closed which are now duplicates)

Comment by Erin Nettifee [ 28/Jun/19 ]

I think there are ways this could be split or simplified as it was discussed at the RA SIG.

If the entire feature cannot be available at go-live, Duke would prioritize the ability to have custom templates for delivery and custom notices. E.g., if the patron wants delivery, and there is a flag or whatever that says they can have delivery, when that item is checked out to them the notice should indicate that it is in the process of delivery and may not be immediately available.

This UXPROD also probably needs some concept of delivery address, yes? Which would then fold into tokens for notices and things like that.

Comment by Cate Boerema (Inactive) [ 02/Jul/19 ]

Discussed in the RA SIG feature re-ranking. Discussion begins at 26:29 of this recording: https://drive.google.com/file/d/15RbACU90Ln4JAazWSz0iM4ZSYia6mIaK/view?usp=sharing

This is really important for some institutions and not needed by others which is dragging down the overall score. Suggestion was that we discuss whether there is a very lite implementation we could do for go-live which we could extend after that. Need to record the fact patron is requesting delivery. Also, need to do notification about delivery method. What can we do minimally for go-live?

This is on the RA SIG agenda.

Comment by Cate Boerema (Inactive) [ 02/Jul/19 ]

This UXPROD also probably needs some concept of delivery address, yes? Which would then fold into tokens for notices and things like that.

Erin Nettifee FOLIO already has multiple addresses per user and, when you select the delivery option in Requests, you can choose from among those addresses. What we don't have defined and working is what happens after that. Also, we don't have the ability to control whether delivery is allowed and to what addresses (see UXPROD-1561 Draft ).

Per above comment, we will discuss minimal implementation for go-live in the RA SIG. Thansk

Comment by Victoria_Smelova [ 28/Aug/19 ]

For Spitfire team to review: https://ebscomeetings.webex.com/ebscomeetings/lsr.php?RCID=07b272e16b6740049bc9f483779e537b

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