Hi everyone, Are there any plans to extend the metadata models for charts and dashboards? A couple suggestions: 1) Currently, only charts have inputs while dashboards don't. This makes sense for a Redash or Looker style visualization platform where each chart has a source / query, and multiple charts then get combined into a dashboard. However, other viz platforms (Power BI, QlikSense for instance) behave differently: ◦ In Power BI, the lineage is sources -> PBI dataset -> PBI report, where a PBI report can have many sheets and charts ◦ In QlikSense, the lineage is sources -> app, where an app can have many sheets and charts. Currently, we've mapped QlikSense apps into the Chart entity, but as you can imagine this can be a bit confusing for end users. Supporting these with more meaningful terminology would make a big difference. 2) Being able to ingest usage of dashboards / charts would be really interesting - both Power BI, Tableau and QlikSense allow capturing usage stats which could then be ingested if the metadata model supported this. Amazing work on this platform - fingers crossed datahub will become the de facto standard for data catalog platforms going forward!

@mammoth-bear-12532 ^ about the modeling question

Hi @cold-jelly-78088: thanks for the question and the suggestion. I'll get back to you with a more thoughtful response to 1)

1) Currently, only charts have inputs while dashboards don't. This makes sense for a Redash or Looker style visualization platform where each chart has a source / query, and multiple charts then get combined into a dashboard. However, other viz platforms (Power BI, QlikSense for instance) behave differently:

◦ In Power BI, the lineage is sources -> PBI dataset -> PBI report, where a PBI report can have many sheets and charts

◦ In QlikSense, the lineage is sources -> app, where an app can have many sheets and charts.

Currently, we've mapped QlikSense apps into the Chart entity, but as you can imagine this can be a bit confusing for end users. Supporting these with more meaningful terminology would make a big difference.

For:

2) Being able to ingest usage of dashboards / charts would be really interesting - both Power BI, Tableau and QlikSense allow capturing usage stats which could then be ingested if the metadata model supported this.

This is definitely in our plan, should be possible to re-use the operational aspect from datasets and attach it to charts and dashboards as well.

Thanks a lot for the response!