<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data on Roy Rosenzweig Center for History and New Media</title>
    <link>https://hugo.chnm.gmu.edu/tags/data/</link>
    <description>Recent content in Data on Roy Rosenzweig Center for History and New Media</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hugo.chnm.gmu.edu/tags/data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>South Asia Collections at The Met: A Preliminary Computational Look</title>
      <link>https://hugo.chnm.gmu.edu/blog/exploring-south-asia-at-the-met-through-data/</link>
      <pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://hugo.chnm.gmu.edu/blog/exploring-south-asia-at-the-met-through-data/</guid>
      <description>&lt;p&gt;Originally published at &lt;a href=&#34;https://www.deepthimurali.com/art-history-and-data/south-asia-at-the-met&#34;&gt;https://www.deepthimurali.com/art-history-and-data/south-asia-at-the-met&lt;/a&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Museum metadata is messy metadata (and sometimes, also, just messy in non-computational ways.) But museum metadata is also historical archive that scholars and the public alike ignore.&lt;/p&gt;&#xA;&lt;p&gt;Every object in a museum collection arrives with a story attached — a donor&amp;rsquo;s name, a date, a department assignment, a classification. Individually, these are administrative details: the bureaucratic residue of how an object got from somewhere else to a vitrine, a storage shelf, or a database entry. But at scale, across thousands of objects and more than a century of acquisitions, these details become historical data. They become a record of &lt;em&gt;how&lt;/em&gt; an institution decided what South Asia was, who got to decide that, and when those decisions were made.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
