<?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"
	>
<channel>
	<title>Comments for Thoughts from Carl Grant, a long-time participant in library automation.</title>
	<atom:link href="http://www.care-affiliates.com/thoughts/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.care-affiliates.com/thoughts</link>
	<description></description>
	<pubDate>Sun, 06 Jul 2008 03:46:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Executive summary - Why the myths about open source are just that&#8230; by Open Sesame &#187; Blog Archive &#187; Open Source Myths</title>
		<link>http://www.care-affiliates.com/thoughts/archives/36#comment-774</link>
		<dc:creator>Open Sesame &#187; Blog Archive &#187; Open Source Myths</dc:creator>
		<pubDate>Mon, 30 Jun 2008 11:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/36#comment-774</guid>
		<description>[...] Carl Grant points us to a [...]</description>
		<content:encoded><![CDATA[<p>[...] Carl Grant points us to a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Moving from &#8220;bolt-on OPAC&#8217;s&#8221; to &#8220;plug-in OPAC&#8217;s&#8221; by Panlibus &#187; Blog Archive &#187; SirsiDynix get fuzzy over search</title>
		<link>http://www.care-affiliates.com/thoughts/archives/34#comment-655</link>
		<dc:creator>Panlibus &#187; Blog Archive &#187; SirsiDynix get fuzzy over search</dc:creator>
		<pubDate>Fri, 20 Jun 2008 11:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/34#comment-655</guid>
		<description>[...] early days in this market as Carl Grant, who was also on the Library 2.0 Gang this month, is saying we need to evolve from bolt-on towards [...]</description>
		<content:encoded><![CDATA[<p>[...] early days in this market as Carl Grant, who was also on the Library 2.0 Gang this month, is saying we need to evolve from bolt-on towards [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why OpenTranslators(TM) are important. by ecorrado.us &#187; Zealots in the library</title>
		<link>http://www.care-affiliates.com/thoughts/archives/24#comment-102</link>
		<dc:creator>ecorrado.us &#187; Zealots in the library</dc:creator>
		<pubDate>Fri, 25 Jan 2008 17:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/24#comment-102</guid>
		<description>[...] on the #code4lib IRC channel) Carl Grant&#8217;s recent response to Dan Chudnov&#8217;s response to Carl&#8217;s earlier post. The way I interpret the conversation is a basic disagreement about what it means to be a member of [...]</description>
		<content:encoded><![CDATA[<p>[...] on the #code4lib IRC channel) Carl Grant&#8217;s recent response to Dan Chudnov&#8217;s response to Carl&#8217;s earlier post. The way I interpret the conversation is a basic disagreement about what it means to be a member of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why OpenTranslators(TM) are important. by Response to OpenTranslators post &#187; Federated Search Blog</title>
		<link>http://www.care-affiliates.com/thoughts/archives/24#comment-98</link>
		<dc:creator>Response to OpenTranslators post &#187; Federated Search Blog</dc:creator>
		<pubDate>Sun, 20 Jan 2008 21:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/24#comment-98</guid>
		<description>[...] a comment on my recent OpenTranslators announcement raises questions post. The comment refers to an in-depth response that Grant posted on his blog. I&#8217;m writing this post to bring attention to Grant&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] a comment on my recent OpenTranslators announcement raises questions post. The comment refers to an in-depth response that Grant posted on his blog. I&#8217;m writing this post to bring attention to Grant&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An important question to ask. by wett516</title>
		<link>http://www.care-affiliates.com/thoughts/archives/12#comment-42</link>
		<dc:creator>wett516</dc:creator>
		<pubDate>Wed, 24 Oct 2007 10:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/12#comment-42</guid>
		<description>The "factory" model also explains why vendors also start looking to a "next generation" system after a while. The sales people want something shiny and new to sell. The finance people look at sales revenue and maintenance revenue and fall for the idea of new sales being able to increase the bottom line. 

The big question may whether the current library vendor service models can make a company profitable in the long run. Vendors will have to compete over services not features. This should force them to be more creative in this area. As the cost structure for services is smaller than up-front license and maintenance fee lock-in, the successful vendor will have to come up with more service offerings. They will have to adapt more quickly as well.

The change in the vendor service model may be true, whether libraries use OSS or not. (The real question for us is whether they use an OSS ILS, because they are OSS.) The next generation of librarians seems to be more comfortable with technology and changing technology. There expectations are going to be much higher technology partners. Software development has reached a new kind of plateau. (http://www.readwriteweb.com/archives/the_future_of_software_development.php) The future doesn't depend copying the newest type of infrastructure, but on assembling parts from a cornucopia of technologies. 

Is there a perfect storm in the works?</description>
		<content:encoded><![CDATA[<p>The &#8220;factory&#8221; model also explains why vendors also start looking to a &#8220;next generation&#8221; system after a while. The sales people want something shiny and new to sell. The finance people look at sales revenue and maintenance revenue and fall for the idea of new sales being able to increase the bottom line. </p>
<p>The big question may whether the current library vendor service models can make a company profitable in the long run. Vendors will have to compete over services not features. This should force them to be more creative in this area. As the cost structure for services is smaller than up-front license and maintenance fee lock-in, the successful vendor will have to come up with more service offerings. They will have to adapt more quickly as well.</p>
<p>The change in the vendor service model may be true, whether libraries use OSS or not. (The real question for us is whether they use an OSS ILS, because they are OSS.) The next generation of librarians seems to be more comfortable with technology and changing technology. There expectations are going to be much higher technology partners. Software development has reached a new kind of plateau. (http://www.readwriteweb.com/archives/the_future_of_software_development.php) The future doesn&#8217;t depend copying the newest type of infrastructure, but on assembling parts from a cornucopia of technologies. </p>
<p>Is there a perfect storm in the works?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The spin begins! by ddorman</title>
		<link>http://www.care-affiliates.com/thoughts/archives/10#comment-37</link>
		<dc:creator>ddorman</dc:creator>
		<pubDate>Sun, 07 Oct 2007 04:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/10#comment-37</guid>
		<description>All worth sayng and well said.  I would just add that with all the BS being put out about Open Source, it is worth reminding everyone that Open Source is a type of license under which software is distributed, and it is this license that gives OS software its advantages.  If a vendor insists that you sign a proprietary license in order to use it's software, you won't get the advantages of OS--it's that simple.</description>
		<content:encoded><![CDATA[<p>All worth sayng and well said.  I would just add that with all the BS being put out about Open Source, it is worth reminding everyone that Open Source is a type of license under which software is distributed, and it is this license that gives OS software its advantages.  If a vendor insists that you sign a proprietary license in order to use it&#8217;s software, you won&#8217;t get the advantages of OS&#8211;it&#8217;s that simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The spin begins! by wett516</title>
		<link>http://www.care-affiliates.com/thoughts/archives/10#comment-34</link>
		<dc:creator>wett516</dc:creator>
		<pubDate>Fri, 05 Oct 2007 11:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/10#comment-34</guid>
		<description>You make some great points, but I have two more--quality and collaboration.

Quality is another important benefit. The fact that the source code is available will mean that are few bugs, better security and better design.  It will be looked at by any number of very smart people that will be able to praise and criticize the actual code. This peer review, like peer review in journals, is an extra layer of quality assurance.

Collaboration is the other benefit that I see. The collaboration that I think about goes beyond the development community. It is the wider openness that is part of open source software. No one has to sign a non-disclosure agreement to use it. All of those things that make the whole product can be shared and built upon. Documentation, training materials and presentations also have licenses that promote sharing and building upon. Developers of products that interact with another system can study the API in detail to make a seamless connection. The product is so much more than a particular software package.</description>
		<content:encoded><![CDATA[<p>You make some great points, but I have two more&#8211;quality and collaboration.</p>
<p>Quality is another important benefit. The fact that the source code is available will mean that are few bugs, better security and better design.  It will be looked at by any number of very smart people that will be able to praise and criticize the actual code. This peer review, like peer review in journals, is an extra layer of quality assurance.</p>
<p>Collaboration is the other benefit that I see. The collaboration that I think about goes beyond the development community. It is the wider openness that is part of open source software. No one has to sign a non-disclosure agreement to use it. All of those things that make the whole product can be shared and built upon. Documentation, training materials and presentations also have licenses that promote sharing and building upon. Developers of products that interact with another system can study the API in detail to make a seamless connection. The product is so much more than a particular software package.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A symphony out of tune:  when companies go deaf.. by Sebastian Hammer</title>
		<link>http://www.care-affiliates.com/thoughts/archives/6#comment-2</link>
		<dc:creator>Sebastian Hammer</dc:creator>
		<pubDate>Wed, 04 Jul 2007 17:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.care-affiliates.com/thoughts/archives/6#comment-2</guid>
		<description>I find it particularly ironic that these changes in the industry take place at a time when libraries and their suppliers more than ever need to be nimble-footed and innovative to keep up with the challenges of the changing information landscape, changes in people's use of information, etc.

Based on my own experiences (which clearly are biased), I would expect a growing counter-trend involving libraries that take charge of their own destiny, implement innovative solutions, and in turn challenge established vendors to improve their products. Small software companies have a role to play here, but library schools are increasingly churning out "librarian-geeks" who are keen to experiment and challenge preconceptions about technology -- just look at some of the fiery debate around MARC vs. alternative data models. Add to this that service-based architectures, open APIs and high-level development tools bring application development into the hands of more and more people, and you have an exciting mix.

These are really exciting times. Don't get me wrong... if librarians don't step up, they could find themselves going the way of the old-school travel agents in the age of Orbitz &#38; co.. but my sense is that they *do* step up, and the vendors will either do their part, or they are the ones who'll become irrelevant.

--Sebastian</description>
		<content:encoded><![CDATA[<p>I find it particularly ironic that these changes in the industry take place at a time when libraries and their suppliers more than ever need to be nimble-footed and innovative to keep up with the challenges of the changing information landscape, changes in people&#8217;s use of information, etc.</p>
<p>Based on my own experiences (which clearly are biased), I would expect a growing counter-trend involving libraries that take charge of their own destiny, implement innovative solutions, and in turn challenge established vendors to improve their products. Small software companies have a role to play here, but library schools are increasingly churning out &#8220;librarian-geeks&#8221; who are keen to experiment and challenge preconceptions about technology &#8212; just look at some of the fiery debate around MARC vs. alternative data models. Add to this that service-based architectures, open APIs and high-level development tools bring application development into the hands of more and more people, and you have an exciting mix.</p>
<p>These are really exciting times. Don&#8217;t get me wrong&#8230; if librarians don&#8217;t step up, they could find themselves going the way of the old-school travel agents in the age of Orbitz &amp; co.. but my sense is that they *do* step up, and the vendors will either do their part, or they are the ones who&#8217;ll become irrelevant.</p>
<p>&#8211;Sebastian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
