Comment on page
Data Models and Entities
The data warehouse can often turn into a data maze. Census helps highlight the most important business data so your teams can get going quickly.
By design, a data warehouse is meant to store massive amounts of data, and it does so very well. It's one of the reasons it's such a powerful platform for companies to build on top of. But all of that data makes navigating a warehouse a challenge, particularly for the members of your team that don't spend their day thinking about schemas and organizational structures.
There are many different methodologies for organizing a data warehouse. dbt has a recommended approach and the Kimball approach is still common. Census most often deals with data at the end of those pipelines, stored in the final step (often the "publish" step, or data mart if you use that terminology).
For the users of your data, the vast majority of what happens in the warehouse is not important to them, and often only a subset of final data is intended to be used.
Census provides two concepts on top of your data warehouse to make it easier to control how data is used in Syncs and Segments.
- 2.Entities are the most important models in your warehouse. They're the ones that most of your company should be using for everything they do in Census. Entities also let you define a bunch of additional metadata about how to use those models.
- 3.Simply use any table or view available in your warehouse as well.
For your data team members, most of the management required to use Census is curating and managing your set of entities that matter for the business teams at your company from the set of models you already have, and extending the set of properties available to them.