<?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: Two to six for Mr. Lorello</title>
	<atom:link href="http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/feed/" rel="self" type="application/rss+xml" />
	<link>http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/</link>
	<description>Thinking critically about the archival impulse</description>
	<lastBuildDate>Fri, 30 Sep 2011 16:58:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Heather</title>
		<link>http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/comment-page-1/#comment-101</link>
		<dc:creator>Heather</dc:creator>
		<pubDate>Mon, 06 Oct 2008 14:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/#comment-101</guid>
		<description>There&#039;s a lot of press when a patron like E. Forbes Smiley steals from a library, and rightly so. But when someone charged with protecting the public trust is doing it-- and apparently has been doing it since 1997-- how can we prepare for that? Obviously I&#039;d rather not have examples of wrongdoing like this, but when it does happen, we need to be using this within the profession as a cautionary tale. How can we further enforce that? I&#039;m not sure. But it seems to me that most of our security precautions are based on keeping outsiders out of the collections, not keeping collections inside. Perhaps there needs to be more discussion about a shift in security perspectives.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a lot of press when a patron like E. Forbes Smiley steals from a library, and rightly so. But when someone charged with protecting the public trust is doing it&#8211; and apparently has been doing it since 1997&#8211; how can we prepare for that? Obviously I&#8217;d rather not have examples of wrongdoing like this, but when it does happen, we need to be using this within the profession as a cautionary tale. How can we further enforce that? I&#8217;m not sure. But it seems to me that most of our security precautions are based on keeping outsiders out of the collections, not keeping collections inside. Perhaps there needs to be more discussion about a shift in security perspectives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell D. James, CA</title>
		<link>http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/comment-page-1/#comment-94</link>
		<dc:creator>Russell D. James, CA</dc:creator>
		<pubDate>Sun, 05 Oct 2008 22:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://archivesfound.com/2008/10/03/two-to-six-for-mr-lorello/#comment-94</guid>
		<description>Maybe this will serve as an example we can use when trying to enforce the ethical guidelines of our profession?  We sure need such examples.</description>
		<content:encoded><![CDATA[<p>Maybe this will serve as an example we can use when trying to enforce the ethical guidelines of our profession?  We sure need such examples.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

