<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>MDMongoose news</title>
        <link>https://mdmongoose.example.com/news</link>
        <description>MDMongoose Blog</description>
        <lastBuildDate>Tue, 17 Nov 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[Release notes — MDMongoose 0.1]]></title>
            <link>https://mdmongoose.example.com/news/release-0-1</link>
            <guid>https://mdmongoose.example.com/news/release-0-1</guid>
            <pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[The first public release of MDMongoose. Deploy it with the bundle and run mdm_init once.]]></description>
            <content:encoded><![CDATA[<p>The first public release of MDMongoose. Deploy it with the bundle and run <code>mdm_init</code> once.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="highlights">Highlights<a href="https://mdmongoose.example.com/news/release-0-1#highlights" class="hash-link" aria-label="Direct link to Highlights" title="Direct link to Highlights" translate="no">​</a></h2>
<ul>
<li class=""><strong>One hierarchy in one Delta table</strong> (<code>MDMNodes</code>), clustered by the tree path so every branch is a
contiguous range of files.</li>
<li class=""><strong>Databricks App</strong> with a three-level hierarchy, grouped properties, action boxes and dialogs.</li>
<li class=""><strong>Edit Children</strong> grid: explode up to three levels, copy and paste with Excel, server-side sort and filters,
undo and redo, one-transaction saves.</li>
<li class=""><strong>Incremental loading</strong> from Delta tables with change data feed: AUTO CDC with expectations in the
<code>mdm_load</code> pipeline, then a set-based Spark <code>MERGE</code> of only the new changes.</li>
<li class=""><strong>Golden records</strong> with match keys, fuzzy name matching and per-property survivorship (source priority,
most recent, custom Python functions), with a dry run.</li>
<li class=""><strong>Exports</strong> to CSV and Excel from the app; materialized views, a lookup index and SCD2 history from the
<code>mdm_export</code> pipeline.</li>
<li class=""><strong>Permissions</strong> with Unity Catalog groups and Steward lists, edited in one table with a live preview.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="performance">Performance<a href="https://mdmongoose.example.com/news/release-0-1#performance" class="hash-link" aria-label="Direct link to Performance" title="Direct link to Performance" translate="no">​</a></h2>
<ul>
<li class="">Every list loads 40 rows at a time with <em>Load next 40</em>.</li>
<li class="">Visited levels and the properties of the rows on screen are cached and preloaded in batches, so navigation
is instant; the app refreshes in the background.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="demo-data">Demo data<a href="https://mdmongoose.example.com/news/release-0-1#demo-data" class="hash-link" aria-label="Direct link to Demo data" title="Direct link to Demo data" translate="no">​</a></h2>
<p>With <code>demo = "true"</code>, <code>mdm_init</code> creates 1 000 customers from three sources, 200 suppliers from two, 300
employees from Workday and Active Directory, and a six-level product hierarchy with 50 products.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="upgrading">Upgrading<a href="https://mdmongoose.example.com/news/release-0-1#upgrading" class="hash-link" aria-label="Direct link to Upgrading" title="Direct link to Upgrading" translate="no">​</a></h2>
<p>This is the first release — deploy the bundle and run <code>mdm_init</code>. See <a class="" href="https://mdmongoose.example.com/docs/deployment">Deployment</a>.</p>]]></content:encoded>
            <category>Release notes</category>
        </item>
        <item>
            <title><![CDATA[Release notes — MDMongoose 0.2]]></title>
            <link>https://mdmongoose.example.com/news/release-0-2</link>
            <guid>https://mdmongoose.example.com/news/release-0-2</guid>
            <pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Finer permissions, enum lists you build in the app, and exports you configure as nodes. Run mdm_init once]]></description>
            <content:encoded><![CDATA[<p>Finer permissions, enum lists you build in the app, and exports you configure as nodes. <strong>Run <code>mdm_init</code> once
after deploying</strong> — it upgrades the permission levels and the definitions.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="seven-permission-levels">Seven permission levels<a href="https://mdmongoose.example.com/news/release-0-2#seven-permission-levels" class="hash-link" aria-label="Direct link to Seven permission levels" title="Direct link to Seven permission levels" translate="no">​</a></h2>
<p><em>Read</em> and <em>Modify</em> are replaced by <strong>Nothing, Reader, Modifier, Supervisor, Manager, Governor</strong> and <strong>Admin</strong>.
Modifiers edit values, Supervisors lock, Managers add, move and delete, Governors decide Owner and Steward.
Every action now has a <strong>Required Level</strong> — a property of the Action node that admins can change.
<a class="" href="https://mdmongoose.example.com/docs/security">Security</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="enum-is-a-nodetype">Enum is a NodeType<a href="https://mdmongoose.example.com/news/release-0-2#enum-is-a-nodetype" class="hash-link" aria-label="Direct link to Enum is a NodeType" title="Direct link to Enum is a NodeType" translate="no">​</a></h2>
<p>Give any node the type <strong>Enum</strong> and its children become the values of a list — no SQL needed. Use it in a
NodeType as <code>Enum(&lt;list name&gt;)</code>. <a class="" href="https://mdmongoose.example.com/docs/enum-link-array">Enum, Link and Array</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="export-nodes">Export nodes<a href="https://mdmongoose.example.com/news/release-0-2#export-nodes" class="hash-link" aria-label="Direct link to Export nodes" title="Direct link to Export nodes" translate="no">​</a></h2>
<p>The <code>type_&lt;NodeType&gt;</code> views are gone. Instead, an <strong>Export node</strong> (Model › Exports) publishes a branch — the
same table as the Export dialog — as a <strong>materialized view</strong> (declared in the <code>mdm_export</code> pipeline and
refreshed incrementally), a <strong>view</strong> (created by the app when you save) or a <strong>CSV / Excel file</strong> on the
<code>exports</code> volume. A new <strong>mdm_export</strong> job refreshes them after every load and golden-record refresh.
<a class="" href="https://mdmongoose.example.com/docs/export-materialized-views">Exporting with materialized views</a> ·
<a class="" href="https://mdmongoose.example.com/docs/architecture-export">Architecture › Export</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="upgrade-notes">Upgrade notes<a href="https://mdmongoose.example.com/news/release-0-2#upgrade-notes" class="hash-link" aria-label="Direct link to Upgrade notes" title="Direct link to Upgrade notes" translate="no">​</a></h2>
<ul>
<li class=""><code>mdm_init</code> renames <em>Read</em> → <strong>Reader</strong> and <em>Modify</em> → <strong>Modifier</strong>, and turns the default
<code>users · Modify</code> grant on the root into <strong><code>users · Manager</code></strong>, so users keep adding and deleting nodes.
Review your own <em>Modify</em> grants: groups that should add or delete nodes need <strong>Manager</strong>.</li>
<li class="">Queries on <code>mdm_export.type_*</code> views must move to an Export node of type <em>Materialized view</em>.</li>
<li class="">The app needs <code>CREATE TABLE</code> on <code>mdm_export</code> for View exports; <code>mdm_init</code> grants it (or run
<code>sql/grants.sql</code>).</li>
<li class="">Redeploy the bundle before running <code>mdm_init</code>: the new <code>mdm_export</code> job and the app's <code>export-job</code> resource
come with it.</li>
</ul>]]></content:encoded>
            <category>Release notes</category>
        </item>
        <item>
            <title><![CDATA[Introducing MDMongoose — MDM without Madness]]></title>
            <link>https://mdmongoose.example.com/news/welcome</link>
            <guid>https://mdmongoose.example.com/news/welcome</guid>
            <pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Master data management usually means another platform next to your lakehouse: another database, another]]></description>
            <content:encoded><![CDATA[<p>Master data management usually means another platform next to your lakehouse: another database, another
copy of your data and another set of permissions to keep in sync. <strong>MDMongoose</strong> takes the opposite route —
it lives <em>inside</em> Databricks.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-another-mdm">Why another MDM?<a href="https://mdmongoose.example.com/news/welcome#why-another-mdm" class="hash-link" aria-label="Direct link to Why another MDM?" title="Direct link to Why another MDM?" translate="no">​</a></h2>
<p>Most of the data that master data is built from already sits in the lakehouse: ERP and CRM extracts, HR feeds,
product files. So we asked a simple question: what if the master data stayed there too?</p>
<p>MDMongoose keeps the whole hierarchy — reference data, loaded records, golden records and even its own
definitions — in <strong>one Delta table</strong>. A web app on <strong>Databricks Apps</strong> lets data stewards browse and edit it,
<strong>Spark Declarative Pipelines</strong> load source changes incrementally and publish materialized views, and
<strong>serverless jobs</strong> build the golden records. One bundle deploys everything, and it runs on Databricks Free
Edition.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-you-can-do-today">What you can do today<a href="https://mdmongoose.example.com/news/welcome#what-you-can-do-today" class="hash-link" aria-label="Direct link to What you can do today" title="Direct link to What you can do today" translate="no">​</a></h2>
<ul>
<li class="">Browse and edit one hierarchy of everything, with typed properties and structure rules.</li>
<li class="">Edit hundreds of nodes at once in the Excel-like <strong>Edit Children</strong> grid.</li>
<li class="">Load source tables incrementally from their change data feed, with data-quality expectations.</li>
<li class="">Build <strong>golden records</strong> with matching and per-property survivorship rules — and a dry run that explains
every value.</li>
<li class="">Export to CSV and Excel, or consume typed <strong>materialized views</strong> in Unity Catalog.</li>
<li class="">Control access with Unity Catalog groups.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-comes-next">What comes next<a href="https://mdmongoose.example.com/news/welcome#what-comes-next" class="hash-link" aria-label="Direct link to What comes next" title="Direct link to What comes next" translate="no">​</a></h2>
<p>On this page we will publish release notes and articles about master data management on Databricks —
hierarchy design, matching strategies and running MDM at scale. Start with the
<a class="" href="https://mdmongoose.example.com/docs/get-started">documentation</a>, and tell us what you would like to read about.</p>]]></content:encoded>
            <category>Announcements</category>
            <category>Master data management</category>
        </item>
    </channel>
</rss>