<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Semantic Bridge to Unity Catalog in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/semantic-bridge-to-unity-catalog/m-p/141416#M845</link>
    <description>&lt;P&gt;&lt;/P&gt;
&lt;P class="subtitle"&gt;How Ontos bridges the gap between technical metadata and business meaning&lt;/P&gt;
&lt;P&gt;Here's a scenario that might sound familiar. You've got Unity Catalog humming along—tables are registered, lineage is tracked, access controls are in place. Technically, everything's governed. But then someone from the business side asks: "What exactly does &lt;CODE&gt;customer_ltv_score&lt;/CODE&gt; mean? Who owns the definition? Is this the canonical source or is there another table I should be using?"&lt;/P&gt;
&lt;P&gt;And suddenly you realize: Unity Catalog tells you &lt;EM&gt;what&lt;/EM&gt; exists. It doesn't tell you what it &lt;EM&gt;means&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;That's the gap Ontos is designed to fill unless you are also using metric views with unity catalog.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/metric-views/" target="_blank"&gt;https://learn.microsoft.com/en-us/azure/databricks/metric-views/&lt;/A&gt;&lt;/P&gt;
&lt;H2&gt;First, a Quick Word on Databricks Labs&lt;/H2&gt;
&lt;P&gt;If you're not familiar with Databricks Labs, it's essentially Databricks' experimental workshop—a GitHub org full of community-driven projects built by Databricks engineers and partners. These aren't official products. They don't come with SLAs or enterprise support contracts. They're tools built by practitioners to solve real problems, shared openly so others can benefit.&lt;/P&gt;
&lt;P&gt;You've probably heard of some Labs projects already: UCX for Unity Catalog migrations, DLT-META for metadata-driven pipelines, Tempo for time series. Ontos is the newest addition, and it tackles something most of us have been duct-taping together with spreadsheets and Confluence pages: business semantics.&lt;/P&gt;
&lt;DIV class="callout blue"&gt;&lt;STRONG&gt;What "Labs" really means:&lt;/STRONG&gt; These projects are provided AS-IS for exploration. No formal support, but active development and community contribution. Think of them as battle-tested tools from people who've felt the same pain you have.&lt;/DIV&gt;
&lt;H2&gt;What Ontos Actually Does&lt;/H2&gt;
&lt;P&gt;Ontos layers business context on top of Unity Catalog. It gives you a proper interface for managing the stuff that technical metadata doesn't capture:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Data Products&lt;/STRONG&gt; — Define and publish datasets as formal products with owners, SLAs, and documentation. Not just "here's a table," but "here's a curated, trustworthy asset you can build on."&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Data Contracts&lt;/STRONG&gt; — Formalize agreements between producers and consumers. What's the schema? What's the freshness guarantee? What happens when something breaks?&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Business Glossaries&lt;/STRONG&gt; — Finally, a place to define what terms actually mean. "Customer" might mean three different things across your org—now you can make that explicit.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Master Data Management&lt;/STRONG&gt; — Track canonical sources and golden records. When someone asks "which customer table is the source of truth?"—you'll have an answer.&lt;/P&gt;
&lt;P&gt;The architecture is straightforward: React frontend, FastAPI backend, deploys as a Databricks App. It talks directly to Unity Catalog APIs and stores its own metadata in PostgreSQL (or Lakebase in production).&lt;/P&gt;
&lt;H2&gt;Why This Matters&lt;/H2&gt;
&lt;P&gt;I've seen teams spend months building elaborate governance frameworks in wikis and spreadsheets, only to watch them go stale the moment someone changes a column name. The problem isn't discipline—it's that the business context lives in a completely different system than the technical reality.&lt;/P&gt;
&lt;P&gt;Ontos sits where it belongs: right next to Unity Catalog, pulling live metadata, letting you annotate it with business meaning. When a table changes, you see it. When a definition drifts, you catch it.&lt;/P&gt;
&lt;P&gt;It's not magic. It's just putting the business semantics where they should have been all along.&lt;/P&gt;
&lt;H2&gt;Getting Started&lt;/H2&gt;
&lt;P&gt;The project is fully open source under Apache 2.0. You can run it locally for development or deploy it as a Databricks App. The README is thorough—environment variables, database setup, the works.&lt;/P&gt;
&lt;P&gt;If you're on the Free Edition, remember: you get one Databricks App. Ontos could be a strong candidate for that slot if data governance is your priority.&lt;/P&gt;
&lt;DIV class="callout"&gt;&lt;STRONG&gt;Quick start:&lt;/STRONG&gt; Clone the repo, set up your &lt;CODE&gt;.env&lt;/CODE&gt; with your Databricks workspace URL and a SQL warehouse ID, run &lt;CODE&gt;yarn dev:frontend&lt;/CODE&gt; and &lt;CODE&gt;yarn dev:backend&lt;/CODE&gt;. You'll have a local instance running in minutes.&lt;/DIV&gt;
&lt;H2&gt;Go Check It Out&lt;/H2&gt;
&lt;P&gt;If you've ever wished Unity Catalog understood your business—not just your tables—Ontos is worth a look. It's early days (46 stars as I write this), but the foundation is solid and the problem it solves is real.&lt;/P&gt;
&lt;P&gt;Give it a spin. File issues if you hit snags. And if you build something cool with it, share it back with the community.&lt;/P&gt;
&lt;DIV class="footer"&gt;
&lt;P&gt;&lt;STRONG&gt;Links:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/databrickslabs/ontos" target="_blank"&gt;Ontos on GitHub&lt;/A&gt; · &lt;A href="https://github.com/databrickslabs" target="_blank"&gt;Databricks Labs&lt;/A&gt; · &lt;A href="https://www.databricks.com/learn/labs" target="_blank"&gt;Labs Project Directory&lt;/A&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Mon, 08 Dec 2025 15:55:52 GMT</pubDate>
    <dc:creator>AbhaySingh</dc:creator>
    <dc:date>2025-12-08T15:55:52Z</dc:date>
    <item>
      <title>Semantic Bridge to Unity Catalog</title>
      <link>https://community.databricks.com/t5/community-articles/semantic-bridge-to-unity-catalog/m-p/141416#M845</link>
      <description>&lt;P&gt;&lt;/P&gt;
