Another question, have you thought about some sort of visual / flow chart representation of how data flows from through various tables, views, ETL processes, stored procedures, etc. before finally making it to a report or dashboard? We have some processes that kind of need documentation like this and it would seem ideal to do it in the same place where you are defining everything about those tables/views/stored procs/dashboards. I'm happy to discuss if this doesn't make sense haha.
1 year ago
This does make sense, lineage information between the different data assets in Secoda is something that we've been working away at over time. We currently extract table lineage for Redshift, BigQuery and Snowflake and are working on getting the same feature out for Postgres and Microsoft SQL Server. So once that's out I will let you know