Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Sif Sprint 158
-
Sif
-
Orchid (R1 2023)
-
TBD
Description
Purpose: The UI to create/delete bound-with relationships is handled in edit mode of the item record, where it will be possible to adding or delete/removing the HRIDs of holdings records that should be linked to the primary item. To support the UI solution msl321 has identified that when we implement the 'save' action, it would be ideal to have a PUT API where he could pass in a single item ID and a list of holdings IDs, and it would replace any existing bound-with parts that include that item ID with the new list.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-1998 Create/edit bound-with item. Edit screen. Add bound-with and analytics with pop-up modal.
-
- Closed
-
-
UIIN-2401 Create/edit bound-with item. Edit screens edit modal. Entered data to be cleared when re-opened
-
- Closed
-
- defines
-
UXPROD-3640 Edit and delete - second iteration. Analytical records; bound with - part 2: link multiple bibs to the same item
-
- Closed
-
- is continued by
-
MODINVSTOR-1025 Race condition in /inventory-storage/bound-withs
-
- Open
-
-
MODINVSTOR-1026 Future.onComplete should be Future.compose in BoundWithAPI.java
-
- Closed
-
-
MODINVSTOR-1027 Unused boundWith examples
-
- Closed
-
-
MODINVSTOR-1028 GenericCompositeFuture.all in BoundWithAPI.java
-
- Closed
-
-
MODINVSTOR-1029 Future<Void> BoundWithAPI.isValid, not Future<Boolean>
-
- Closed
-
-
MODINVSTOR-1030 Avoid raw types in BoundWithAPI.getDeleteBoundWithPartFutures
-
- Closed
-
-
MODINVSTOR-1031 Avoid raw types in BoundWithAPI.getCreateBoundWithPartFutures
-
- Closed
-