Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
Firebird Sprint 103
-
2
-
Firebird
Description
Purpose/Overview:
For now item's effective location is changed by database trigger. Such implementation is not capable of triggering business logic (e.g. sending domain event).
Requirements/Scope:
- If temporary/permanent location of holding is changed all items, for which location is not specified should be updated according to https://wiki.folio.org/display/RA/Effective+Location+Logic (they should inherit effective location of holding)
- Domain events should be sent for all such items, as it is for usual update
- Legacy database triggers should be removed
Approach:
On every holding update there should be check if effective location is changed. If it is changed there should sql query to find all items with unspecified location and effective location for such items should be updated.
AC:
The following cases should be checked after the implemtation:
- Changing item’s permanent/temporary location to remote location
- Moving an item to the holding with permanent/temporary remote location
- Creating an item in the holding with permanent/temporary remote location
- Starting actions on holding:
- Changing holding’s permanent/temporary location to remote location
TestRail: Results
Attachments
Issue Links
- blocks
-
MODRS-4 FOLIO-initiated sending items to the accession queue
-
- Closed
-
- defines
-
UXPROD-2696 Remote Storage Integration (Dematic thin thread)
-
- Closed
-
- relates to
-
MODINVSTOR-722 Remove update effective location database functions
-
- Closed
-
-
MODINVSTOR-941 Location changes in holdings records via batch-synchronous APIs not triggering update to item effective location
-
- Closed
-