<?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: Designing Search Checklist</title>
	<atom:link href="http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/</link>
	<description>Adaptive Path Blog</description>
	<lastBuildDate>Wed, 10 Mar 2010 15:51:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ainscough.net &#187; Checklist for designing search</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179511</link>
		<dc:creator>ainscough.net &#187; Checklist for designing search</dc:creator>
		<pubDate>Mon, 25 Aug 2008 20:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179511</guid>
		<description>[...] Designing Search Checklist from adaptive path. [...]</description>
		<content:encoded><![CDATA[<p>[...] Designing Search Checklist from adaptive path. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David G. Paul</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179437</link>
		<dc:creator>David G. Paul</dc:creator>
		<pubDate>Tue, 12 Aug 2008 15:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179437</guid>
		<description>nice list, I think I&#039;ll have to remember those items when I redesign my search page later!</description>
		<content:encoded><![CDATA[<p>nice list, I think I&#8217;ll have to remember those items when I redesign my search page later!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL/PHP Boolean Search&#160;Updated - Joe Dolson Accessible Web Design</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179301</link>
		<dc:creator>MySQL/PHP Boolean Search&#160;Updated - Joe Dolson Accessible Web Design</dc:creator>
		<pubDate>Sun, 03 Aug 2008 20:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179301</guid>
		<description>[...] the publication of a brief article on Search results design by Adaptive Path, I decided that revising my database search script was a valuable goal. [...]</description>
		<content:encoded><![CDATA[<p>[...] the publication of a brief article on Search results design by Adaptive Path, I decided that revising my database search script was a valuable goal. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Some links for light reading (29/7/08)</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179267</link>
		<dc:creator>Max Design - standards based web design, development and training &#187; Some links for light reading (29/7/08)</dc:creator>
		<pubDate>Tue, 29 Jul 2008 11:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179267</guid>
		<description>[...] Designing Search Checklist [...]</description>
		<content:encoded><![CDATA[<p>[...] Designing Search Checklist [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Abut</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179239</link>
		<dc:creator>Al Abut</dc:creator>
		<pubDate>Fri, 25 Jul 2008 19:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179239</guid>
		<description>Great list!

I&#039;d add a few more that I&#039;ve found to be important and inspired by some of the nuances of Google&#039;s UI:

1) I&#039;d modify &quot;Allow sorting and refinement tools if appropriate for your users and content&quot; to reveal some hierarchy within the results themselves rather than cluttering things up with more options, when possible. Do this by building a bit of default sorting with sublists and grouping related items together.

This sounds more complicated than it is and is visually simply to understand. For example, if results two and three are subsections of the first result, then indent them and move closer to their &quot;parent&quot;. A good example is &lt;a href=&quot;http://www.google.com/search?q=al%20abut&quot; rel=&quot;nofollow&quot;&gt;an ego search for my name&lt;/a&gt; - the first two results from my site are grouped together, then the next two from flickr, then two more from some w3 list I posted to ages ago, etc.

2) give sneak peeks of other types of searches for the same term by giving snippets above the &quot;real&quot; results and a link to more, or even modifying the look of a single result to get across that it&#039;s a different media. For example, &lt;a href=&quot;http://www.google.com/search?q=obama&quot; rel=&quot;nofollow&quot;&gt;searching for Obama&lt;/a&gt; will have the results you&#039;d expect and also some snippets of recent news, a thumbnail and rating next to the youtube clip, etc.

This last one is actually more relevant than you might think, this isn&#039;t just a problem for search companies with various flavors of engines. Depending on what kind of site you&#039;re building or working on, it&#039;s worth questioning when a page of mainly text with a long list of links is the best fit for the type of thing being searched and what to do when it isn&#039;t, whether to make modifications to a single search result UI to highlight the differences or have a separate type of search for a particular type of data rather than trying to have only one search result UI to rule them all. Context over consistency - sounds simple, often isn&#039;t :)</description>
		<content:encoded><![CDATA[<p>Great list!</p>
<p>I&#8217;d add a few more that I&#8217;ve found to be important and inspired by some of the nuances of Google&#8217;s UI:</p>
<p>1) I&#8217;d modify &#8220;Allow sorting and refinement tools if appropriate for your users and content&#8221; to reveal some hierarchy within the results themselves rather than cluttering things up with more options, when possible. Do this by building a bit of default sorting with sublists and grouping related items together.</p>
<p>This sounds more complicated than it is and is visually simply to understand. For example, if results two and three are subsections of the first result, then indent them and move closer to their &#8220;parent&#8221;. A good example is <a href="http://www.google.com/search?q=al%20abut" rel="nofollow">an ego search for my name</a> &#8211; the first two results from my site are grouped together, then the next two from flickr, then two more from some w3 list I posted to ages ago, etc.</p>
<p>2) give sneak peeks of other types of searches for the same term by giving snippets above the &#8220;real&#8221; results and a link to more, or even modifying the look of a single result to get across that it&#8217;s a different media. For example, <a href="http://www.google.com/search?q=obama" rel="nofollow">searching for Obama</a> will have the results you&#8217;d expect and also some snippets of recent news, a thumbnail and rating next to the youtube clip, etc.</p>
<p>This last one is actually more relevant than you might think, this isn&#8217;t just a problem for search companies with various flavors of engines. Depending on what kind of site you&#8217;re building or working on, it&#8217;s worth questioning when a page of mainly text with a long list of links is the best fit for the type of thing being searched and what to do when it isn&#8217;t, whether to make modifications to a single search result UI to highlight the differences or have a separate type of search for a particular type of data rather than trying to have only one search result UI to rule them all. Context over consistency &#8211; sounds simple, often isn&#8217;t <img src='http://www.adaptivepath.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179208</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Tue, 22 Jul 2008 05:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179208</guid>
		<description>Hi Chiara,

That&#039;s a good list, and it certainly matches our experience. We&#039;ve also written a little on this: &lt;a href=&quot;http://www.steptwo.com.au/papers/cmb_searchresults/index.html&quot; rel=&quot;nofollow&quot;&gt;What to include in search results&lt;/a&gt;. That says pretty much the same thing...

Cheers, James</description>
		<content:encoded><![CDATA[<p>Hi Chiara,</p>
<p>That&#8217;s a good list, and it certainly matches our experience. We&#8217;ve also written a little on this: <a href="http://www.steptwo.com.au/papers/cmb_searchresults/index.html" rel="nofollow">What to include in search results</a>. That says pretty much the same thing&#8230;</p>
<p>Cheers, James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Santoyo</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179179</link>
		<dc:creator>Mario Santoyo</dc:creator>
		<pubDate>Thu, 17 Jul 2008 19:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179179</guid>
		<description>Chiara it seems you are on the road to create a pattern :) Erin Malone is without doubt smiling somewhere in her vacation :). 

We have the following list for our results, I&#039;ve generalized it to match a general SERP instead of an specific one (docs, products, etc).

1. Navigation Artifacts
BreadCrumb: Searched Terms + Categorie or paths followed (via facets or traditional breadcrumbs usage depending on the artifacts placed to filter and navigate the SERPS)
Search form with searched terms
Number of items/pages in SERP

2. Specification Artifacts
Clusters and/or  Filters to narrow down SERP

3. Related searches
Semantic or grammatical corrections suggestions
Releated search terms (to narrow via specification SERPs)

4. Manipulation artifacts
Sorting
Comparison of results

5. Expanded navigation artifacts
Visited results
Related results
Related goals
Advertising spaces

6. Results artifact
Depends on what you are implementing. But in every problem we have faced on our different portals we decide to select data that can help user understand what she would find out on the result once it is clicked and help her decide on which results might prove interesting goals to follow and which don&#039;t. For example on a retail site we&#039;ve decided to place a brief item description, photograph, geographical location and price, since we have been able to discern through ethnographic studies this are the variables that our users use to inform their purchase decision.

7. Alternate revenue artifacts
Result highlighting or special treatment
Advertising spaces

We also take into account the default sorting of the results, and it varies on what kind of implementation you are working on, always treating only the results that correctly matches user expectations. On some sites we&#039;ve decided to give better placements to the results that have payed for special treatment, results through which we know we can have higher take rates, ranking based on proximity against search expectation, etc.</description>
		<content:encoded><![CDATA[<p>Chiara it seems you are on the road to create a pattern <img src='http://www.adaptivepath.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Erin Malone is without doubt smiling somewhere in her vacation <img src='http://www.adaptivepath.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . </p>
<p>We have the following list for our results, I&#8217;ve generalized it to match a general SERP instead of an specific one (docs, products, etc).</p>
<p>1. Navigation Artifacts<br />
BreadCrumb: Searched Terms + Categorie or paths followed (via facets or traditional breadcrumbs usage depending on the artifacts placed to filter and navigate the SERPS)<br />
Search form with searched terms<br />
Number of items/pages in SERP</p>
<p>2. Specification Artifacts<br />
Clusters and/or  Filters to narrow down SERP</p>
<p>3. Related searches<br />
Semantic or grammatical corrections suggestions<br />
Releated search terms (to narrow via specification SERPs)</p>
<p>4. Manipulation artifacts<br />
Sorting<br />
Comparison of results</p>
<p>5. Expanded navigation artifacts<br />
Visited results<br />
Related results<br />
Related goals<br />
Advertising spaces</p>
<p>6. Results artifact<br />
Depends on what you are implementing. But in every problem we have faced on our different portals we decide to select data that can help user understand what she would find out on the result once it is clicked and help her decide on which results might prove interesting goals to follow and which don&#8217;t. For example on a retail site we&#8217;ve decided to place a brief item description, photograph, geographical location and price, since we have been able to discern through ethnographic studies this are the variables that our users use to inform their purchase decision.</p>
<p>7. Alternate revenue artifacts<br />
Result highlighting or special treatment<br />
Advertising spaces</p>
<p>We also take into account the default sorting of the results, and it varies on what kind of implementation you are working on, always treating only the results that correctly matches user expectations. On some sites we&#8217;ve decided to give better placements to the results that have payed for special treatment, results through which we know we can have higher take rates, ranking based on proximity against search expectation, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruairi Galavan</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179174</link>
		<dc:creator>Ruairi Galavan</dc:creator>
		<pubDate>Wed, 16 Jul 2008 14:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179174</guid>
		<description>When search results are documents (pdf&#039;s etc) give introductory text (e.g., the abstract) to the document.

Thanks for the list,
 
Implementing changes on my current design now!</description>
		<content:encoded><![CDATA[<p>When search results are documents (pdf&#8217;s etc) give introductory text (e.g., the abstract) to the document.</p>
<p>Thanks for the list,</p>
<p>Implementing changes on my current design now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Ogan</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179165</link>
		<dc:creator>Erik Ogan</dc:creator>
		<pubDate>Tue, 15 Jul 2008 20:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179165</guid>
		<description>“Include a query box so the user can search again.”

…prefilled with the query just run so the user can edit, rather than starting from scratch.</description>
		<content:encoded><![CDATA[<p>“Include a query box so the user can search again.”</p>
<p>…prefilled with the query just run so the user can edit, rather than starting from scratch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chiara Fox</title>
		<link>http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/comment-page-1/#comment-179164</link>
		<dc:creator>Chiara Fox</dc:creator>
		<pubDate>Tue, 15 Jul 2008 20:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/07/14/designing-search-checklist/#comment-179164</guid>
		<description>These are great everyone! Keep them coming!</description>
		<content:encoded><![CDATA[<p>These are great everyone! Keep them coming!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
