<?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: Complexity Gives Us Job Security</title>
	<atom:link href="http://dbl.lishost.org/blog/2010/03/25/complexity-gives-us-job-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://dbl.lishost.org/blog/2010/03/25/complexity-gives-us-job-security/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:51:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark</title>
		<link>http://dbl.lishost.org/blog/2010/03/25/complexity-gives-us-job-security/comment-page-1/#comment-40927</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 20 May 2010 18:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/?p=587#comment-40927</guid>
		<description>WorldCat Local certainly goes a long way in accomplishing the goals of simplicity in service and coverage. It&#039;s not perfect, but our first year with it has transformed bibliographic instruction. No longer do we have to run the gamut of catalogs and databases, especially for underclassmen. We&#039;re also totally redesigning our website, stripping out everything that is not essential for the users. It also uses their terminology: goodbye, &quot;interlibrary loan,&#039; hello &quot;borrow from another library.&quot;</description>
		<content:encoded><![CDATA[<p>WorldCat Local certainly goes a long way in accomplishing the goals of simplicity in service and coverage. It&#8217;s not perfect, but our first year with it has transformed bibliographic instruction. No longer do we have to run the gamut of catalogs and databases, especially for underclassmen. We&#8217;re also totally redesigning our website, stripping out everything that is not essential for the users. It also uses their terminology: goodbye, &#8220;interlibrary loan,&#8217; hello &#8220;borrow from another library.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Mabe</title>
		<link>http://dbl.lishost.org/blog/2010/03/25/complexity-gives-us-job-security/comment-page-1/#comment-40184</link>
		<dc:creator>James Mabe</dc:creator>
		<pubDate>Mon, 19 Apr 2010 23:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/?p=587#comment-40184</guid>
		<description>I agree with the above, and would add that it&#039;s not in the interest of the companies providing these products and services to improve them. Particularly in public libraries, the costs of ILS implementation are always so high (especially when coming out of a set operating budget) and the level of competition remains so low that vendors know they can provide middling to poor products without having to worry about losing customers to competitors. Furthermore, not only are information professionals frequently unaware of the state of the art (as the above comment rightfully states), but often it is true that front-line staff and IT departments fail to cooperate to create the best scenario for information seekers. More than merely a matter of emotional investment in the complex interface, it is also true that a significant financial investment has taken place, and public libraries cannot help but consider the costs they have already accrued to implement (however poorly or incompletely) their ILS and online resources. Additionally, libraries do not by coincidence operate much the same way they have for the last half-century; the emotional connection to The Way We Do Things runs far wider than merely memorizing keyboard commands.</description>
		<content:encoded><![CDATA[<p>I agree with the above, and would add that it&#8217;s not in the interest of the companies providing these products and services to improve them. Particularly in public libraries, the costs of ILS implementation are always so high (especially when coming out of a set operating budget) and the level of competition remains so low that vendors know they can provide middling to poor products without having to worry about losing customers to competitors. Furthermore, not only are information professionals frequently unaware of the state of the art (as the above comment rightfully states), but often it is true that front-line staff and IT departments fail to cooperate to create the best scenario for information seekers. More than merely a matter of emotional investment in the complex interface, it is also true that a significant financial investment has taken place, and public libraries cannot help but consider the costs they have already accrued to implement (however poorly or incompletely) their ILS and online resources. Additionally, libraries do not by coincidence operate much the same way they have for the last half-century; the emotional connection to The Way We Do Things runs far wider than merely memorizing keyboard commands.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andromeda</title>
		<link>http://dbl.lishost.org/blog/2010/03/25/complexity-gives-us-job-security/comment-page-1/#comment-39847</link>
		<dc:creator>Andromeda</dc:creator>
		<pubDate>Tue, 30 Mar 2010 16:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/?p=587#comment-39847</guid>
		<description>Personally?  I think a lot of it&#039;s ignorance.

I was taking a class on ILSes last term.  And it seemed like at least once a week I&#039;d mention something to my husband, a software engineer (who coincidentally works for one of those companies which makes things easy to search, though he didn&#039;t at the time), and he&#039;d say something like...&quot;Wait.  Your software doesn&#039;t &lt;I&gt;do&lt;/I&gt; that?  Why?  It&#039;s, like, two days of a sophomore CS major&#039;s time!&quot;  And I&#039;d say...really?  that easy?

I think most librarians, and patrons, are unaware of how hard or easy it is to implement a lot of features.  When we don&#039;t know they&#039;re easy -- when we don&#039;t know they&#039;re not merely last year&#039;s but last &lt;I&gt;decade&#039;s&lt;/I&gt; technology -- we don&#039;t push vendors to implement them.  If we don&#039;t demand them, who&#039;s going to supply them?

I mean, I also think you&#039;re right that there&#039;s a (perceived) value to (some) librarians in being gatekeepers (all the parentheses are because users are simply flocking to easier things while the gatekeepers handwring about how, well, at least their resources are &lt;I&gt;better&lt;/I&gt;).  And I think people (not just librarians) who have mastered a complex interface have an emotional investment in it which makes change hard.  But mostly I think librarians don&#039;t demand good interfaces because we don&#039;t know much about them, and we don&#039;t know what the technology can offer us, and, well, we&#039;re getting what we demand.</description>
		<content:encoded><![CDATA[<p>Personally?  I think a lot of it&#8217;s ignorance.</p>
<p>I was taking a class on ILSes last term.  And it seemed like at least once a week I&#8217;d mention something to my husband, a software engineer (who coincidentally works for one of those companies which makes things easy to search, though he didn&#8217;t at the time), and he&#8217;d say something like&#8230;&#8221;Wait.  Your software doesn&#8217;t <i>do</i> that?  Why?  It&#8217;s, like, two days of a sophomore CS major&#8217;s time!&#8221;  And I&#8217;d say&#8230;really?  that easy?</p>
<p>I think most librarians, and patrons, are unaware of how hard or easy it is to implement a lot of features.  When we don&#8217;t know they&#8217;re easy &#8212; when we don&#8217;t know they&#8217;re not merely last year&#8217;s but last <i>decade&#8217;s</i> technology &#8212; we don&#8217;t push vendors to implement them.  If we don&#8217;t demand them, who&#8217;s going to supply them?</p>
<p>I mean, I also think you&#8217;re right that there&#8217;s a (perceived) value to (some) librarians in being gatekeepers (all the parentheses are because users are simply flocking to easier things while the gatekeepers handwring about how, well, at least their resources are <i>better</i>).  And I think people (not just librarians) who have mastered a complex interface have an emotional investment in it which makes change hard.  But mostly I think librarians don&#8217;t demand good interfaces because we don&#8217;t know much about them, and we don&#8217;t know what the technology can offer us, and, well, we&#8217;re getting what we demand.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

