Status of this?
Hold until after Aug 2.
In the Sys Ops SIG meeting the topic of Reference Data Upgrades came up. The SIG thinks that the solution of this problem for mod-inventory-storage is not enough, but that this problem needs to be solved in a general way, for all modules.
There has been a long discussion 3-4 years ago about how FOLIO should handle reference data upon upgrades. See these links for background:
Previous Notes:
Background and Problem Statement
- The issue at hand involves the handling of reference data during system upgrades. In previous upgrades, some institutions experienced data loss where customized reference data was overwritten by default settings during the upgrade process.
- This problem was particularly highlighted in recent upgrade cycles, prompting a need for a more robust solution to preserve institution-specific customizations.
Existing Solutions and Approaches
Discussion Points
- Standardization Across Modules:
- The TC debated whether a similar approach should be mandated across all modules to ensure consistency and prevent data loss during upgrades. However, it was noted that this might require module-specific adjustments, depending on how each module manages its reference data.
- Need for a Broader Solution:
- There was recognition that a broader, more flexible solution might be necessary to handle various scenarios, such as changes in reference data structures. This could involve more sophisticated checks during the upgrade process to determine whether and how data should be updated or preserved.
Potential Actions
- Subgroup Formation:
- The idea of forming a new subgroup to focus on developing a comprehensive strategy for reference data handling during upgrades was floated. This subgroup could explore creating an RFC (Request for Comments) to propose a standardized approach across the project.
- Review of Previous Work:
- It was suggested that before moving forward, the TC should review previous efforts and discussions on this topic, including past proposals and proof-of-concept work that may have stalled due to resource constraints. This review would help ensure that any new efforts build on previous work rather than starting from scratch.
Next Steps
- Further Discussion:
- The TC agreed to revisit this discussion in the next meeting, with members encouraged to review past work and consider whether they are interested in participating in a potential subgroup. The goal would be to establish a clear path forward for managing reference data during upgrades across all modules.
Today: