<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>EAD on Dressing Up Data</title>
    <link>https://dressing-up-data.netlify.app/tags/ead/</link>
    <description>Recent content in EAD on Dressing Up Data</description>
    <generator>Hugo -- gohugo.io</generator>
    <copyright>Copyright © 2008–2018, Steve Francia and the Hugo Authors; all rights reserved.</copyright>
    <lastBuildDate>Tue, 17 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dressing-up-data.netlify.app/tags/ead/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Seeking Validation?</title>
      <link>https://dressing-up-data.netlify.app/post/2026-03-17-seeking-validation/</link>
      <pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://dressing-up-data.netlify.app/post/2026-03-17-seeking-validation/</guid>
      <description>
        
          
            The time has come for me to reckon with EAD.
EAD, or Encoded Archival Description, has been in my life for a couple of years now. During grad school, I did a lot of experimenting with converting the hierarchical, tag-based XML data of EAD into tabular data. One of the outputs of this was a paper in which I visualized metadata from a Smithsonian Folk Life archival collection as a spatial network, and analyzed the geographical spread of various genre tags assigned to audio recordings.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
