Consumers of our warehouse are asking for an Excel-based data lineage. They would like to see full end to end linage from source (landing) to warehouse to mart tables including exposing any expressions, look-ups, and descriptions.
Justification for this includes:
- Excel is the application almost all business users will leverage when documenting data lineage, mappings, and data dictionaries
- In some cases the consumer is external to our company. It is not feasible to give them access to Compose or send them the HTML version of the Compose on-line documents
- Users feel that Compose on-online documents are ok, but not great. Issues they face include:
- Availability across the entire organization. There is no single web location all users can access.
- Does not solve use cases where information must be shared with external clients
- Data lineage is only at the entity level and not attribute level like is supported in the Compose application
- Not all internal users will be given read-only access to the Compose application
- Navigation and search is not user friendly. Search is not across the entire project. There is more hunting and pecking for information via drill-down
- Similar to the above point, there is no ability to trend across all fields, mappings, expressions, etc. Much easier to do in Excel.
We have had mixed results trying to maintain it in Excel on our own. It's very manual, time consuming, and prone to errors / omissions. In order to be current and accurate, Compose needs to generate it.
Thx!