&lt;P class="subtitle"&gt;How Ontos bridges the gap between technical metadata and business meaning&lt;/P&gt;
&lt;P&gt;Here's a scenario that might sound familiar. You've got Unity Catalog humming along—tables are registered, lineage is tracked, access controls are in place. Technically, everything's governed. But then someone from the business side asks: "What exactly does &lt;CODE&gt;customer_ltv_score&lt;/CODE&gt; mean? Who owns the definition? Is this the canonical source or is there another table I should be using?"&lt;/P&gt;
&lt;P&gt;And suddenly you realize: Unity Catalog tells you &lt;EM&gt;what&lt;/EM&gt; exists. It doesn't tell you what it &lt;EM&gt;means&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;That's the gap Ontos is designed to fill unless you are also using metric views with unity catalog.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/metric-views/" target="_blank"&gt;https://learn.microsoft.com/en-us/azure/databricks/metric-views/&lt;/A&gt;&lt;/P&gt;
&lt;H2&gt;First, a Quick Word on Databricks Labs&lt;/H2&gt;
&lt;P&gt;If you're not familiar with Databricks Labs, it's essentially Databricks' experimental workshop—a GitHub org full of community-driven projects built by Databricks engineers and partners. These aren't official products. They don't come with SLAs or enterprise support contracts. They're tools built by practitioners to solve real problems, shared openly so others can benefit.&lt;/P&gt;
&lt;P&gt;You've probably heard of some Labs projects already: UCX for Unity Catalog migrations, DLT-META for metadata-driven pipelines, Tempo for time series. Ontos is the newest addition, and it tackles something most of us have been duct-taping together with spreadsheets and Confluence pages: business semantics.&lt;/P&gt;
&lt;DIV class="callout blue"&gt;&lt;STRONG&gt;What "Labs" really means:&lt;/STRONG&gt; These projects are provided AS-IS for exploration. No formal support, but active development and community contribution. Think of them as battle-tested tools from people who've felt the same pain you have.&lt;/DIV&gt;
&lt;H2&gt;What Ontos Actually Does&lt;/H2&gt;
&lt;P&gt;Ontos layers business context on top of Unity Catalog. It gives you a proper interface for managing the stuff that technical metadata doesn't capture:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Data Products&lt;/STRONG&gt; — Define and publish datasets as formal products with owners, SLAs, and documentation. Not just "here's a table," but "here's a curated, trustworthy asset you can build on."&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Data Contracts&lt;/STRONG&gt; — Formalize agreements between producers and consumers. What's the schema? What's the freshness guarantee? What happens when something breaks?&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Business Glossaries&lt;/STRONG&gt; — Finally, a place to define what terms actually mean. "Customer" might mean three different things across your org—now you can make that explicit.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Master Data Management&lt;/STRONG&gt; — Track canonical sources and golden records. When someone asks "which customer table is the source of truth?"—you'll have an answer.&lt;/P&gt;
&lt;P&gt;The architecture is straightforward: React frontend, FastAPI backend, deploys as a Databricks App. It talks directly to Unity Catalog APIs and stores its own metadata in PostgreSQL (or Lakebase in production).&lt;/P&gt;
&lt;H2&gt;Why This Matters&lt;/H2&gt;
&lt;P&gt;I've seen teams spend months building elaborate governance frameworks in wikis and spreadsheets, only to watch them go stale the moment someone changes a column name. The problem isn't discipline—it's that the business context lives in a completely different system than the technical reality.&lt;/P&gt;
&lt;P&gt;Ontos sits where it belongs: right next to Unity Catalog, pulling live metadata, letting you annotate it with business meaning. When a table changes, you see it. When a definition drifts, you catch it.&lt;/P&gt;
&lt;P&gt;It's not magic. It's just putting the business semantics where they should have been all along.&lt;/P&gt;
&lt;H2&gt;Getting Started&lt;/H2&gt;
&lt;P&gt;The project is fully open source under Apache 2.0. You can run it locally for development or deploy it as a Databricks App. The README is thorough—environment variables, database setup, the works.&lt;/P&gt;
&lt;P&gt;If you're on the Free Edition, remember: you get one Databricks App. Ontos could be a strong candidate for that slot if data governance is your priority.&lt;/P&gt;
&lt;DIV class="callout"&gt;&lt;STRONG&gt;Quick start:&lt;/STRONG&gt; Clone the repo, set up your &lt;CODE&gt;.env&lt;/CODE&gt; with your Databricks workspace URL and a SQL warehouse ID, run &lt;CODE&gt;yarn dev:frontend&lt;/CODE&gt; and &lt;CODE&gt;yarn dev:backend&lt;/CODE&gt;. You'll have a local instance running in minutes.&lt;/DIV&gt;
&lt;H2&gt;Go Check It Out&lt;/H2&gt;
&lt;P&gt;If you've ever wished Unity Catalog understood your business—not just your tables—Ontos is worth a look. It's early days (46 stars as I write this), but the foundation is solid and the problem it solves is real.&lt;/P&gt;
&lt;P&gt;Give it a spin. File issues if you hit snags. And if you build something cool with it, share it back with the community.&lt;/P&gt;
&lt;DIV class="footer"&gt;
&lt;P&gt;&lt;STRONG&gt;Links:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/databrickslabs/ontos" target="_blank"&gt;Ontos on GitHub&lt;/A&gt; · &lt;A href="https://github.com/databrickslabs" target="_blank"&gt;Databricks Labs&lt;/A&gt; · &lt;A href="https://www.databricks.com/learn/labs" target="_blank"&gt;Labs Project Directory&lt;/A&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 08 Dec 2025 15:55:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/semantic-bridge-to-unity-catalog/m-p/141416#M845</guid>
      <dc:creator>AbhaySingh</dc:creator>
      <dc:date>2025-12-08T15:55:52Z</dc:date>
    </item>
  </channel>
</rss>

