<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>librarian.net &#187; libtypos</title>
	<atom:link href="http://www.librarian.net/tag/libtypos/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarian.net</link>
	<description>putting the rarin back in librarian since 1999</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:37:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>errors, on fixing</title>
		<link>http://www.librarian.net/stax/3005/errors-on-fixing/</link>
		<comments>http://www.librarian.net/stax/3005/errors-on-fixing/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 17:58:59 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[googlebooksearch]]></category>
		<category><![CDATA[libtypos]]></category>
		<category><![CDATA[typos]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/3005/errors-on-fixing/</guid>
		<description><![CDATA[I read with interest this blog post over on Freedom to Tinker about the Google Book Search folks talking about finding and fixing errors in their giant catalog, metadata errors especially. The conversation seems to have largely started at this post on LanguageLog and gotten more interesting with follow-up comments from folks at Google. One [...]]]></description>
			<content:encoded><![CDATA[<p>I read with interest <a href="http://www.freedom-to-tinker.com/blog/felten/finding-and-fixing-errors-googles-book-catalog">this blog post over on Freedom to Tinker</a> about the Google Book Search folks talking about finding and fixing errors in their giant catalog, metadata errors especially. The conversation seems to have largely started at <a href="http://languagelog.ldc.upenn.edu/nll/?p=1701">this post on LanguageLog</a> and gotten more interesting with <a href="http://languagelog.ldc.upenn.edu/nll/?p=1701#comment-41758">follow-up comments from folks at Google</a>. One of the things we have all learned in libraryland is that the ability to trawl through our data with computers means that we can <a href="http://www.eric.ed.gov/ERICWebPortal/custom/portlets/recordDetails/detailmini.jsp?_nfpb=true&#038;_&#038;ERICExtSearch_SearchValue_0=EJ448943&#038;ERICExtSearch_SearchType_0=no&#038;accno=EJ448943">find errors</a> that might have otherwise stayed buried for years, or perhaps forever. Of course computers also help us <a href="http://librarytypos.blogspot.com/">create these errors</a> in the first place.<br />
<blockquote>What&#8217;s most interesting to me is a seeming difference in mindset between critics like Nunberg on the one hand, and Google on the other. Nunberg thinks of Google&#8217;s metadata catalog as a fixed product that has some (unfortunately large) number of errors, whereas Google sees the catalog as a work in progress, subject to continual improvement. Even calling Google&#8217;s metadata a &#8220;catalog&#8221; seems to connote a level of completion and immutability that Google might not assert. An electronic &#8220;card catalog&#8221; can change every day &#8212; a good thing if the changes are strict improvements such as error fixes &#8212; in a way that a traditional card catalog wouldn&#8217;t.</p></blockquote>
<p>Note: thanks to people who let me know that one link was wrong, and that I managed to typo both &#8220;computers&#8221; and &#8220;interesting&#8221; in this post.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/3005/errors-on-fixing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>blog: typo of the day</title>
		<link>http://www.librarian.net/stax/1882/blog-typo-of-the-day/</link>
		<comments>http://www.librarian.net/stax/1882/blog-typo-of-the-day/#comments</comments>
		<pubDate>Thu, 19 Oct 2006 01:33:00 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[blogz]]></category>
		<category><![CDATA[blogs]]></category>
		<category><![CDATA[libtypos]]></category>
		<category><![CDATA[typo]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1882</guid>
		<description><![CDATA[Typo of the Day, highlighting one word each day from the list of thousands found by the members of the forum LIBTYPOS-L. More information about Terry Ballard&#8217;s typographical errors in library databases project can be found on his website.]]></description>
			<content:encoded><![CDATA[<p><a href="http://typooftheday.blogspot.com/">Typo of the Day</a>, highlighting one word each day from the list of thousands found by the members of the forum <a href="http://groups.yahoo.com/group/Libtypos-L/">LIBTYPOS-L</a>. More information about <a href="http://faculty.quinnipiac.edu/libraries/tballard/typoscomplete.html">Terry Ballard&#8217;s typographical errors in library databases</a> project can be found on his website.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1882/blog-typo-of-the-day/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

