<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reproducible ML on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/reproducible-ml/</link><description>Recent content in Reproducible ML on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 28 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/reproducible-ml/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Artifacts &amp;amp; Metadata Management</title><link>https://ai-blog.noorshomelab.dev/metadataflow-guide-2026/04-data-artifacts-metadata/</link><pubDate>Wed, 28 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/metadataflow-guide-2026/04-data-artifacts-metadata/</guid><description>&lt;h2 id="introduction-to-data-artifacts--metadata-management"&gt;Introduction to Data Artifacts &amp;amp; Metadata Management&lt;/h2&gt;
&lt;p&gt;Welcome back, future MLOps wizard! In our previous chapters, we set up our environment and got a taste of how Meta AI&amp;rsquo;s powerful new library, let&amp;rsquo;s call it &lt;code&gt;MetaMLFlow&lt;/code&gt; (a hypothetical name for Meta&amp;rsquo;s open-source dataset management library), helps us organize our datasets. But what happens after you&amp;rsquo;ve prepared your data? How do you keep track of different versions, transformations, and the models trained on them? That&amp;rsquo;s where &lt;strong&gt;Data Artifacts &amp;amp; Metadata Management&lt;/strong&gt; comes in!&lt;/p&gt;</description></item></channel></rss>