Patron Portal Support (for Patron Features in Discovery) (UXPROD-992)

[UXPROD-3646] Support Delivery Requests via Patron Edge Service Created: 20/Apr/22  Updated: 30/Nov/23

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Portal Support (for Patron Features in Discovery)

Type: New Feature Priority: P3
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: patronportal, requests, resourceaccess, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by EDGPATRON-38 Delivery Request Support: Extend Patr... Draft
is defined by EDGPATRON-85 Delivery Request Support: Extend Patr... Draft
Epic Link: Patron Portal Support (for Patron Features in Discovery)
Front End Estimate: Out of scope
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:

The current implementation of edge patron services does not support placing delivery fulfillment requests using using FOLIO's purpose-built functionality. We need to extend edge-patron/mod-patron to support creating holds (requests) with a delivery fulfillment preference and to supply additional information to the edge client to facilitate such requests (eg. patron default fulfillment preference, pickup location, is delivery enabled, default delivery address, available address options for the user, etc.)

In scope

  • Update the API schema for edge/mod-patron to support fields required for either pick-up and delivery fulfillment requests
  • Update patron account summary API in edge/mod-patron to include the following pieces of information:
    • Is the "delivery" fulfillment option enabled for the user?
    • What is the user's default fulfillment preference (delivery or pick-up)?
    • What is the user's default pickup location?
    • If "delivery" is enabled, what are the user's available addresses?
    • If delivery is enabled, what is the user's default delivery address?

Out of scope

  • Free-form address entry
  • User update of their contact information (address)

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • Do we include the full address in the patron account information, or just the type Id and label?
  • Should delivery information be an optional parameter of the (eg. "includeHoldPreference=true/false")?


 Comments   
Comment by Tim Darlington [ 19/Aug/22 ]

Re the question "Do we include the full address in the patron account information, or just the type Id and label?", Massey would prefer that full address is displayed, as patrons often forget to update their address with the University and may only realise this when requesting if the delivery address is displayed to them.

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