RolePersonComments
Solution Architect
Java Lead
UI Lead
Product Owner


Jira Legacy
serverFOLIO Issue TrackerSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyUXPROD-137
 - Transfer/Relink Holdings and/or Items

...

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: (???) with 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

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:

...