That is what I have already found out. In Tableau our users are mostly using 4 entities: Workbook, Dashboard, View, Datasource. In terms of Datahub Dashboard is a Dashboard, View is a Chart, and Datasource can be represented as a Dataset (with some assumptions). No correspondence for Workbook, which is an entity with several Dashboards and Datasources. About ingestion - I'm using tableauserverclient python module to get the data, Tableau Server allows you to get some meta-information directly from the objects (names, tags, urls and so on), but for additional information (like list of datasources and sql code) I had to download xml-files and parse them. It requires admin user and a generated token. P.S.: I've never used Tableau before and it brings me a lot of pain, and I may be missing something obvious 😅 Hope that starts some action cat on keyboard

Interesting mapping, thanks for sharing

We've been discussing introducing "Container" entities that would likely be able to map to the Workbook concept you're talking about, basically groups of other entities with some attached metadata. Think this could work?

Will it also support lineage? If it is possible to make a dataset -> container lineage, this can work

Why lineage specifically? We’d want some sort of contains edge, yes

Because "contains" is not the right form of relationship in this case, it is rather "uses data from" like any other form of data transformation

hmm i see

It is a more complex entity. It has all the usual metadata (name, description, url, tags, owners, and so on), consists of several dashboards and charts and depends on several datasources. I'd say that easiest way is to create a new entity, that can be downstream for dashboard, chart, dataset. P.S.: our BI engineers are very busy so it's hard to get any information from them, and I'm working with small pieces of information that I managed to get