<?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: website redesign and users (OMG! not the user!)</title>
	<atom:link href="http://tech-ink.net/2009/09/08/website-redesign-and-users-omg-not-the-user/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech-ink.net/2009/09/08/website-redesign-and-users-omg-not-the-user/</link>
	<description>A Librarian Collective</description>
	<lastBuildDate>Fri, 11 Sep 2009 19:42:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David</title>
		<link>http://tech-ink.net/2009/09/08/website-redesign-and-users-omg-not-the-user/comment-page-1/#comment-86</link>
		<dc:creator>David</dc:creator>
		<pubDate>Fri, 11 Sep 2009 19:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://tech-ink.net/?p=82#comment-86</guid>
		<description>We define our primary user group as the faculty and students on campus: people who are using the library for research or instruction. We held focus groups with faculty, grad students, and undergrads during our last go-round.

When it came to deciding on the visual design parameters, we went for 1024-wide for the simple reason that that&#039;s how most of the web is working anyway. If you go to the Globe &amp; Mail, or even many of our subscription databases, they have been designed for a 1024-wide screen, so there&#039;s no reason why we should handicap ourselves for a layout that nobody uses. We&#039;re not doing anything really sexy in terms of interactivity on the site, so &quot;IE6&quot; doesn&#039;t really come into it, I don&#039;t think.</description>
		<content:encoded><![CDATA[<p>We define our primary user group as the faculty and students on campus: people who are using the library for research or instruction. We held focus groups with faculty, grad students, and undergrads during our last go-round.</p>
<p>When it came to deciding on the visual design parameters, we went for 1024-wide for the simple reason that that&#8217;s how most of the web is working anyway. If you go to the Globe &amp; Mail, or even many of our subscription databases, they have been designed for a 1024-wide screen, so there&#8217;s no reason why we should handicap ourselves for a layout that nobody uses. We&#8217;re not doing anything really sexy in terms of interactivity on the site, so &#8220;IE6&#8243; doesn&#8217;t really come into it, I don&#8217;t think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rochelle</title>
		<link>http://tech-ink.net/2009/09/08/website-redesign-and-users-omg-not-the-user/comment-page-1/#comment-85</link>
		<dc:creator>Rochelle</dc:creator>
		<pubDate>Fri, 11 Sep 2009 17:07:24 +0000</pubDate>
		<guid isPermaLink="false">http://tech-ink.net/?p=82#comment-85</guid>
		<description>Ahhh you are so brave!

We addressed the audience thing head on, and of course there are waves of reaction to that choice. Our primary audience is undergraduate students at our campus. And of them, we are trying to answer the questions 80% of them have. This means that some of the quirkier things are harder to find, and it means that faculty questions are not answered on the first page. (They have to click the &quot;faculty&quot; tab, makng them secondarily our audience.) We have only been live a couple of weeks and I&#039;m already really feeling the need for multiple views for our different audiences.

Our approach to that will be to create a website you have to log into. I know that will go over like a lead balloon, but if we had everyone logging in, we could deliver content to them based on their role and their current needs. That way we could properly address the needs of all our users.</description>
		<content:encoded><![CDATA[<p>Ahhh you are so brave!</p>
<p>We addressed the audience thing head on, and of course there are waves of reaction to that choice. Our primary audience is undergraduate students at our campus. And of them, we are trying to answer the questions 80% of them have. This means that some of the quirkier things are harder to find, and it means that faculty questions are not answered on the first page. (They have to click the &#8220;faculty&#8221; tab, makng them secondarily our audience.) We have only been live a couple of weeks and I&#8217;m already really feeling the need for multiple views for our different audiences.</p>
<p>Our approach to that will be to create a website you have to log into. I know that will go over like a lead balloon, but if we had everyone logging in, we could deliver content to them based on their role and their current needs. That way we could properly address the needs of all our users.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
