Motivation
Requiring Score developers to create custom DB script every time there is a new CC release, even when there is no DB schema change, is not a sustainable approach.
Score users are increasingly asking to make a replacement release like 10.7.0.1 replaced 10.7.0. Even though that is a bug release, now there is a desire for minor releases to be replacement release too. It is not efficient and sustainable to create custom DB script every time.
Reduce time to uptake a new OAGIS release for the user.
Functional Requirements
Score dev user should be able to click a button to generate a DB script from a Score instance that can be distributed to other Score instances to sync the standard data, when there is no DB schema change. Standard data can include CC, code lists, and agency ID list.
Approaches
DB script that includes the entire standard data
Approach detail
….how to do this…..how does the approach works….
Issues/Barriers to this approach
…..given the current Score design, what are the issues to employing such approaches and what changes are needed to effectively employing the approach……..…..specifics to consider
DB script that includes only new/updated records
Approach detail
….how to do this…..how does the approach works….
Issues/Barriers to this approach
…..given the current Score design, what are the issues to employing such approaches and what changes are needed to effectively employing the approach……..…..specifics to consider