Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Won't Do
-
None
-
None
Description
In order to simplify the presentation of a request together with the referenced item, requestor (patron/user) and loan (via the item) provide the facility to include these records in a single request.
API Design
Introduce a new endpoint to provide optional inclusion (thoughts welcome on what this should be named):
GET /circulation/requests/{id}/combined
UI Context
The current requirements for UIREQ issues call for the following fields (some of these properties do not exist yet):
From the item (identified by itemId):
- barcode *
- title *
- author (out of scope)
- call number (out of scope)
- volume (out of scope)
- copy (out of scope)
- enumeration (out of scope)
- shelving location (out of scope)
From the user (identified by requesterId):
- name *
- barcode *
- patron group
The Requests front-end module (ui-requests), in addition to using its own /requests endpoint from mod-circ-storage, also needs access to related metadata from Users and Items. It would be more efficient to aggregate this data in a back-end business logic module than to try to combine it all in ui-requests.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
CIRC-27 create an endpoint for requests objects
-
- Closed
-
- relates to
-
CIRC-28 Store item title and barcode as part of request
-
- Closed
-
-
CIRC-29 Store requesting patron name and barcode as part of request
-
- Closed
-
-
RMB-58 building blocks for complex aggregations (federation)
-
- Closed
-
-
UIREQ-61 backend should perform aggregation and joins
-
- Open
-
-
CIRC-27 create an endpoint for requests objects
-
- Closed
-
-
CIRCSTORE-14 create an endpoint for requests objects
-
- Closed
-
-
UIREQ-1 Requests: View Request Details v1
-
- Closed
-
-
UIREQ-2 Requests: Create Request v1
-
- Closed
-
-
UIREQ-3 Requests: Search Results v1
-
- Closed
-