<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;User Interface&gt;Search</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/User-Interface/Search</link>
	<description>A listing of the most recently indexed works about Design and Web Design and User Interface and Search in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Web Design&gt;User Interface&gt;Search</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/User-Interface/Search</link>
	</image>
	<item>
		<title>Search Goal Redefinition Through User-System Interaction</title>
		<link>http://tc.eserver.org/34969.html</link>
		<guid>http://tc.eserver.org/34969.html</guid>
		<description>The purpose of this research is to examine search goal redefinition during users&apos; interaction with information retrieval systems.</description>
	</item>
	<item>
		<title>Designing Search Pages</title>
		<link>http://tc.eserver.org/29766.html</link>
		<guid>http://tc.eserver.org/29766.html</guid>
		<description>Many web sites and applications include a search feature. Often they provide an extremely simple search interface consisting of a single text box and a &quot;Go&quot; button. Sometimes, however, the users&apos; tasks call for more sophistication, and guidelines for complex search interfaces are difficult to find. This paper details four levels of search interface, and it provides heuristics (guidelines) to use when designing complex search interfaces. Different solutions are appropriate, depending on the users&apos; motivation and knowledge of their subject, experience using search interfaces, and search goals. Finally, PubMed serves as a useful example to illustrate how these guidelines can be used to analyze existing search interfaces.</description>
	</item>
	<item>
		<title>Reconciling Information-Seeking Behavior with Search User Interfaces for the Web</title>
		<link>http://tc.eserver.org/24753.html</link>
		<guid>http://tc.eserver.org/24753.html</guid>
		<description>Current search interfaces reflect the inner workings of search technology rather than what we know about how people look for information.</description>
	</item>
	<item>
		<title>Best Practices and Future Visions for Search User Interfaces: Position Paper</title>
		<link>http://tc.eserver.org/23071.html</link>
		<guid>http://tc.eserver.org/23071.html</guid>
		<description>The author argues that progress in search requires vigorous inquiry into how search can be embedded into application environments such as those for decision-making, personal information collecting, and designing.</description>
	</item>
	<item>
		<title>The Big Dig: Mining Nuggets of Value</title>
		<link>http://tc.eserver.org/21724.html</link>
		<guid>http://tc.eserver.org/21724.html</guid>
		<description>It is difficult to apply the lessons learned from e-commerce search interfaces to more complex ones, such as those for libraries or technical material.  This article provides a guide to tailoring search interfaces to users with a persona-based approach.</description>
	</item>
	<item>
		<title>Why Amazon Succeeds -- And Why It Won&apos;t Help You</title>
		<link>http://tc.eserver.org/14198.html</link>
		<guid>http://tc.eserver.org/14198.html</guid>
		<description>Amazon is one of the best on-site search capabilities we&apos;ve ever seen. But surprisingly, the reason why it works so well is likely to be the same reason why Search &lt;i&gt;won&apos;t&lt;/i&gt; work well on your site.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/User-Interface/Search.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>