<?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: Isn&#8217;t Evergreen just for consortia with hundreds of libraries?</title>
	<atom:link href="http://evergreen-ils.org/blog/?feed=rss2&#038;p=120" rel="self" type="application/rss+xml" />
	<link>http://evergreen-ils.org/blog/?p=120</link>
	<description>The blog for Evergreen open-source library software</description>
	<lastBuildDate>Fri, 20 Nov 2009 15:58:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://evergreen-ils.org/blog/?p=120&#038;cpage=1#comment-41589</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Mon, 11 Feb 2008 22:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://open-ils.org/blog/?p=120#comment-41589</guid>
		<description>As far as resource consumption, that&#039;s an easy worry to answer. I believe 100% that hardware affordable to the tiniest library can run EG. 

What&#039;s harder to answer is the &#039;functional&#039; perspective---is EG appropriate for the workflow of a smaller or even very small library?  Supporting the kind of workflow they need, not being overly complex and putting lots of configuration options and/or screens and interfaces in the way that they&#039;d never need.  That Kent County library will be demonstrating this with an actual implementation will be huge. If I were a small library considering EG, I&#039;d call up Kent County to get their perspective. And once Kent has implemented and has life proof in front of your eyes, I&#039;d call them up and hear how happy they were with it (and the answer will hopefully be &#039;very&#039;).</description>
		<content:encoded><![CDATA[<p>As far as resource consumption, that&#8217;s an easy worry to answer. I believe 100% that hardware affordable to the tiniest library can run EG. </p>
<p>What&#8217;s harder to answer is the &#8216;functional&#8217; perspective&#8212;is EG appropriate for the workflow of a smaller or even very small library?  Supporting the kind of workflow they need, not being overly complex and putting lots of configuration options and/or screens and interfaces in the way that they&#8217;d never need.  That Kent County library will be demonstrating this with an actual implementation will be huge. If I were a small library considering EG, I&#8217;d call up Kent County to get their perspective. And once Kent has implemented and has life proof in front of your eyes, I&#8217;d call them up and hear how happy they were with it (and the answer will hopefully be &#8216;very&#8217;).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
