<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Importing actors	</title>
	<atom:link href="https://blog.museum-digital.org/2023/11/22/importing-actors/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.museum-digital.org/2023/11/22/importing-actors/</link>
	<description>A blog on museum-digital and the broader digitization of museum work.</description>
	<lastBuildDate>Mon, 27 Nov 2023 14:10:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Joshua Ramon Enslin		</title>
		<link>https://blog.museum-digital.org/2023/11/27/automatically-enforcing-consistent-naming-of-places/</link>

		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Mon, 27 Nov 2023 14:10:12 +0000</pubDate>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3922#comment-5623</guid>

					<description><![CDATA[Last week I wrote about how new actors find their way into museum-digital’s controlled vocabulary for actors during imports. One of the first steps detailed&#8230;]]></description>
			<content:encoded><![CDATA[<p>Last week I wrote about how new actors find their way into museum-digital’s controlled vocabulary for actors during imports. One of the first steps detailed&hellip;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
