Yeah, Entity modeling was one of the big inspirations to our approach. The main difference is how do you reassemble the single time-series table to create any table.
This was quite a challenge and I think what makes the traceability and source of truth problem a lot simpler.
In Narrator, the data team writes small SQL to create single customer centric business concepts that we call activities. These are around 25 lines and decided to be understood by anyone in the company (i.e. "viewed page", "called us",...).
Now, every question you or a stakeholder has will simply be a rearrangement of these activities. If you can describe what you want, then Narrator can assemble a table that represent it.
Source of truth - What ever is in the activity stream?
Tracebility - always Dataset (activities and how they relate), then activities (~25 SQL).
Coherent Model - Customers doing actions in time.
Does that make sense? Some of these things are easier to show in a demo then describe in text.
This was quite a challenge and I think what makes the traceability and source of truth problem a lot simpler.
In Narrator, the data team writes small SQL to create single customer centric business concepts that we call activities. These are around 25 lines and decided to be understood by anyone in the company (i.e. "viewed page", "called us",...).
Now, every question you or a stakeholder has will simply be a rearrangement of these activities. If you can describe what you want, then Narrator can assemble a table that represent it.
Source of truth - What ever is in the activity stream? Tracebility - always Dataset (activities and how they relate), then activities (~25 SQL). Coherent Model - Customers doing actions in time.
Does that make sense? Some of these things are easier to show in a demo then describe in text.