Good morning! I just started exploring DataHub, the platform seems to be "ingestion" driven mainly, meaning that you define what type of dataset you want to ingest ( a bigquery table for example) and add the relevant documentation to it, its tags and owners. in our case however the documentation sits one level up meaning that the same data product can be accessed by a table in bigquery or an API etc.., the overarching the documentation is the same though. can we get around this somehow within datahub? thank you!

@famous-zebra-66988 could you elaborate a bit? Would you like to ingest the documentation from this external source and have it mirrored in datahub?

Hey @astonishing-answer-96712, No I some have documentation that spans over different “ingested” datasets (i.e a bigquery table and api access point that deliver the same data in slightly different methods), would like to avoid duplicating the overlapping documentation for both datasets .

Hi @famous-zebra-66988! We don’t have anything that would address this out of the box.. one option would be to to use the Actions Framework to build custom actions that propagate documentation between entities. Separately, I wonder if this is a good use case for defining a top-level “Data Product” entity - something that we are discussing with community members in #design-data-product-entity. We don’t have a concrete timeline of when we’ll ship that just yet, but I encourage you to join the convo to see if this is a use case we should be considering!