| Role | Person | Comments |
|---|---|---|
| Solution Architect | ||
| Java Lead | ||
| UI Lead | ||
| Product Owner | Stephanie Buck |
Requirements
This feature covers ability to move attached records and maintain existing relationships. When moving holdings to another instance, all associated items have to be transferred as well. Bulk moving items and holdings. Ease of linking/relinking bib/holdings/item data. Part of the refined UX design of Inventory. Drag and drop is one possible solution.
BE Design
Connections between items, instances, holdings.
Possible scenarios and implementation:
1) Move item(s) between holdings
Changing of each moved item by request: PUT /inventory/items/{itemId} with new item.holdingsRecordId
2) Move holdings with item(s) to another instance
Changing of each moved holding by request: (???) with new holding.instanceId
3) Move selected item(s) to a holdings in another instance
This case looks the same to 1). Changing of each moved item by request: PUT /inventory/items/{itemId} with new item.holdingsRecordId
Questions:
1) Group moving of items/holdings. Do we need to support transactionality? If one of the moved item/holding fails there are two possible scenarios:
- Saving successfully updated items/holdings, just show error for unsaved items/holdings
- Roll-back all the changes if at least one of the item/holding is failed to save