Requests (UXPROD-790)

[UXPROD-2429]  Delivery Fulfillment Service Point Phase 1 - Specify an Alternate DFSP for SPs that Don't Do Delivery Created: 18/May/20  Updated: 28/May/23

Status: Open
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: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-2648 Delivery Fulfillment Service Point Ph... Analysis Complete
Defines
is defined by CIRC-917 Routing when Delivery fulfillment ser... Open
is defined by MODINVSTOR-606 BE: Delivery fulfillment service poin... Open
is defined by UITEN-111 Delivery fulfillment service point Y/... 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 Estimator: Cate Boerema (Inactive)
Back End Estimator: Cate Boerema (Inactive)
PO Rank: 100
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: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R1
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 an incomplete implementation because some SPs (for example remote storage service points) are not set up to do delivery, and some deliveries need to be routed to a specific SP that would be expected to handle the check out and physical delivery process.

Proposed feature:

This feature has been discussed and designed with the Resource access SIG. There are two phases to the feature which will be represented as two UXPROD features.

Phase 1 (this UXPROD):

  • 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
  • Suppose an item has a request on it with fulfillment preference of delivery. 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 ( UXPROD-2648 Analysis Complete ):

  • 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

See deck for full context and design: https://docs.google.com/presentation/d/1QQMjephCPdrt6UQsR5MbRSDv1BwOSIRzM5VcIMEuUSs/edit#slide=id.g8f2aaa41d7_1_14



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

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

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

Hi Sergiy Sergiyenko. 10 days seems like a lot for UITEN-111 Open . Is the extra time for writing tests and such? Or do you think there will be more frontend work needed for this than I have anticipated with my stories?

Comment by Sergiy Sergiyenko [ 09/Sep/20 ]

Hi Cate Boerema. Yes, agree, perhaps too pessimistic. I would estimate the UITEN-111 Open at 5 sp. So it would be wise to down to Medium (< 5 days).

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

Stephanie Buck, based on your email, I've taken this back from Firebird and assigning to Core Functional for now

Comment by Erin Nettifee [ 18/Jan/22 ]

Brooks Travis I'm going to take this feature to my backlog based on the PO convo today...

Comment by Erin Nettifee [ 20/Jan/22 ]

Circ POs will be discussing this feature on 1-25-2022

Comment by Erin Nettifee [ 25/Jan/22 ]

Moving this from Analysis Complete back to In Refinement as it's getting looked at again

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:23:54 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.