<?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: budget cuts for staff = books lost forever</title>
	<atom:link href="http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/</link>
	<description>putting the rarin back in librarian since 1999</description>
	<lastBuildDate>Sat, 11 Feb 2012 18:14:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ananke</title>
		<link>http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/comment-page-1/#comment-33605</link>
		<dc:creator>Ananke</dc:creator>
		<pubDate>Mon, 09 Oct 2006 02:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/stax/1866#comment-33605</guid>
		<description>I think the &#039;Na&#039; issue is a problem when you use common words. Because if you search for Hamlet and it isn&#039;t under H, most of the time you don&#039;t scroll down to T just in case. Particularly a problem if you rank the results in alphabetical and seperate pages (like most databases do with periodical titles) because it isn&#039;t at all intuitive. 

Searching for stuff when you know it&#039;s there is not the best way to test the useability of a search, particularly the way the results are presented.</description>
		<content:encoded><![CDATA[<p>I think the &#8216;Na&#8217; issue is a problem when you use common words. Because if you search for Hamlet and it isn&#8217;t under H, most of the time you don&#8217;t scroll down to T just in case. Particularly a problem if you rank the results in alphabetical and seperate pages (like most databases do with periodical titles) because it isn&#8217;t at all intuitive. </p>
<p>Searching for stuff when you know it&#8217;s there is not the best way to test the useability of a search, particularly the way the results are presented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Driedger</title>
		<link>http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/comment-page-1/#comment-28351</link>
		<dc:creator>Kevin Driedger</dc:creator>
		<pubDate>Fri, 29 Sep 2006 19:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/stax/1866#comment-28351</guid>
		<description>Okay, I read the article and while I do agree that poor cataloging leads to lost books, I don&#039;t think the information in the article is accurate, or maybe it isn&#039;t current, or maybe the author is a lousy catalog searcher. A keyword search of a library catalog will pick up a title whether the initial article is present or not. So, even if the Harvard library&#039;s catalog records incorrectly indexed &quot;na&quot; as the first word of many titles, a keyword search for the subsequent words would still get the title. It wouldn&#039;t work for a title browse search, but lets face it, most people do keyword searches, or if their title browse search doesn&#039;t work, they move to a keyword search. 

I just tested this out at the Harvard library catalog and titles that began &quot;na&quot; search just fine as keywords. So, yes, good cataloging is a good thing, but no, things are not as bad as this author reports (at least in this instance).</description>
		<content:encoded><![CDATA[<p>Okay, I read the article and while I do agree that poor cataloging leads to lost books, I don&#8217;t think the information in the article is accurate, or maybe it isn&#8217;t current, or maybe the author is a lousy catalog searcher. A keyword search of a library catalog will pick up a title whether the initial article is present or not. So, even if the Harvard library&#8217;s catalog records incorrectly indexed &#8220;na&#8221; as the first word of many titles, a keyword search for the subsequent words would still get the title. It wouldn&#8217;t work for a title browse search, but lets face it, most people do keyword searches, or if their title browse search doesn&#8217;t work, they move to a keyword search. </p>
<p>I just tested this out at the Harvard library catalog and titles that began &#8220;na&#8221; search just fine as keywords. So, yes, good cataloging is a good thing, but no, things are not as bad as this author reports (at least in this instance).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mariser</title>
		<link>http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/comment-page-1/#comment-28139</link>
		<dc:creator>mariser</dc:creator>
		<pubDate>Fri, 29 Sep 2006 14:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/stax/1866#comment-28139</guid>
		<description>yes, I thought this was terribly sad. and a cautionary tale; this story is &quot;the smoking gun&quot; that needs to be brought out any time an administrator/whoever argues that &quot;there is no need for a cataloger...anybody can do that copy-and-paste...&quot;  copy-cataloging should not be an excuse to not verify records

/rant</description>
		<content:encoded><![CDATA[<p>yes, I thought this was terribly sad. and a cautionary tale; this story is &#8220;the smoking gun&#8221; that needs to be brought out any time an administrator/whoever argues that &#8220;there is no need for a cataloger&#8230;anybody can do that copy-and-paste&#8230;&#8221;  copy-cataloging should not be an excuse to not verify records</p>
<p>/rant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david king</title>
		<link>http://www.librarian.net/stax/1866/budget-cuts-for-staff-books-lost-forever/comment-page-1/#comment-28136</link>
		<dc:creator>david king</dc:creator>
		<pubDate>Fri, 29 Sep 2006 14:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/stax/1866#comment-28136</guid>
		<description>Of course, a better keyword/relevenace ranked search and RFID would REALLY help alleviate this problem...

Just sayin.</description>
		<content:encoded><![CDATA[<p>Of course, a better keyword/relevenace ranked search and RFID would REALLY help alleviate this problem&#8230;</p>
<p>Just sayin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

