Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
customfield_11100 28815
-
eHoldings Sprint 69, eHoldings Sprint 70, eHoldings Sprint 72
-
5
-
Spitfire
Description
According to UIU-1155, User data has to be extended to include Request Preferences data:
Following fields has to be supported:
"requestPreference": { "holdShelf" : "true/false", "delivery": "true/false", "defaultServicePointId": <servicePointId> "defaultDeliveryAddressTypeId": <addressId> "fulfillment": "Delivery/Hold shelf" }
"holdShelf" – boolean, is always "true";
"delivery" – boolean, "false" by default;
"defaultServicePointId" – UUID of service point or empty (if not set);
"defaultDeliveryAddressTypeId" – UUID of user's address type selected as default in case of Delivery, can be empty;
"fulfillment" – user's fulfillment type, one of two options: "Delivery", "Hold shelf". Default: "Hold shelf"
Since the above data belong to request processing logic, it's proposed to store it next to other request related stuff in mod-circulation/mod-circulation-storage.
The goal of the spike is to define the necessary steps to introduce Request Preferences per User in mod-circulation. The outcomes include but not limited to the following:
- how and where to store the data
- what API has to be provided to make the data available to UI module(s)
- what are the base components to implement
- POC (optional)
TestRail: Results
Attachments
Issue Links
- has to be done before
-
UIU-1155 Request preferences on Edit and View user record
-
- Closed
-
- relates to
-
CIRCSTORE-154 Delivery requests: Store request preferences of user
-
- Closed
-
-
UXPROD-113 Fulfilling delivery requests
-
- Closed
-