<?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: world usability day is tomorrow</title>
	<atom:link href="http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/</link>
	<description>putting the rarin back in librarian since 1999</description>
	<lastBuildDate>Sat, 11 Feb 2012 18:14:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: don warner saklad</title>
		<link>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/comment-page-1/#comment-122831</link>
		<dc:creator>don warner saklad</dc:creator>
		<pubDate>Sun, 30 Nov 2008 07:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/?p=2520#comment-122831</guid>
		<description>Our city public library&#039;s website and library buildings fail when it comes to usability. Navigating Boston Public Library buildings&#039; floor, departments, collections, curatorial experts sets up BPLusers for repetitive back and forth catch 22s. Add to that the lack in a good customers services approach, routine supervision and routine training. Our BPL website has features that are not universal, not compatible will all operating systems. When feedback is offered it&#039;s received dismissively, deflected by BPLers, wrongfully perceived as adversarial. Communications failures results in usability failures.</description>
		<content:encoded><![CDATA[<p>Our city public library&#8217;s website and library buildings fail when it comes to usability. Navigating Boston Public Library buildings&#8217; floor, departments, collections, curatorial experts sets up BPLusers for repetitive back and forth catch 22s. Add to that the lack in a good customers services approach, routine supervision and routine training. Our BPL website has features that are not universal, not compatible will all operating systems. When feedback is offered it&#8217;s received dismissively, deflected by BPLers, wrongfully perceived as adversarial. Communications failures results in usability failures.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Auntie Nanuuq</title>
		<link>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/comment-page-1/#comment-121090</link>
		<dc:creator>Auntie Nanuuq</dc:creator>
		<pubDate>Thu, 13 Nov 2008 19:04:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/?p=2520#comment-121090</guid>
		<description>The statement on what Technology should be is great! 

&quot;Technology should enhance our lives, not add to our stress or cause danger through poor design or poor quality. It is our duty to ensure that this technology is effective, efficient, satisfying and reliable, and that it is usable by all people.&quot; 

It is a shame that SirsiDynix only provides enhancement for the public who use our online catalogs, but stress through poor design and difficulty of use for the library staff. 

One would hope, when spending boodles of cash on a new automated library system &amp; public catalog, that ease of use would be considered for both sets of users!  It is embarrassing that after 5 months of having SirsiDynix in our library, that I am still unable to successfully place a hold on materials for a customer using the staff&#039;s program on the first try!

&quot;Human error will occur if technology is not both easy-to-use and easy-to-understand. We need to reduce human error that results from bad design.&quot;

Thank-you for the article.</description>
		<content:encoded><![CDATA[<p>The statement on what Technology should be is great! </p>
<p>&#8220;Technology should enhance our lives, not add to our stress or cause danger through poor design or poor quality. It is our duty to ensure that this technology is effective, efficient, satisfying and reliable, and that it is usable by all people.&#8221; </p>
<p>It is a shame that SirsiDynix only provides enhancement for the public who use our online catalogs, but stress through poor design and difficulty of use for the library staff. </p>
<p>One would hope, when spending boodles of cash on a new automated library system &amp; public catalog, that ease of use would be considered for both sets of users!  It is embarrassing that after 5 months of having SirsiDynix in our library, that I am still unable to successfully place a hold on materials for a customer using the staff&#8217;s program on the first try!</p>
<p>&#8220;Human error will occur if technology is not both easy-to-use and easy-to-understand. We need to reduce human error that results from bad design.&#8221;</p>
<p>Thank-you for the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey Bisson</title>
		<link>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/comment-page-1/#comment-121086</link>
		<dc:creator>Casey Bisson</dc:creator>
		<pubDate>Thu, 13 Nov 2008 14:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarian.net/?p=2520#comment-121086</guid>
		<description>But this year&#039;s theme is transportation, focusing on the environmental aspects. I can see a connection between that and usability, I guess, but the the WUD website doesn&#039;t seem to complete the circle.</description>
		<content:encoded><![CDATA[<p>But this year&#8217;s theme is transportation, focusing on the environmental aspects. I can see a connection between that and usability, I guess, but the the WUD website doesn&#8217;t seem to complete the circle.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

