Versions Compared

Old Version 5

changes.mady.by.user Benn Oshrin

Saved on

compared with

New Version 6

changes.mady.by.user Benn Oshrin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Source Files

Data Model Design

Process Flow (by example)

  1. Source/batch files are loaded into raw (R) tables
  2. The data is normalized and moved into standardized (S) tables, eg prs_sor_role_records and associated tables
  3. Where a person has multiple records from a given SOR, the "best" biodem data is elected into prs_sor_persons
    1. This covers (eg) correction of typos and name changes
  4. Where a person has multiple SORs, the "best" biodem data is elected into prc_persons
    1. Note: The current table definition implies same SOR for best name & biodem

Guidelines

  1. The database is a "black box", so nothing sees it except for core Registry code. All manipulation is done via APIs.
  2. Where possible, tables should be consolidated to keep the number of tables down and simplify administering them. As a general rule of thumb, if two tables have the same structure and vary by only one column name, the tables should be consolidated.

...