<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>librarian.net &#187; ui</title>
	<atom:link href="http://www.librarian.net/tag/ui/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarian.net</link>
	<description>putting the rarin back in librarian since 1999</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:37:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>research-based usability</title>
		<link>http://www.librarian.net/stax/3338/research-based-usability/</link>
		<comments>http://www.librarian.net/stax/3338/research-based-usability/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 21:20:39 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[userexperience]]></category>

		<guid isPermaLink="false">http://www.librarian.net/?p=3338</guid>
		<description><![CDATA[People sometimes think that saying something is more &#8220;usable&#8221; is a way of saying that you like using it better. And then they&#8217;ll reply that maybe they like using it some other way and you&#8217;re at a stalemate. In point of fact, usability is testable and quantifiable. There are a lot of places you can [...]]]></description>
			<content:encoded><![CDATA[<p>People sometimes think that saying something is more &#8220;usable&#8221; is a way of saying that you like using it better. And then they&#8217;ll reply that maybe they like using it some other way and you&#8217;re at a stalemate. In point of fact, usability is testable and quantifiable. There are a lot of places you can go to read about research-based usability, things that work for most people. I just got this link <a href="http://twitter.com/TheLiB/status/24603642729">from Twitter</a> today: <a href="http://sixrevisions.com/usabilityaccessibility/10-usability-tips-based-on-research-studies/">10 Usability Tips Based on Research Studies</a>. For people who want a bunch more stuff like this, I highly recommend Usability.gov&#8217;s <a href="http://www.usability.gov/guidelines/guidelines_book.pdf">Research-Based Web Design &#038; Usability Guidelines</a> (pdf, 21MB ) which are not only great reading but they&#8217;re government documents, so free to repurpose and republish.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/3338/research-based-usability/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>just to make sure we&#8217;re all on the same page here</title>
		<link>http://www.librarian.net/stax/2875/just-to-make-sure-were-all-on-the-same-page-here/</link>
		<comments>http://www.librarian.net/stax/2875/just-to-make-sure-were-all-on-the-same-page-here/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 23:27:12 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[ie]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/?p=2875</guid>
		<description><![CDATA[&#8220;A team from Google interviewed dozens of people in Times Square the other day, asking a simple question: What&#8217;s a browser? This was in an effort to understand and improve the customer experience of Google&#8217;s own browser, called Chrome. Turns out that over 90% of the people interviewed could not describe what a Web browser [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;A team from Google interviewed dozens of people in Times Square the other day, asking a simple question: What&#8217;s a browser? This was in an effort to understand and improve the customer experience of Google&#8217;s own browser, called Chrome.</p>
<p>Turns out that over 90% of the people interviewed could not describe what a Web browser is.&#8221;</p>
<p>Don&#8217;t believe me? <a href="http://pleaseenjoy.com/project.php?cat=4&#038;subcat=&#038;pid=131&#038;navpoint=0">Watch the video</a>. Granted, this comes from Google, but while we&#8217;re all being &#8220;blah blah Firefox, etc&#8221; there are many people who just see what happens when you &#8220;click the e&#8221; and go forward from there.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/2875/just-to-make-sure-were-all-on-the-same-page-here/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>world usability day is tomorrow</title>
		<link>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/</link>
		<comments>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 17:17:58 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[events]]></category>
		<category><![CDATA[holidays]]></category>
		<category><![CDATA[interfacedesign]]></category>
		<category><![CDATA[tek]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/?p=2520</guid>
		<description><![CDATA[If you&#8217;re into the whole usability idea &#8212; and more and more our interfaces to technology are all we have when interacting wiht the goods, services and government in our lives &#8212; then you might like to know that World Usability Day is tomorrow. I&#8217;ll noodle around a bit looking at my own websites and [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re into the whole usability idea &#8212; and more and more our interfaces to technology are all we have when interacting wiht the goods, services and government in our lives &#8212; then you might like to know that <a href="http://worldusabilityday.org/">World Usability Day is tomorrow</a>. I&#8217;ll noodle around a bit looking at my own websites and I suggest that you and your libraries do the same.<br />
<blockquote>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. This is particularly important for people with disabilities, because technology can enhance their lives, letting them fully participate in work, social and civic experiences. Human error is a misnomer. Technology should be developed knowing that human beings have certain limitations. 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.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/2520/world-usability-day-is-tomorrow/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>ALA finally hiring Usability Officer</title>
		<link>http://www.librarian.net/stax/2177/ala-finally-hiring-usability-officer/</link>
		<comments>http://www.librarian.net/stax/2177/ala-finally-hiring-usability-officer/#comments</comments>
		<pubDate>Fri, 26 Oct 2007 00:59:25 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[ala]]></category>
		<category><![CDATA[jobs]]></category>
		<category><![CDATA[shifty]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/2177/ala-finally-hiring-usability-officer/</guid>
		<description><![CDATA[You can get 75K plus decent benefits to be a usability officer at ALA. They say &#8220;senior&#8221; but to the best of my knowledge there aren&#8217;t any other usability officers there currently. I&#8217;m not sure where officer actually comes from, maybe some ALA-er can explain? In any case, if I were the Usability Officer after [...]]]></description>
			<content:encoded><![CDATA[<p>You can get 75K plus decent benefits to be a <a href="https://cs.ala.org/jobs/viewjobs.cfm#372">usability officer at ALA</a>. They say &#8220;senior&#8221; but to the best of my knowledge there aren&#8217;t any other usability officers there currently. I&#8217;m not sure where officer actually comes from, maybe some ALA-er can explain? In any case, if I were the Usability Officer after I changed the job listings to not spell Website with a capital W, I would ask very specifically what this requirement in the ad means.<br />
<blockquote>The ability to work in a team environment and between two universes of Information Technology and Librarianship is essential in order to maintain an outcome-oriented, global vision.</p></blockquote>
<p> I&#8217;m curious why those are deemed to be two universes instead of, say, two moons orbiting around one big planet of helping people do the things they want to do and go where they want to go. I&#8217;m sure <a href="http://theshiftedlibrarian.com/archives/2007/10/24/heres-hoping-usability-becomes-institutionalized-within-ala.html">Jenny is asking the same questions</a>. I hope they find someone, but I wonder what affect that person will be able to have on the in-process-for-many-years-already website redesign?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/2177/ala-finally-hiring-usability-officer/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>my trip to Seattle</title>
		<link>http://www.librarian.net/stax/2103/my-trip-to-seattle/</link>
		<comments>http://www.librarian.net/stax/2103/my-trip-to-seattle/#comments</comments>
		<pubDate>Thu, 02 Aug 2007 13:27:43 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[libraries]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[centralbranch]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[flickr]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[publiclibrary]]></category>
		<category><![CDATA[seattle]]></category>
		<category><![CDATA[seattlepubliclibrary]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/2103/my-trip-to-seattle/</guid>
		<description><![CDATA[I was in Seattle over the weekend. Sorry I didn&#8217;t call you. I went to a wedding and then got a terrible cold and spent the last day and a half on my friend&#8217;s couch reading comic books until flying home on a red eye the day before yesterday. I am recovered now, mostly. The [...]]]></description>
			<content:encoded><![CDATA[<p>I was in Seattle over the weekend. Sorry I didn&#8217;t call you. I went to a wedding and then got a terrible cold and spent the last day and a half on my friend&#8217;s couch reading comic books until flying home on a red eye the day before yesterday. I am recovered now, mostly. The one thing on my to do list was to see the new library. When I left Seattle four years ago, it was just a hole in the ground and a loose frame but not yet open to the public. I had really liked the old library &#8212; though understood why it needed updating &#8212; and I even liked the temporary library. I can&#8217;t say the same for the new library.</p>
<p>Now, there are many great things about the new library. I connected to the wifi/internet no problem. All the people I asked for advice and directions were super friendly and helpful. I liked having the option to get a cup of coffee and have a dozen interesting places to hang out with it. The place is fun to look at and explore. I enjoyed getting to pore through bound volumes of old periodicals that were right there on the shelves. The online catalog has finally improved to the point where it&#8217;s easy to use and makes a fair amount of sense; at SPL in particular that was not always true.</p>
<p>However, I saw a real disconnect beween the lovely outside and grand entry spaces to the library, plus a few other very design-y areas, and the rest of the building. Materials were hard to find. VERY hard to find. Signage was abysmal, often just laserprinted pieces of paper, sometimes laminated and sometimes not. Doors to areas that may have been public were forbidding and unwelcoming. There weren&#8217;t enough elevators. There weren&#8217;t enough bathrooms. There wasn&#8217;t a comfortable place to sit in the entire building. There were lots of &#8220;dead spaces&#8221; that, because of architecture, couldn&#8217;t really be used for anything and they were collecting dust. The lighting was bad. Stack areas were dim and narrow. The teen area seemed like an afterthought. Bizarre display areas with a table and some books on it were in the middle of vast open areas. Most of the place felt like it was too big and then the stacks felt too crowded and I had to climb around people working to find things. Shelvers shut down the entire &#8220;spiral&#8221; concept with booktrucks. The writer&#8217;s area in this library is a shadow of the glorious writers room in the old downtown building where I had a desk briefly.</p>
<p>Did I think it was going to be different? Maybe a little. I left Seattle specifically because its idea of progress and mine were fundamentally at odds and I didn&#8217;t enjoy the destabilizing effect of a city always under construction and didn&#8217;t get enough from the things that were eventually constructed. This library looks like it was built for a bookless future where we get all of our information from the internet and the digital realm. For now, we&#8217;ll just keep the books on hand because people will bitch if they don&#8217;t get to read them, but they&#8217;re no longer the reason for the library, and they&#8217;re no longer honored and appreciated as the things we love and build libraries to house.</p>
<p><a href="http://flickr.com/photos/iamthebestartist/sets/72157601150868558/">My small photoset of the Seattle Public Library is here</a>.<br />
<strong><br />
update</strong>: I was pointed to <a href="http://lists.webjunction.org/wjlists/publib/2007-August/108927.html">a PUBLIB posting</a> by a librarian who was at SPL quite recently who makes many of the same points that I do in different ways.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/2103/my-trip-to-seattle/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>usability for library websites and services &#8211; UMich</title>
		<link>http://www.librarian.net/stax/1962/usability-for-library-websites-and-services-umich/</link>
		<comments>http://www.librarian.net/stax/1962/usability-for-library-websites-and-services-umich/#comments</comments>
		<pubDate>Wed, 31 Jan 2007 15:48:39 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[umich]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1962</guid>
		<description><![CDATA[The Usability Working Group of the University of Michigan University Library has a new website up which aims to &#8220;provide open access to our reports and working documents in order to share our findings with the University of Michigan Libraries as well as the community-at-large.&#8221; [web4lib]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.lib.umich.edu/usability/">Usability Working Group of the University of Michigan University Library</a> has a new website up which aims to &#8220;provide open access to our reports and working documents in order to share our findings with the University of Michigan Libraries as well as the community-at-large.&#8221; <small>[<a href="http://permalink.gmane.org/gmane.education.web4lib/7504">web4lib</a>]</small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1962/usability-for-library-websites-and-services-umich/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ALA Website Usability Survey</title>
		<link>http://www.librarian.net/stax/1850/ala-website-usability-survey/</link>
		<comments>http://www.librarian.net/stax/1850/ala-website-usability-survey/#comments</comments>
		<pubDate>Sun, 10 Sep 2006 17:40:39 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[ala]]></category>
		<category><![CDATA[requests]]></category>
		<category><![CDATA[survey]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1850</guid>
		<description><![CDATA[Please take the ALA Website Usability Survey. Please be honest. Jenny has included the text of a letter from ALA&#8217;s Executive Director explaning the rationale behind the survey. Even though I think this is too little way too late &#8212; maybe this should have beern done before the last redesign? &#8212; it&#8217;s still an attempt [...]]]></description>
			<content:encoded><![CDATA[<p>Please take the <a href="http://www.ala.org/ala/ourassociation/alawebsiteresources/uasurveystart.htm">ALA Website Usability Survey</a>. Please be honest. Jenny has included <a href="http://www.theshiftedlibrarian.com/archives/2006/09/06/ala_website_usability_survey.html">the text of a letter from ALA&#8217;s Executive Director</a> explaning the rationale behind the survey. Even though I think this is too little way too late &#8212; maybe this should have beern done before the last redesign? &#8212; it&#8217;s still an attempt to right wrongs. Give them a chance, take the survey.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1850/ala-website-usability-survey/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SPL&#8217;s signage woes</title>
		<link>http://www.librarian.net/stax/1848/spls-signage-woes/</link>
		<comments>http://www.librarian.net/stax/1848/spls-signage-woes/#comments</comments>
		<pubDate>Sat, 09 Sep 2006 16:59:46 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[libraries]]></category>
		<category><![CDATA[signs]]></category>
		<category><![CDATA[spl]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1848</guid>
		<description><![CDATA[I&#8217;ve talked before about Seattle Public&#8217;s newish Big Beautiful Library, and others have mentioned the weird juxtaposition of amazing architecture with crummy laser-printed signage or post-it signage. It&#8217;s no surprise that you can have cleaner lines and more striking architecture without little notes everyplace saying &#8220;this way to the restroom&#8221; but those are the choices [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve talked before about Seattle Public&#8217;s newish Big Beautiful Library, and others have mentioned the weird juxtaposition of amazing architecture with <a href="http://flickr.com/photos/doublegrande/150637993/">crummy</a> <a href="http://www.flickr.com/photos/tags/tempsigns/">laser-printed signage</a> or <a href="http://flickr.com/photos/peterkaminski/5444932/">post-it signage</a>. It&#8217;s no surprise that you can have cleaner lines and more striking architecture without little notes everyplace saying &#8220;this way to the restroom&#8221; but those are the choices we have to make as librarians. Now it looks like <a href="http://seattlepi.nwsource.com/local/283819_library05.html">Seattle is finally paying someone to fix their sign problem</a>. <small>[thanks carolyn]</small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1848/spls-signage-woes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>ALA claims to be doing web site usability survey.</title>
		<link>http://www.librarian.net/stax/1830/ala-claims-to-be-doing-web-site-usability-survey/</link>
		<comments>http://www.librarian.net/stax/1830/ala-claims-to-be-doing-web-site-usability-survey/#comments</comments>
		<pubDate>Thu, 24 Aug 2006 21:05:30 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[ala]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[website]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1830</guid>
		<description><![CDATA[No it&#8217;s not The Onion, it&#8217;s true. &#8220;You may be aware that we are currently conducting a usability assessment of our ALA website.&#8221;]]></description>
			<content:encoded><![CDATA[<p>No it&#8217;s not The Onion, it&#8217;s true. &#8220;You may be aware that we are currently <a href="http://lp-web.ala.org:8000/guest/archives/ALACOUN/log0608/msg00025.html">conducting a usability assessment of our ALA website</a>.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1830/ala-claims-to-be-doing-web-site-usability-survey/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>this is broken: brief story of me</title>
		<link>http://www.librarian.net/stax/1821/this-is-broken-a-brief-story-of-me/</link>
		<comments>http://www.librarian.net/stax/1821/this-is-broken-a-brief-story-of-me/#comments</comments>
		<pubDate>Mon, 14 Aug 2006 13:27:54 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[books]]></category>
		<category><![CDATA[thisisbroken]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1821</guid>
		<description><![CDATA[Libraries, sometimes when you stick those barcode labels on the front of your books, you obscure information on the cover, sometimes changing the meaning of the title entirely. Seriously, there are lots of places to put a sticky barcode, why the front cover?]]></description>
			<content:encoded><![CDATA[<p>Libraries, sometimes when you stick those barcode labels on the front of your books, you obscure information on the cover, sometimes <a href="http://www.thisisbroken.com/b/2006/08/library_book_co.html">changing the meaning of the title entirely</a>. Seriously, there are lots of places to put a sticky barcode, why the front cover?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1821/this-is-broken-a-brief-story-of-me/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>make Amazon suck like your OPAC. innovative + api haxie</title>
		<link>http://www.librarian.net/stax/1773/make-amazon-suck-like-your-opac-innovative-api-haxie/</link>
		<comments>http://www.librarian.net/stax/1773/make-amazon-suck-like-your-opac-innovative-api-haxie/#comments</comments>
		<pubDate>Thu, 15 Jun 2006 14:27:32 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[humor]]></category>
		<category><![CDATA[innovative]]></category>
		<category><![CDATA[opac]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1773</guid>
		<description><![CDATA[If Amazon sucked like our old OPAC. To be fair, this Innovative version is pretty ancient. Funny? Yes. Accurate? Not entirely. [thanks marlene]]]></description>
			<content:encoded><![CDATA[<p><a href="http://library2.csusm.edu/amazon/index.htm">If Amazon sucked like our old OPAC</a>. To be fair, this Innovative version is pretty ancient. Funny? Yes. Accurate? Not entirely. <small>[thanks <a href="http://marlenescorner.blogspirit.com/archive/2006/06/15/amazon-version-roots.html">marlene</a>]</small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1773/make-amazon-suck-like-your-opac-innovative-api-haxie/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>co-browsing: why use software that you can&#8217;t use and patrons don&#8217;t like?</title>
		<link>http://www.librarian.net/stax/1581/co-browsing-why-use-software-that-you-cant-use-and-patrons-dont-like/</link>
		<comments>http://www.librarian.net/stax/1581/co-browsing-why-use-software-that-you-cant-use-and-patrons-dont-like/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 01:24:51 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[cobrowsing]]></category>
		<category><![CDATA[customerservice]]></category>
		<category><![CDATA[librarianinblack]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1581</guid>
		<description><![CDATA[The Librarian in Black has a few more things to say about co-browsing in her post How much is co-browsing really helping our users? I stopped trying to use co-browsing a long time ago. It&#8217;s bad customer service to give something to someone that has a good chance of not working. Period. Everyone touts co-browsing [...]]]></description>
			<content:encoded><![CDATA[<p>The Librarian in Black has a few more things to say about co-browsing in her post <a href="http://librarianinblack.typepad.com/librarianinblack/2005/12/how_much_is_cob.html">How much is co-browsing really helping our users</a>?<br />
<blockquote>I stopped trying to use co-browsing a long time ago.  It&#8217;s bad customer service to give something to someone that has a good chance of not working.  Period.  Everyone touts co-browsing as the cat&#8217;s pajamas, and it is kind of cool A) when it actually works, which is rare and B) when the user&#8217;s question actually warrants it&#8230;.  I am not a co-browsing fan.  At all.  If the big-name software companies can get to work on a Mac with a firewall and a dial-up connection running Firefox, then rock on.  I&#8217;ll be a fan.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1581/co-browsing-why-use-software-that-you-cant-use-and-patrons-dont-like/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>how do patrons perceive your filtering system?</title>
		<link>http://www.librarian.net/stax/1550/how-do-patrons-perceive-your-filtering-system/</link>
		<comments>http://www.librarian.net/stax/1550/how-do-patrons-perceive-your-filtering-system/#comments</comments>
		<pubDate>Wed, 23 Nov 2005 15:54:04 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[filtering]]></category>
		<category><![CDATA[pamrotella]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1550</guid>
		<description><![CDATA[Filtering is a reality that many libraries have to deal with in order to get funding for their connectivity and/or technology. I think some libraries give up once they have to filter and don&#8217;t make the patrons&#8217; filtering interactions as user-friendly as their other library interactions.]]></description>
			<content:encoded><![CDATA[<p>Filtering is a reality that many libraries have to deal with in order to get funding for their connectivity and/or technology. I think some libraries give up once they have to filter and <a href="http://www.pamrotella.com/polhist/rants/rants001/rants00019.html">don&#8217;t make the patrons&#8217; filtering interactions as user-friendly</a> as their other library interactions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1550/how-do-patrons-perceive-your-filtering-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility in books, websites, libraries and your mind.</title>
		<link>http://www.librarian.net/stax/1512/accessibility-in-books-websites-libraries-and-your-mind/</link>
		<comments>http://www.librarian.net/stax/1512/accessibility-in-books-websites-libraries-and-your-mind/#comments</comments>
		<pubDate>Tue, 18 Oct 2005 11:52:58 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[ala]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1512</guid>
		<description><![CDATA[I have been reading a lot of books about accessible design lately. This started around the time that I got sent this story about the National Library for the Blind in Norway and some of the design flaws that make it very hard for the visually disabled to get into, much less use. The Vermont [...]]]></description>
			<content:encoded><![CDATA[<p>I have been reading a lot of books about accessible design lately. This started around the time that I got sent <a href="http://www.aftenposten.no/english/local/article1129225.ece">this story about the National Library for the Blind</a> in Norway and some of the design flaws that make it very hard for the visually disabled to get into, much less use. The <a href="http://www.vtc.vsc.edu/">Vermont Technical College</a> has a lot of these books on access. Sadly, I am one of the only people to have checked them out in the last decade. As an aside, I think at this point I would have a very hard time going back to a library where they didn&#8217;t have datestamps in the back of the book. I think libraries keeping circulation info &#8220;secret&#8221; &#8212; not on purpose, but by ILS system design &#8212; is a decline in information-sharing with patrons, and a shame. Here are the books I have read, with links to my reviews.</p>
<p><a href="http://jessamyn.info/booklist/book/384">Beautiful Barrier Free</a><br />
<a href="http://jessamyn.info/booklist/book/385">Access by Design</a><br />
<a href="http://jessamyn.info/booklist/book/380">Design for Dignity: Studies in Accessibility</a></p>
<p>And, of course, let&#8217;s remember how to make our web sites accessible. Jacob Nielsen has come out with lists of <a href="http://www.useit.com/alertbox/designmistakes.html">top ten web design mistakes</a> as well as <a href="http://www.useit.com/alertbox/weblogs.html">top ten weblog design mistakes</a>. Check to see if you make any of these mistakes. I recently wrote a note to ALA&#8217;s webmaster commenting on the lack of ALT or title tags on the <a href="http://www.ala.org/ala/eventsandconferencesb/midwinter/2006/home.htm">ALA Midwinter Meeting page</a>. It&#8217;s a nice looking page, but information is imparted through lots of graphics, with no alternate navigation. Usually there is a set of text links at the bottom of the page if they use images for navigation. <a href="http://pasta.cantbedone.org/pages/hLbYV9.htm">This is what someone viewing the page with a text-only browser would see</a>. I cannot stress enough: <strong>this is the conference information page for the largest library association in the world</strong>. If we can&#8217;t <a href="http://www.ala.org/ala/productsandpublications/books/editions/adaptivetechnology.htm">follow our own rules</a> about accessibility, how can we expect others to?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1512/accessibility-in-books-websites-libraries-and-your-mind/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What We Want, The OPAC Manifesto</title>
		<link>http://www.librarian.net/stax/1451/what-we-want-the-opac-manifesto/</link>
		<comments>http://www.librarian.net/stax/1451/what-we-want-the-opac-manifesto/#comments</comments>
		<pubDate>Sat, 27 Aug 2005 02:56:27 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA[me!]]></category>
		<category><![CDATA[manifesto]]></category>
		<category><![CDATA[opac]]></category>
		<category><![CDATA[ui]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1451</guid>
		<description><![CDATA[Andrew Pace reminds me that I used to have a wiki, way back when. This wiki was a place where, among other things, I had a roomshare page for ALA as well as the OPAC Manifesto which was going to be an article in Searcher Magazine. However, the final version was not quite Searcher material, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.lib.ncsu.edu/staff/apace/">Andrew Pace</a> reminds me that I used to have a wiki, way back when. This wiki was a place where, among other things, I had a roomshare page for ALA as well as the OPAC Manifesto which was going to be an article in Searcher Magazine. However, the final version was not quite Searcher material, so I shelved it temporarily while I thought about wikifixing and promptly forgot about it. <a href="http://www.librarian.net/opac/">The OPAC Manifesto</a> is back for your viewing [though not editing] pleasure. Thanks very much to people who helped with it. Feel free to link or republish in any not-for-profit venture, just cite it and credit it. </p>
<p><strong>update:</strong> for those of you who missed this topic before, the manifesto was set up on a wiki so that anyone could add or edit ideas on it. The intro and outro are mine, the rest was collaboratively built.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1451/what-we-want-the-opac-manifesto/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

