Data Model ERDs
(revised February 2009April 2011)
Currently Being Revised
- Full Data Model (old)
- Full Data Model (revised April 2011)
- Full Data Model (revised Feb 2012)
- Common Tables
- Groups
- Persons
...
Source Files
- Available in SVN
Notes
...
- Source/batch files are loaded into raw (R) tables
- The data is normalized and moved into standardized (S) tables, eg
prs_sor_role_records
and associated tables - Where a person has multiple records, the "best" biodem data is elected into
prc_persons
## This covers (eg) correction of typos and name changes
Guidelines
- The database is a "black box", so nothing sees it except for core Registry code. All manipulation is done via APIs.
- 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.
- As a general rule, only Calculated data is referenced for publishing outside the Registry.
...
- Table names are prefixed
CCT_
whereCC
indicates the responsible component andT
indicates the type of table as enumerated above. - Table and column names are all lowercase, with underscores (_) to separate words/fragments. StudlyCaps are not used.
- Natural english is preferred over major/minor. So
start_date
, notdate_start
. - Column names should avoid incorporating the table name.
- The suffix _column name
id
indicates a row identifier. - The suffix
_t
indicates a type identifier, as defined inctx_data_types
.
...