Upgrading tenant resets reference and sample records
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
is cloned by
Checklist
hideTestRail: Results
Activity
Show:

Julian Ladisch March 29, 2023 at 7:10 AM
Closed, because we cannot test migration on bugfest environment.
Done
Details
Details
Assignee
Unassigned
UnassignedReporter

Labels
Priority
Development Team
Thunderjet
Fix versions
Release
Orchid (R1 2023) Bug Fix
RCA Group
Data related (ex. Can be detected with large dataset only)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 18, 2022 at 3:15 PM
Updated June 18, 2024 at 8:14 AM
Resolved March 28, 2023 at 9:04 AM
TestRail: Cases
TestRail: Runs
When upgrading a tenant for mod-organizations-storage all reference and sample records are installed again:
organizations
contacts
interfaces
categories
organization_types
Libraries often modify (translation, rename) or delete (category not needed) these records. These changes are reverted on mod-organizations-storage migration resulting in duplicate work for staff.
Fix: When upgrading from version a to version b mod-organizations-storage should not touch records that haven't change from a to b.
Example how this might be implemented:
https://github.com/folio-org/mod-inventory-storage/blob/647654b45d46fce03a07f084fb7c2ca7756ccc2e/src/main/java/org/folio/rest/impl/TenantRefAPI.java#L110-L157