Page Comparison

...

• Credentials
• Account
• Business Rules
• Courses
• Departments

Source Files

• Available in SVN

Notes

• Data Model ERD Notes

...

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, the "best" biodem data is elected into prc_persons## This covers (eg) correction of typos and name changes

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.
3. As a general rule, only Calculated data is referenced for publishing outside the Registry.

...

1. Table names are prefixed CCT_ where CC indicates the responsible component and T indicates the type of table as enumerated above.
2. Table and column names are all lowercase, with underscores ({_}) to separate words/fragments. StudlyCaps are not used.
3. Natural english is preferred over major/minor. So start_date, not date_start.
4. Column names should avoid incorporating the table name.
5. The column name id indicates a row identifier.
6. The suffix _t indicates a type identifier, as defined in ctx_data_types.

...