<?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: Easy as 1,2,3?</title>
	<atom:link href="http://www.goodusability.co.uk/2009/01/easy-as-123/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk/2009/01/easy-as-123/</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 19:18:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SEO &#38; Pagination - What is Pagination? &#124; SEO - janet bartoli roussos</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-2267</link>
		<dc:creator>SEO &#38; Pagination - What is Pagination? &#124; SEO - janet bartoli roussos</dc:creator>
		<pubDate>Thu, 27 Aug 2009 18:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-2267</guid>
		<description>[...] found a good, plain speaking site that helps describe this a bit further – from David Hamill’s blog and from reading blue acorn’s great technical details – still I think eliminating pagination [...]</description>
		<content:encoded><![CDATA[<p>[...] found a good, plain speaking site that helps describe this a bit further – from David Hamill’s blog and from reading blue acorn’s great technical details – still I think eliminating pagination [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-1083</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Tue, 07 Apr 2009 07:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-1083</guid>
		<description>Hi Keith, you&#039;re right that providing other facilities for fast information retrieval are important. But you&#039;re assuming that everyone notices them and understands how to use them. This isn&#039;t always the case. If you paginate your results with numbers, a lot of people will assume that this is the way they navigate through them.

The issues you point out are challenges that can be solved, they just require a bit of effort . If I select a month from a date range, the number of results only becomes an issue when it gets too large. I&#039;d rather be able to choose a month than have to guess a number between 2 and 45.</description>
		<content:encoded><![CDATA[<p>Hi Keith, you&#8217;re right that providing other facilities for fast information retrieval are important. But you&#8217;re assuming that everyone notices them and understands how to use them. This isn&#8217;t always the case. If you paginate your results with numbers, a lot of people will assume that this is the way they navigate through them.</p>
<p>The issues you point out are challenges that can be solved, they just require a bit of effort . If I select a month from a date range, the number of results only becomes an issue when it gets too large. I&#8217;d rather be able to choose a month than have to guess a number between 2 and 45.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Humm</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-1076</link>
		<dc:creator>Keith Humm</dc:creator>
		<pubDate>Tue, 07 Apr 2009 02:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-1076</guid>
		<description>Hmm. I agree with a lot of your comments, but think that for the most part they are largely irrelevant.

A lot of people misuse numerical pagination - primarily by not providing other facilities for fast information retrieval. Providing links such as &#039;date ranges&#039; for pagination presents its own issues - the compact form for dates is ambiguous (USA vs. Intl formats) and much, much longer. It&#039;s also difficult to understand exactly how many items per page you will receive etc.

My point, I guess, is that filtering and searching are the important parts that get neglected, not pages as such. Pagination should serve a single purpose: to divide things up into digestible chunks.

Things like date ranges and ABC etc are *filters* and not paginators. They work together.</description>
		<content:encoded><![CDATA[<p>Hmm. I agree with a lot of your comments, but think that for the most part they are largely irrelevant.</p>
<p>A lot of people misuse numerical pagination &#8211; primarily by not providing other facilities for fast information retrieval. Providing links such as &#8216;date ranges&#8217; for pagination presents its own issues &#8211; the compact form for dates is ambiguous (USA vs. Intl formats) and much, much longer. It&#8217;s also difficult to understand exactly how many items per page you will receive etc.</p>
<p>My point, I guess, is that filtering and searching are the important parts that get neglected, not pages as such. Pagination should serve a single purpose: to divide things up into digestible chunks.</p>
<p>Things like date ranges and ABC etc are *filters* and not paginators. They work together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Product filters &#124; Usability Thoughts</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-932</link>
		<dc:creator>Product filters &#124; Usability Thoughts</dc:creator>
		<pubDate>Mon, 16 Mar 2009 20:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-932</guid>
		<description>[...] was talking the other day about pagination and David Hamill had a point there, those tiny numbers don&#8217;t send any message to the user, so what&#8217;s the [...]</description>
		<content:encoded><![CDATA[<p>[...] was talking the other day about pagination and David Hamill had a point there, those tiny numbers don&#8217;t send any message to the user, so what&#8217;s the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PÃ¤r NystrÃ¶m</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-756</link>
		<dc:creator>PÃ¤r NystrÃ¶m</dc:creator>
		<pubDate>Wed, 04 Mar 2009 08:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-756</guid>
		<description>I try to decide whether or not to use pagination by the content of the search result... 

If the posts are &quot;nominal&quot; (in the meaning unrelated to eachother in their main content) I prefer pagination. Consider Google&#039;s search results: two different posts can have totally unrelated content, although the search algorithm can still sort it by mathematical relevance. But this relevance is not really the relevance of the user.

Also, when the user is not interrested in comparing two posts I like pagination.

If the posts are sortable on the factor that the user is interrested in comparing, I do not use pagination. I use scrollbars or something else to avoid that two interresting posts happen to fall in different pages.</description>
		<content:encoded><![CDATA[<p>I try to decide whether or not to use pagination by the content of the search result&#8230; </p>
<p>If the posts are &#8220;nominal&#8221; (in the meaning unrelated to eachother in their main content) I prefer pagination. Consider Google&#8217;s search results: two different posts can have totally unrelated content, although the search algorithm can still sort it by mathematical relevance. But this relevance is not really the relevance of the user.</p>
<p>Also, when the user is not interrested in comparing two posts I like pagination.</p>
<p>If the posts are sortable on the factor that the user is interrested in comparing, I do not use pagination. I use scrollbars or something else to avoid that two interresting posts happen to fall in different pages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Use relevant pagination styles &#124; ux digest</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-212</link>
		<dc:creator>Use relevant pagination styles &#124; ux digest</dc:creator>
		<pubDate>Mon, 23 Feb 2009 04:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-212</guid>
		<description>[...] Source: Easy as 1, 2, 3? (Good Usability) [...]</description>
		<content:encoded><![CDATA[<p>[...] Source: Easy as 1, 2, 3? (Good Usability) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-192</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Fri, 20 Feb 2009 10:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-192</guid>
		<description>Hi Chris. Good point but your database design shouldn&#039;t dictate the user experience. It should be the other way round. I get your point about page load times but one 3 second page can provide a better user experience than 3 split second page loads. After all, your user needs to digest each of those pages only to discover that they need to try the next page.</description>
		<content:encoded><![CDATA[<p>Hi Chris. Good point but your database design shouldn&#8217;t dictate the user experience. It should be the other way round. I get your point about page load times but one 3 second page can provide a better user experience than 3 split second page loads. After all, your user needs to digest each of those pages only to discover that they need to try the next page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Cohen</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-191</link>
		<dc:creator>Chris Cohen</dc:creator>
		<pubDate>Fri, 20 Feb 2009 09:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-191</guid>
		<description>An interesting approach, but in a situation where you advocate showing everything on one page instead of paginating, the load on the server will increase dramatically, both in terms of bandwidth and processing. A 5-page, 10-item-per-page display then becomes 50 items on one page.

I like the idea of alphabetical presentation, but it&#039;s not as intuitive from a database design point of view. You would potentially need to change the indexes on the database table to make this efficient, and then cater for things like products starting with the word &#039;the&#039; to avoid them all getting clumped in the &#039;T&#039; section.</description>
		<content:encoded><![CDATA[<p>An interesting approach, but in a situation where you advocate showing everything on one page instead of paginating, the load on the server will increase dramatically, both in terms of bandwidth and processing. A 5-page, 10-item-per-page display then becomes 50 items on one page.</p>
<p>I like the idea of alphabetical presentation, but it&#8217;s not as intuitive from a database design point of view. You would potentially need to change the indexes on the database table to make this efficient, and then cater for things like products starting with the word &#8216;the&#8217; to avoid them all getting clumped in the &#8216;T&#8217; section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linkit 20.2. - 20.2. &#124; Valontuoja</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-189</link>
		<dc:creator>Linkit 20.2. - 20.2. &#124; Valontuoja</dc:creator>
		<pubDate>Fri, 20 Feb 2009 06:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-189</guid>
		<description>[...] Good Usability &#187; Easy as 1,2,3? Using 1,2,3 links is often a result of lazy web design. In many cases, it&#8217;s the web equivalent of asking your users to rake through bargain bins. They don&#8217;t know what&#8217;s in each bin, they have to rummage through them in order to find out.    20. Helmikuu 2009 ( 1 minuuttia sitten ) -  Linkit [...]</description>
		<content:encoded><![CDATA[<p>[...] Good Usability &raquo; Easy as 1,2,3? Using 1,2,3 links is often a result of lazy web design. In many cases, it&rsquo;s the web equivalent of asking your users to rake through bargain bins. They don&rsquo;t know what&rsquo;s in each bin, they have to rummage through them in order to find out.    20. Helmikuu 2009 ( 1 minuuttia sitten ) &#8211;  Linkit [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas &#124; Santhos Webdesign</title>
		<link>http://www.goodusability.co.uk/2009/01/easy-as-123/comment-page-1/#comment-188</link>
		<dc:creator>Thomas &#124; Santhos Webdesign</dc:creator>
		<pubDate>Thu, 19 Feb 2009 22:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=419#comment-188</guid>
		<description>Excellent article! I&#039;ve also been very surprised by the way Hotmail deals with it... Should expect more from such a company...

I think when it&#039;s used numerical, you&#039;d almost better NOT do it... As you mentioned, finding some particular date or something... which number to choose? Always need a couple of attempts... Why not place everything in one large list?

Take a look at Outlook for instance. Why isn&#039;t it used there?? Everyone on this planet is scrolling through a long list of mails. Me too and I don&#039;t mind. So why should it be different on the web?

Alphabetical is another thing, because you KNOW where to click.</description>
		<content:encoded><![CDATA[<p>Excellent article! I&#8217;ve also been very surprised by the way Hotmail deals with it&#8230; Should expect more from such a company&#8230;</p>
<p>I think when it&#8217;s used numerical, you&#8217;d almost better NOT do it&#8230; As you mentioned, finding some particular date or something&#8230; which number to choose? Always need a couple of attempts&#8230; Why not place everything in one large list?</p>
<p>Take a look at Outlook for instance. Why isn&#8217;t it used there?? Everyone on this planet is scrolling through a long list of mails. Me too and I don&#8217;t mind. So why should it be different on the web?</p>
<p>Alphabetical is another thing, because you KNOW where to click.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
