A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

When we ingest metadata from different source systems in an organization, it's possible that at the origin a field is called "score", while downstream system may name the same field as "marks". How do we handle it in DataHub to convey to a user that both are same fields?

Is there any way to capture semantics in DataHub?

<@U02FTL239SL> This is precisely what the Business Glossary is meant to address. It allows you to declare a controlled vocabulary of terms and relationships which can subsequently be associated with real-world data in a manner similar to tagging

<@U01GCJKA8P9> Thanks for the input. Could you please point me to any example .yml and .json where I could see the structure of Business Glossary ingestion to DataHub?

Here is a sample business glossary showing how you can define a Business Glossary in YML:
<https://gist.github.com/gabe-lyons/a9cbfd03fd4b30c5e1ac8d69ea0f7463>

Here is a short video demoing what that glossary would look like once it was ingested in datahub:
<https://www.loom.com/share/3ddbcf86975c468d9a0c55d2428eab81>