data modeling whitepaper

Understanding Corepula Method Data Modeling building blocks - An Overview of the Non-Historized Attribute Entity Type

In this article we will discuss an important Corepula Method data modeling building block called "non-historized entity type" and discuss its importance.

From the data modeling perpective,a non-historized attribute construct stores a set of non-historized attributes. Non-historized attributes are those whose value should never change (at least in the eyes of the business). A pool of non-historized attributes is created by stripping away all static attributes from the underlying source entity. The final list of non-historized attributes must be approved by the business. Each non-historized entity is directly linked to one and only one core entity type.

From the data modeling point of view, a source system's natural keys must be added to the non-historized attribute pool. These natural key attributes play a crucial role in tying together source and Corepula Method-based schema records. In addition, they are leveraged by the resulting ETL process in the record-matching phase to help identify whether a given source record already exists. Attributes such as GENDER CODE, EYE COLOR, and BIRTH DATE are good candidates for being classified as non-historized. The list of non-historized attributes is typically industry- and business-specific.

For a more thorough introduction into Corepula Method, please download Corepula Method data modeling whitepaper (PDF)