Requests (UXPROD-790)

[UXPROD-2648] Delivery Fulfillment Service Point Phase 2 - Collect DFSP in the User's Address(es) Created: 07/Sep/20  Updated: 27/Jan/23

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

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Tim Auger
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-2429 Delivery Fulfillment Service Point P... Open
Defines
is defined by CIRC-918 Use DFSP in Delivery Address, If Ava... Open
is defined by MODUIMP-25 Support Load of DFSP in User Address ... Open
is defined by UIREQ-518 Display DFSP on Request Record Open
is defined by UIU-1841 Collect DFSP in User Address Block Open
Relates
relates to UXPROD-2696 Remote Storage Integration (Dematic t... Closed
relates to UXPROD-3494 Resolve issues encountered by having ... Draft
Epic Link: Requests
Front End Estimate: TBD
Front End Estimator: Sergiy Sergiyenko
Back End Estimator: Marc Johnson
Development Team: Volaris
PO Rank: 19
PO Ranking Note: CB: Marking PO rank the same as calculated total rank for now. Currently 19.
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R2
Rank: MO State (MVP June 2020): R3
Rank: U of AL (MVP Oct 2020): R4

 Description   

DFSP = Delivery fulfillment service point

Background:

Delivery requests were originally implemented in Q4 2019 such that, when a delivery request is at the top of the queue and the requested item is checked in at any service point, FOLIO will attempt to begin the fulfillment process (i.e. check the item out to the requester). This is a challenge because some SPs (for example remote storage service points) are not set up to do delivery. To address this issue, the RA SIG has agreed on a design which is being broken down into two parts. This UXPROD represents the second part. See deck for full context and design: https://docs.google.com/presentation/d/1QQMjephCPdrt6UQsR5MbRSDv1BwOSIRzM5VcIMEuUSs/edit#slide=id.g8f2aaa41d7_1_14

Proposed feature:

Phase 1 ( UXPROD-2429 Open ):

  • Enable users to specify at the SP whether the SP is a DFSP or not
  • If the SP is not a DFSP, require users to specify an alternate DSFP
  • When an item is checked in at a SP that is not a DFSP, FOLIO will route the item to the alternate DFSP for delivery request fulfillment

Phase 2 (this UXPROD):

  • Enable the capture of DFSP in the user's address
  • If an item is checked in, FOLIO checks the delivery request and then follows this logic (in this order):
    1. Is there a DFSP associated with the delivery address? If so, use that.
    2. Is the SP a DFSP = Y? If so, use it.
    3. Is the SP a DFSP = N? If so, use the Alternate/Backup DFSP
    4. If no Alternate DFSP is specified, fail check in
      • Error message: Item with delivery request can't be checked in at this service point. An alternate delivery fulfillment service point must be specified in Settings.


 Comments   
Comment by Cate Boerema (Inactive) [ 07/Sep/20 ]

Marc Johnson and Sergiy Sergiyenko can you please estimate this feature for me? Thanks much!

Comment by Holly Mistlebauer [ 07/Mar/22 ]

This feature is marked DRAFT until Brooks Travis has a chance to review it for validity.

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