Building Reporting Specifications in Collibra
Summary: Grant Rollerson, Grant Rollerson, discusses the process of building reporting specifications using Collibra and linking them to Tableau. The key point is deciding on appropriate asset types for report specifications. Grant considers using 'Report' with 'Business Terms,' 'Metrics,' and 'KPIs', and relates them to Tableau's assets using business asset groups. The goal is to maintain simplicity and clarity, especially in dealing with legacy systems, and Grant is seeking feedback from others on their approach.
Reporting Specifications
I want to
Build out my reporting specification in Collibra
hand it to a Tableau builder dude
Tableau report is subsequently built and harvested into Collibra, along with lovely lineage to Redshift
My Q is, what asset types do you use to build the report specification? This is a business asset so it feels wrong to use
Data Product b/c while Blue like Report, it takes inputs and outputs (both data assets).
Data Set & Data Element, but again both are data assets whereas a report specification is a business construct.
I could use Report, with Business Terms, Metrics & KPI for the report grain/constituents. Then;
relate the Report to the actual Tableau blue assets (Dashboard or Worksheet) via OOTB Business Asset groups Business Asset.
if keen, relate the functional grain to the Tableau Data Attribute via Business Asset represented by Data Attribute.
I ask also b/c we have legacy Report Catalogs with Tableau reports built manually as Report and Report Attributes that I want to keep, because our business users get confused by the Tableau Op Model.... so it's easier to leave them there and just relate them to the harvested Dashboard etc.
In the end the conclusion was KISS
Specifications > Business Term
Business data points in the Specification > Business Term (and Metrics, where relevant)
Anyway, keen to hear what others have done.
