ASPIRe Data Warehouse Naming Conventions

urn:js:virtue:aspire:standard:4.1

TL;DR

The following naming conventions should be applied to objects in the ASPIRE Data Warehouse.

Definition

The following sections define the standard for each schema and object type

Staging tables (ADW_STAGE)

The following convention aims to follow elements of the S3 Raw bucket it is loaded from to enable automation and consistency. Double underscores separate each element of the name to avoid ambiguity where underscores exist within an element.

Convention: <IRM L1 AREA>__<Max 6 character Source Name code>__<Max 6 character Extract Description code>

Example: CUSTOMER__GOLWEB__DIGINT

(Customer IRM, Groceries On-Line Website, Digital Interactions extract)

The extract description describes the data being extracted from the source. It does not reflect the extract file names.

Raw Data Vault (ADW_RDV)

TBC

Business Data Vault (ADW_BDV)

TBC

Transform (<IRM>_TRAN)

TBC

Presentation Layer (<IRM>_PL)

TBC