<?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: The Failure of Middleware, Part 7: OAI and Google Scholar</title>
	<atom:link href="http://meredith.wolfwater.com/wordpress/2005/04/07/the-failure-of-middleware-part-7-oai-and-google-scholar/feed/" rel="self" type="application/rss+xml" />
	<link>http://meredith.wolfwater.com/wordpress/2005/04/07/the-failure-of-middleware-part-7-oai-and-google-scholar/</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: Meredith</title>
		<link>http://meredith.wolfwater.com/wordpress/2005/04/07/the-failure-of-middleware-part-7-oai-and-google-scholar/comment-page-1/#comment-1714</link>
		<dc:creator>Meredith</dc:creator>
		<pubDate>Sun, 10 Apr 2005 01:33:03 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-1714</guid>
		<description>I agree that great things are being developed right now to make library middleware more user-centered. I&#039;ve certainly been very impressed with many of OCLC&#039;s recent projects.  But I think if we can&#039;t change librarians&#039; thinking about searching and the catalog, it will be much more difficult to implement these great solutions. I know I can be cynical about vendors sometimes, but I do think we librarians share the blame for the lack of innovation.</description>
		<content:encoded><![CDATA[<p>I agree that great things are being developed right now to make library middleware more user-centered. I&#8217;ve certainly been very impressed with many of OCLC&#8217;s recent projects.  But I think if we can&#8217;t change librarians&#8217; thinking about searching and the catalog, it will be much more difficult to implement these great solutions. I know I can be cynical about vendors sometimes, but I do think we librarians share the blame for the lack of innovation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Childress</title>
		<link>http://meredith.wolfwater.com/wordpress/2005/04/07/the-failure-of-middleware-part-7-oai-and-google-scholar/comment-page-1/#comment-1706</link>
		<dc:creator>Eric Childress</dc:creator>
		<pubDate>Thu, 07 Apr 2005 17:23:54 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-1706</guid>
		<description>A very well-written and thoughtful series of posts. You mention RedLightGreen and OAIster as
useful search channels, and I agree. But it should be pointed out that libraries are working
to surface their resources to users through the search engines (OCLC&#039;s Open WorldCat, for
example, http://www.oclc.org/worldcat/open) and that libraries, local system vendors, and 
other library-related organizations are building and releasing web services/service-oriented
architecture (SOA) offerings from RSS feeds to various modular components. In short, more
and better middleware is arriving daily. Cheers, Eric.</description>
		<content:encoded><![CDATA[<p>A very well-written and thoughtful series of posts. You mention RedLightGreen and OAIster as<br />
useful search channels, and I agree. But it should be pointed out that libraries are working<br />
to surface their resources to users through the search engines (OCLC&#8217;s Open WorldCat, for<br />
example, <a href="http://www.oclc.org/worldcat/open)" rel="nofollow">http://www.oclc.org/worldcat/open)</a> and that libraries, local system vendors, and<br />
other library-related organizations are building and releasing web services/service-oriented<br />
architecture (SOA) offerings from RSS feeds to various modular components. In short, more<br />
and better middleware is arriving daily. Cheers, Eric.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

