Sync Dev CC data between instances

Motivation

1. 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.

2. 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.

3. Reduce time to uptake a new OAGIS release for the user.

Functional Requirements

1. 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.

2.  

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

• Need to separate database schemas for End User Content and Developer Content

  • How to recognize a which database schema a particular ID is about?

    • User ID generator/management like Twitter??

    • Just use database schema to give context?

Pros

• Less sensitive to DB schema change

Cons

• May take longer

DB script that includes only new/updated records (The diff approach)

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

Pros

• Faster

Cons

• Sensitive to database schema change

Another approach???

Does any approach lend itself better to the bug fix (release)?