<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Record-Linkage on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/record-linkage/</link>
    <description>Recent content in Record-Linkage on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/record-linkage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Entity Resolution &amp; Record Linkage: Dedupe vs Splink vs Record Linkage</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-self-hosted-entity-resolution-dedupe-splink-recordlinkage/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-self-hosted-entity-resolution-dedupe-splink-recordlinkage/</guid>
      <description>&lt;h2 id=&#34;why-entity-resolution-matters-for-self-hosted-data-infrastructure&#34;&gt;Why Entity Resolution Matters for Self-Hosted Data Infrastructure&lt;/h2&gt;&#xA;&lt;p&gt;Every organization accumulating data across multiple sources eventually faces the same problem: duplicate records. A customer appears in your CRM as &amp;ldquo;John Smith,&amp;rdquo; your billing system as &amp;ldquo;J. Smith,&amp;rdquo; and your support ticket system as &amp;ldquo;Jonathan Smith.&amp;rdquo; Without entity resolution, these three records remain disconnected, leading to fragmented analytics, duplicate communications, and missed cross-sell opportunities.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
