In FOLIO, most storage modules follow the "last writer wins" strategy for handling record updates. From the UI perspective this may lead to a situation when a stale record (older version of a give record) previously loaded into the UI may override a more recent version on the server. Hence relevant updates may get lost in the process and the user is not made aware of what has happened.
From the storage and API perspective, optimistic locking is the proposed strategy to handle conflicts: (
UXPROD-1752). Handling of updates in FOLIO should rely on more explicit semantics, both in the storage (backend) APIs and the way it is communicated to the user through the UI.
1 user and system trying to act on the same record, either individual records or batch
- User A editing a user and system batch process is updating lots of users
- User A editing an instance/holding/item and data import updating the same record (consider the DI redesign that is taking place now)
- User A editing an item and checkout trying to update the item status
- User A editing an item and bulk renewal trying to update the item
- User A editing a budget and system applying a transaction to that budget at the same time
- User A editing an instance/holdings/item after data import ran in Preview mode but before the data import changes were committed
- User A editing a request while the request is being expired (request expiration date or hold shelf expiration date) - rare