<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Transformation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/data-transformation/</link>
    <description>Recent content in Data-Transformation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/data-transformation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Metadata Transformation Platforms: Catmandu vs Metafacture vs OpenRefine</title>
      <link>https://www.pistack.xyz/posts/2026-06-15-metadata-transformation-catmandu-metafacture-openrefine/</link>
      <pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-15-metadata-transformation-catmandu-metafacture-openrefine/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Libraries, archives, museums, and research institutions deal with an enormous variety of metadata formats — MARC, Dublin Core, EAD, METS, MODS, JSON-LD, and dozens more. Converting between these formats, cleaning messy data, and enriching records at scale requires specialized metadata transformation platforms. Unlike generic ETL tools, metadata-focused platforms understand library-specific standards and provide domain-specific transformations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
