<?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: Elf and Privacy Issues</title>
	<atom:link href="http://meredith.wolfwater.com/wordpress/2005/12/28/elf-and-privacy-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://meredith.wolfwater.com/wordpress/2005/12/28/elf-and-privacy-issues/</link>
	<description>A librarian, writer and educator reflecting on the profession and the tools we use to serve our patrons</description>
	<lastBuildDate>Mon, 06 Feb 2012 09:11:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: casey</title>
		<link>http://meredith.wolfwater.com/wordpress/2005/12/28/elf-and-privacy-issues/comment-page-1/#comment-35574</link>
		<dc:creator>casey</dc:creator>
		<pubDate>Fri, 30 Dec 2005 07:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://meredith.wolfwater.com/wordpress/index.php/2005/12/28/elf-and-privacy-issues/#comment-35574</guid>
		<description>The SPL RSS FAQ (which, yeah, people don&#039;t read) says, &quot;RSS is a standard format, so SPL’s RSS feeds should work with any RSS reader. However, the Seattle Public Library does not support or endorse any one in particular.&quot; 

Sounds like SPL doesn&#039;t endorse any feed reader.  Now, I agree that libraries do need to take patron privacy very seriously and not place the onus on the patron, but I wonder how long it would take them to get sued if they came out and said DON&#039;T USE MY YAHOO! (or whatever site(s) are leaking personal info)?

Oh, and Ed, it&#039;s pretty primitive but SPL has the ability to share lists of stuff from the catalog.  For example:

http://catalog.spl.org/link?keys=2254173,2277882,2008743,2182664,550248&amp;name=Tunes</description>
		<content:encoded><![CDATA[<p>The SPL RSS FAQ (which, yeah, people don&#8217;t read) says, &#8220;RSS is a standard format, so SPL’s RSS feeds should work with any RSS reader. However, the Seattle Public Library does not support or endorse any one in particular.&#8221; </p>
<p>Sounds like SPL doesn&#8217;t endorse any feed reader.  Now, I agree that libraries do need to take patron privacy very seriously and not place the onus on the patron, but I wonder how long it would take them to get sued if they came out and said DON&#8217;T USE MY YAHOO! (or whatever site(s) are leaking personal info)?</p>
<p>Oh, and Ed, it&#8217;s pretty primitive but SPL has the ability to share lists of stuff from the catalog.  For example:</p>
<p><a href="http://catalog.spl.org/link?keys=2254173,2277882,2008743,2182664,550248&amp;name=Tunes" rel="nofollow">http://catalog.spl.org/link?keys=2254173,2277882,2008743,2182664,550248&amp;name=Tunes</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meredith</title>
		<link>http://meredith.wolfwater.com/wordpress/2005/12/28/elf-and-privacy-issues/comment-page-1/#comment-35429</link>
		<dc:creator>Meredith</dc:creator>
		<pubDate>Wed, 28 Dec 2005 16:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://meredith.wolfwater.com/wordpress/index.php/2005/12/28/elf-and-privacy-issues/#comment-35429</guid>
		<description>I agree, the library should try to make it as easy as possible for people to share if they want to.  I love what Seattle, AADL, and Hennepin County have done.  However, libraries really have a responsibility to educate patrons about information security issues, and not just those three I mentioned. We can&#039;t just say, &quot;well, it&#039;s Library Elf, not us who is offering these feeds&quot; and leave it at that.  Education is an important part of our mission and we are doing a terrible disservice to our patrons if we don&#039;t give them all the facts about the services they may be using -- even those outside of the library.</description>
		<content:encoded><![CDATA[<p>I agree, the library should try to make it as easy as possible for people to share if they want to.  I love what Seattle, AADL, and Hennepin County have done.  However, libraries really have a responsibility to educate patrons about information security issues, and not just those three I mentioned. We can&#8217;t just say, &#8220;well, it&#8217;s Library Elf, not us who is offering these feeds&#8221; and leave it at that.  Education is an important part of our mission and we are doing a terrible disservice to our patrons if we don&#8217;t give them all the facts about the services they may be using &#8212; even those outside of the library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Vielmetti</title>
		<link>http://meredith.wolfwater.com/wordpress/2005/12/28/elf-and-privacy-issues/comment-page-1/#comment-35428</link>
		<dc:creator>Edward Vielmetti</dc:creator>
		<pubDate>Wed, 28 Dec 2005 16:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://meredith.wolfwater.com/wordpress/index.php/2005/12/28/elf-and-privacy-issues/#comment-35428</guid>
		<description>The Ann Arbor District Library inserts warnings in a patron&#039;s RSS feed periodically about how the information in the feed might be made public if they use an aggregator.  I think that&#039;s a good approach to the problem in that it puts the news right where people can see it.

As a patron who would love to get book recommendations from the library and from other patrons, I&#039;m in favor of sharing as much as I can manage to do (knowing that there might be the occasional title I&#039;d want to keep private).  Libraries are doing themselves a disservice by not looking at the flip side of the privacy question and asking themselves &quot;how can patrons share news about really great books&quot;?  I should be able to share a reading list of good materials right out of the catalog and not have to resort to Amazon or hand-copying them into my blog to get that word out.</description>
		<content:encoded><![CDATA[<p>The Ann Arbor District Library inserts warnings in a patron&#8217;s RSS feed periodically about how the information in the feed might be made public if they use an aggregator.  I think that&#8217;s a good approach to the problem in that it puts the news right where people can see it.</p>
<p>As a patron who would love to get book recommendations from the library and from other patrons, I&#8217;m in favor of sharing as much as I can manage to do (knowing that there might be the occasional title I&#8217;d want to keep private).  Libraries are doing themselves a disservice by not looking at the flip side of the privacy question and asking themselves &#8220;how can patrons share news about really great books&#8221;?  I should be able to share a reading list of good materials right out of the catalog and not have to resort to Amazon or hand-copying them into my blog to get that word out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

