<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Abriam Downing</title>
    <description>The latest articles on DEV Community by Abriam Downing (@abriam_downing_7589a04b2f).</description>
    <link>https://dev.to/abriam_downing_7589a04b2f</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4183240%2Ff65b90c8-825e-4999-8730-a2fa9dcf025d.png</url>
      <title>DEV Community: Abriam Downing</title>
      <link>https://dev.to/abriam_downing_7589a04b2f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abriam_downing_7589a04b2f"/>
    <language>en</language>
    <item>
      <title>Duplicate CSV rows: start with exact matches, then review</title>
      <dc:creator>Abriam Downing</dc:creator>
      <pubDate>Tue, 13 Oct 2026 23:52:21 +0000</pubDate>
      <link>https://dev.to/abriam_downing_7589a04b2f/duplicate-csv-rows-start-with-exact-matches-then-review-36k</link>
      <guid>https://dev.to/abriam_downing_7589a04b2f/duplicate-csv-rows-start-with-exact-matches-then-review-36k</guid>
      <description>&lt;p&gt;Disclosure: I create Rowstead, a browser-local CSV tool. This guide was prepared with AI assistance.&lt;/p&gt;

&lt;h2&gt;
  
  
  A shared name is not enough
&lt;/h2&gt;

&lt;p&gt;Two people can have the same name. One person can have several addresses. Removing a row because its name looks familiar can discard useful information. Start with complete-row matches and keep a review copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Spaces can hide a match
&lt;/h2&gt;

&lt;p&gt;A leading or trailing space can make two otherwise matching cells different. If trimming is appropriate for your data, review that change before checking for duplicate rows again. Some values contain meaningful spaces, so choose cleanup deliberately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep a decision trail
&lt;/h2&gt;

&lt;p&gt;Record why you kept or removed a record. For uncertain rows, mark them for review rather than guessing. Keep the source file and your decision log together.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what your tool actually does
&lt;/h2&gt;

&lt;p&gt;An exact duplicate-row check does not infer identity or merge people. Email syntax checks do not establish deliverability or marketing permission. Keep those distinctions visible in your import workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review before exporting
&lt;/h2&gt;

&lt;p&gt;Compare original and cleaned previews. Save the source, export a reviewed copy, then test a small import in the destination.&lt;/p&gt;

&lt;p&gt;I use these review principles in &lt;a href="https://rowstead.pages.dev/" rel="noopener noreferrer"&gt;Rowstead&lt;/a&gt;. The practical lesson applies whichever CSV tool you choose.&lt;/p&gt;

</description>
      <category>data</category>
      <category>productivity</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
