Transfer/Relink Holdings and/or Items

UXPROD-137 - Getting issue details... STATUS  - Transfer/Relink Holdings and/or Items

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.

No need to support transaction for items updating. Just need to populate errors for each failed items update in the response.

2) Move holdings with item(s) to another instance

Changing of each moved holding by request: PUT /inventory/holdings/{holdingId} with new holding.instanceId.

Holdings update endpoint: simple CRUD PUT endpoint should be implemented for holdings updating.

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.