https://ellipsys-bi.com/en/tags/metadata-management/Metadata ManagementHugoBlox Kit (https://hugoblox.com)en-USThu, 02 Jul 2026 00:00:00 +0000https://ellipsys-bi.com/media/logo.svghttps://ellipsys-bi.com/en/tags/metadata-management/https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/Thu, 02 Jul 2026 00:00:00 +0000https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/<p><strong style="color:#C00000;">{openAudit}</strong> lets you browse data lineage through its Mosaïc web portal, but the consolidated metadata can also be published to various data catalogs on the market, which often have significant limitations when it comes to data lineage. The benefit is having a single tool for optimal data governance.</p> <p>The data lineage is reconstructed in the <strong style="color:#C00000;">{openAudit}</strong> technical repository, then exposed to data catalogs via dedicated connectors.</p> <p>This architecture makes it possible to decouple the data lineage collection and reconstruction mechanisms from the exposure layer used by governance teams.</p> <blockquote class="border-l-4 border-neutral-300 dark:border-neutral-600 pl-4 italic text-neutral-600 dark:text-neutral-400 my-6"> <p><strong>Key point:</strong> the technical repository stays independent from the target catalog. The collection and lineage-reconstruction (and connection) mechanisms don&rsquo;t depend on the data catalog in use.</p> </blockquote> <h2 id="architecture">Architecture</h2> <p> <figure > <div class="flex justify-center "> <div class="w-full" > <img alt="img-big" srcset="https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/data-lineage-alimentation-data-catalogues-1-en_hu_cbb841d43bbf559e.webp 320w, https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/data-lineage-alimentation-data-catalogues-1-en_hu_7a240380fc93dde0.webp 480w, https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/data-lineage-alimentation-data-catalogues-1-en_hu_3ee369225894186e.webp 760w" sizes="(max-width: 480px) 100vw, (max-width: 768px) 90vw, (max-width: 1024px) 80vw, 760px" src="https://ellipsys-bi.com/en/ressources/data-lineage-principes/data-lineage-alimentation-data-catalogues/data-lineage-alimentation-data-catalogues-1-en_hu_cbb841d43bbf559e.webp" width="760" height="417" loading="lazy" data-zoomable /></div> </div></figure> </p> <p>The collected metadata is consolidated in the <strong>oA.mdb</strong> columnar database after processing by the <strong>oA.Job</strong> engine.</p> <p>The central repository notably contains:</p> <ul> <li>Field-level data lineage.</li> <li>Usage data.</li> <li>Associated governance information, where applicable.</li> </ul> <p>The catalogs are then fed from this single repository via exposure connectors independent of the data catalog solutions in use.</p> <h2 id="exposure-connectors">Exposure connectors</h2> <p>The connectors handle:</p> <ul> <li>Automated publication of the lineage.</li> <li>Continuous synchronization.</li> <li>Restriction management.</li> <li>Support for the various Workspaces.</li> </ul> <p>Data lineage exposure can be complete or partial depending on the display capabilities of the target catalog, keeping in mind that the data lineage produced upstream is itself available at field level.</p> <blockquote class="border-l-4 border-neutral-300 dark:border-neutral-600 pl-4 italic text-neutral-600 dark:text-neutral-400 my-6"> <p><strong>Result:</strong> catalogs only consume the consolidated metadata, not the original technical sources.</p> </blockquote> <h2 id="supported-catalogs">Supported catalogs</h2> <p>The available connectors currently support the following data catalogs:</p> <ul> <li>DataGalaxy</li> <li>Zeenea</li> <li>Collibra</li> </ul> <h2 id="usage-management">Usage management</h2> <p>When audit logs are available, observed usage is integrated into the technical repository and then exposed to the catalog.</p> <p>This lets users distinguish:</p> <ul> <li>&ldquo;Live&rdquo; flows, consumed by tools or queried.</li> <li>Flows — and therefore objects — that see no consumption (often more than 80% of the total).</li> </ul> <blockquote class="border-l-4 border-neutral-300 dark:border-neutral-600 pl-4 italic text-neutral-600 dark:text-neutral-400 my-6"> <p><strong>Typical use case:</strong> enrich the data catalog with usage information to identify objects that are candidates for rationalization or decommissioning.</p> </blockquote> <script> (function () { // Hide the "Last updated on" date and the Author block on Resources // pages: these aren't blog posts (no date/byline). function hide() { document.querySelectorAll("time.mt-12.mb-8").forEach(function (el) { el.style.display = "none"; }); document.querySelectorAll("div.flex.pt-12.pb-4").forEach(function (el) { if (el.querySelector('img[src*="/media/authors/"]')) { el.style.display = "none"; } }); // Extra safety net: also hide the social sharing row and any container // linked to the author card, matched semantically rather than by class // name (more robust to theme updates). var shareHrefPatterns = [ "twitter.com/intent", "x.com/intent", "facebook.com/sharer", "linkedin.com/sharing", "wa.me/", "api.whatsapp.com", "mailto:?" ]; document.querySelectorAll("a[href]").forEach(function (a) { var href = a.getAttribute("href") || ""; if (shareHrefPatterns.some(function (p) { return href.indexOf(p) !== -1; })) { a.style.display = "none"; } }); document.querySelectorAll('a[href="https://ellipsys-bi.com/authors/me/"]').forEach(function (a) { var el = a.closest("div.flex") || a.parentElement; if (el) el.style.display = "none"; }); } document.addEventListener("DOMContentLoaded", hide); })(); </script>