<?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: Next Generation Library Systems</title>
	<atom:link href="http://scholarlypublishing.org/jpwilkin/archives/7/feed" rel="self" type="application/rss+xml" />
	<link>http://scholarlypublishing.org/jpwilkin/archives/7</link>
	<description>John's blog on libraries, library technology, and pizza</description>
	<lastBuildDate>Sun, 03 Jan 2010 16:01:13 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wire &#187; Thank you, John Wilkins</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-100</link>
		<dc:creator>wire &#187; Thank you, John Wilkins</dc:creator>
		<pubDate>Fri, 11 Jan 2008 17:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-100</guid>
		<description>[...] I was catching up on Lorcan Dempsey&#8217;s thoughts before attending his talks at KU today and tomorrow.&#160; Lorcan, thanks for pointing me to John Wilkins&#8217; blog - really more essay than blog.&#160; While reading John&#8217;s salient and well-structured thoughts on metasearch and library systems, I find myself nodding and thinking &#8220;exactly&#8221;.&#160; &#8220;We must not try to do what the network can do for us&#8221;.&#160; Read on&#8230;. [...]</description>
		<content:encoded><![CDATA[<p>[...] I was catching up on Lorcan Dempsey&#8217;s thoughts before attending his talks at KU today and tomorrow.&nbsp; Lorcan, thanks for pointing me to John Wilkins&#8217; blog &#8211; really more essay than blog.&nbsp; While reading John&#8217;s salient and well-structured thoughts on metasearch and library systems, I find myself nodding and thinking &#8220;exactly&#8221;.&nbsp; &#8220;We must not try to do what the network can do for us&#8221;.&nbsp; Read on&#8230;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tito Sierra</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-41</link>
		<dc:creator>Tito Sierra</dc:creator>
		<pubDate>Thu, 06 Dec 2007 03:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-41</guid>
		<description>I have noticed a tendency towards premature optimization in many library systems and standards.  How can one optimize a system before a user has had an opportunity to use the system? I believe a better approach is to start small and grow your system based on continual feedback from your users. This requires a willingness to experiment, take risks, and sometimes fail. Though with an iterative approach the costs of failure are small in comparison to the costs of elaborately designed architectures that seem to become irrelevant too quickly.</description>
		<content:encoded><![CDATA[<p>I have noticed a tendency towards premature optimization in many library systems and standards.  How can one optimize a system before a user has had an opportunity to use the system? I believe a better approach is to start small and grow your system based on continual feedback from your users. This requires a willingness to experiment, take risks, and sometimes fail. Though with an iterative approach the costs of failure are small in comparison to the costs of elaborately designed architectures that seem to become irrelevant too quickly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Investing our resources where they count... &#124; TheoLib</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-35</link>
		<dc:creator>Investing our resources where they count... &#124; TheoLib</dc:creator>
		<pubDate>Wed, 21 Nov 2007 01:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-35</guid>
		<description>[...] Wilkin&#039;s post about the Next Generation Library Systems nicely states the principle and its corollary. We need to develop ways to make our data available [...]</description>
		<content:encoded><![CDATA[<p>[...] Wilkin&#8217;s post about the Next Generation Library Systems nicely states the principle and its corollary. We need to develop ways to make our data available [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpwilkin</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-34</link>
		<dc:creator>jpwilkin</dc:creator>
		<pubDate>Tue, 20 Nov 2007 03:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-34</guid>
		<description>Re opening data to anyone, including ourselves, I think you&#039;re absolutely right about this.  Considering this is also the thrust of Buzzy&#039;s question, I think I should make clear that I was using Google as an example, a sort of metonymy that&#039;s probably problematic considering our work with Google here at Michigan.  I&#039;d hoped that that was clear by the label for this first principle and the couple of opening sentences.  It clearly wasn&#039;t.</description>
		<content:encoded><![CDATA[<p>Re opening data to anyone, including ourselves, I think you&#8217;re absolutely right about this.  Considering this is also the thrust of Buzzy&#8217;s question, I think I should make clear that I was using Google as an example, a sort of metonymy that&#8217;s probably problematic considering our work with Google here at Michigan.  I&#8217;d hoped that that was clear by the label for this first principle and the couple of opening sentences.  It clearly wasn&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpwilkin</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-33</link>
		<dc:creator>jpwilkin</dc:creator>
		<pubDate>Tue, 20 Nov 2007 03:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-33</guid>
		<description>Hey, Buzzy.  There are definitely strategies for doing this in ways that don&#039;t lock us into betting that Google will continue to be the dominant online venue!  When we work to make information discoverable, we should do it in such a way that &lt;strong&gt;any&lt;/strong&gt; information provider can provide competitive discovery services.  OAI is a perfect example of the approach we can take, and the work that Herbert Van de Sompel and others have done to extend OAI might just be the answer in this area.  Let&#039;s not fear dominance, though.  It&#039;s not that we bet on Google&#039;s dominance, but rather that we need to take advantage of their (and anyone else&#039;s) dominance because that&#039;s where the users are.  In short, there are lots of ways to avoid being locked in, &lt;strong&gt;and&lt;/strong&gt; we should recognize and take advantage of dominance wherever we find it.</description>
		<content:encoded><![CDATA[<p>Hey, Buzzy.  There are definitely strategies for doing this in ways that don&#8217;t lock us into betting that Google will continue to be the dominant online venue!  When we work to make information discoverable, we should do it in such a way that <strong>any</strong> information provider can provide competitive discovery services.  OAI is a perfect example of the approach we can take, and the work that Herbert Van de Sompel and others have done to extend OAI might just be the answer in this area.  Let&#8217;s not fear dominance, though.  It&#8217;s not that we bet on Google&#8217;s dominance, but rather that we need to take advantage of their (and anyone else&#8217;s) dominance because that&#8217;s where the users are.  In short, there are lots of ways to avoid being locked in, <strong>and</strong> we should recognize and take advantage of dominance wherever we find it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Ashton</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-32</link>
		<dc:creator>Andy Ashton</dc:creator>
		<pubDate>Mon, 19 Nov 2007 18:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-32</guid>
		<description>Just a comment on the whole piece - or rather, a comment on the state of library technology writ large...

Although I come from a relatively small institution without a significant research mandate, I&#039;m still fairly shocked at the lack of discussion and awareness among rank-and-file librarians, and within library &quot;scholarship&quot;, regarding many of the core issues you bring up in the piece.  

At a recent symposium on &quot;Next-Generation Catalogs&quot;, it became clear that the overwhelming majority of librarians believe that their Next-Gen system will be a product purchased from a traditional ILS vendor, the difference being that it looks and acts more like Amazon.  And maybe they&#039;re right.   However, the dialog about web services, open repositories - or even real discussions about a wholesale shift from MARC for standard library collections - is still the domain of researchers and developers.  The most promising library-oriented projects that I&#039;m aware of are often emerging from outside of libraries.

As you mention at one point in this piece, the most open, accessible  services are useful without metadata that people want to use, but I have yet to see a broad-based, universal discussion among librarians to that end.  

Unfortunately, so many libraries don&#039;t make room for participation in community-driven development projects, and so remain largely outside the sphere from which their future systems may be developed, and largely ignorant of the issues surrounding them.  We risk continuing to be passive consumers of interfaces - a role that doesn&#039;t argue well for librarians&#039; long-term relevance.</description>
		<content:encoded><![CDATA[<p>Just a comment on the whole piece &#8211; or rather, a comment on the state of library technology writ large&#8230;</p>
<p>Although I come from a relatively small institution without a significant research mandate, I&#8217;m still fairly shocked at the lack of discussion and awareness among rank-and-file librarians, and within library &#8220;scholarship&#8221;, regarding many of the core issues you bring up in the piece.  </p>
<p>At a recent symposium on &#8220;Next-Generation Catalogs&#8221;, it became clear that the overwhelming majority of librarians believe that their Next-Gen system will be a product purchased from a traditional ILS vendor, the difference being that it looks and acts more like Amazon.  And maybe they&#8217;re right.   However, the dialog about web services, open repositories &#8211; or even real discussions about a wholesale shift from MARC for standard library collections &#8211; is still the domain of researchers and developers.  The most promising library-oriented projects that I&#8217;m aware of are often emerging from outside of libraries.</p>
<p>As you mention at one point in this piece, the most open, accessible  services are useful without metadata that people want to use, but I have yet to see a broad-based, universal discussion among librarians to that end.  </p>
<p>Unfortunately, so many libraries don&#8217;t make room for participation in community-driven development projects, and so remain largely outside the sphere from which their future systems may be developed, and largely ignorant of the issues surrounding them.  We risk continuing to be passive consumers of interfaces &#8211; a role that doesn&#8217;t argue well for librarians&#8217; long-term relevance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Ashton</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-31</link>
		<dc:creator>Andy Ashton</dc:creator>
		<pubDate>Mon, 19 Nov 2007 18:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-31</guid>
		<description>Great piece, thanks for sharing it.  My only comment on this section, which is dead-on, is that I don&#039;t see the discovery services such as those implemented by Google et al to be the inevitable points-of-discovery.  At the risk of arguing the same point: the more open and ubiquitous web services become, the less discovery becomes reliant on a single provider.  Instead of opening our data to Google or Amazon, I see emerging projects opening data to anyone, including ourselves.  This makes the point-of-access less defined and encourages a more fluid interchange of data via network services.  If library systems open up, provided the metadata is there and accessible, academic networks can be just as valuable as Google in discovery. Obviously we have a long way to go, but it is encouraging to see a bunch of community-driven projects popping up that seem to be embracing this idea.</description>
		<content:encoded><![CDATA[<p>Great piece, thanks for sharing it.  My only comment on this section, which is dead-on, is that I don&#8217;t see the discovery services such as those implemented by Google et al to be the inevitable points-of-discovery.  At the risk of arguing the same point: the more open and ubiquitous web services become, the less discovery becomes reliant on a single provider.  Instead of opening our data to Google or Amazon, I see emerging projects opening data to anyone, including ourselves.  This makes the point-of-access less defined and encourages a more fluid interchange of data via network services.  If library systems open up, provided the metadata is there and accessible, academic networks can be just as valuable as Google in discovery. Obviously we have a long way to go, but it is encouraging to see a bunch of community-driven projects popping up that seem to be embracing this idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buzzy</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/7/comment-page-1#comment-30</link>
		<dc:creator>Buzzy</dc:creator>
		<pubDate>Mon, 19 Nov 2007 18:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/7#comment-30</guid>
		<description>Question: Are there strategies for putting &quot;all things online in a way that Google can discover&quot; that don&#039;t lock us into betting that Google will continue to be the dominant online venue?</description>
		<content:encoded><![CDATA[<p>Question: Are there strategies for putting &#8220;all things online in a way that Google can discover&#8221; that don&#8217;t lock us into betting that Google will continue to be the dominant online venue?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
