<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Dynamics in Search User Interfaces</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marcus Nitsche</string-name>
          <email>marcus.nitsche@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Florian Uhde</string-name>
          <email>orian.uhde@st.ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Haun</string-name>
          <email>stefan.haun@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andreas Nürnberger</string-name>
          <email>andreas.nuernberger@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Otto von Guericke University</institution>
          ,
          <addr-line>Magdeburg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Searching the WWW has become an important task in today's information society. Nevertheless, users will mostly find static search user interfaces (SUIs) with results being only calculated and shown after the user triggers a button. This procedure is against the idea of flow and dynamic development of a natural search process. The main difficulty of good SUI design is to solve the conflict between good usability and presentation of relevant information. Serving a UI for every task and every user group is especially hard because of varying requirements. Dynamic search user interface elements allow the user to manage desired information fluently. They offer the possibility to add individual meta information, like tags, to the search process and enrich it thereby.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Search User Interface</kwd>
        <kwd>User Experience</kwd>
        <kwd>Exploratory Search</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Presented at EuroHCIR2013. Copyright c 2013 for the individual papers
by the papers’ authors. Copying permitted only for private and academic
purposes. This volume is published and copyrighted by its editors.
knowledge available online. Therefore, a proficient tool to
analyse the structure of the web and to provide guidance to specific
sources of information is needed. This task is accomplished by
modern search engines like Google2, Bing3, Yahoo4 and other
local or topic centred search engines. By the increase of
computational power in smart phones and wider access to online resources
the demand for these search tools has risen and the quality of the
search terms has changed. Instead of single-query-searches, users
tend to request complex answers5, trying to learn about topics in
deep. While the need for information and the expectations of users
increased, matching the broader knowledge base contained in the
Internet in the last few years. About 300 Mio. websites were added
in 20116. Search engines mainly remain the same. This leads to the
fact that a “significant design challenge for web search engine
developers is to develop functionality that accommodates the wide
variety of skills and information needs of a diverse user population”
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Therefore, this paper proposes the concept of using dynamic
elements in SUIs, that focus on fluent work flow characteristics, a
high grade of interactivity and an adequate answer-time-behaviour.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. INFORMATION GATHERING</title>
      <p>
        Looking at users’ habits in search, they no longer perform
simple lookup searches. There is an increasing need to answer
complex information needs. Therefore, we mainly consider
information gathering processes, searches where users are not familiar with
the domain. Users need to refine search queries, branch out into
other queries to gain additional understanding and collect results to
merge them into a single topic. This kind of search process is called
exploratory search and is contrary to a known-item search task as
stated in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Exploratory search processes “depend on selection,
navigation, and trial-and-error tactics, which in turn facilitate
increasing expectations to use the Web as a source for learning and
exploratory discovery” [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Search tasks are fragmented,
consisting of single queries and search requests. The search requests may
yield additional data or parts of the final information which in the
end form the information requested by the user. While
performing such a complex search task, a pattern called berry picking [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
can be observed. While reading through a source of data, looking
for qualified information the user discovers new traces leading to
other sources, which have to be handled one after the next. By
re2http://www.google.com, 02.05.2013
3http://www.bing.com, 02.05.2013
4http://www.yahoo.com, 02.05.2013
5see the 2009 HitWise study for more details:
//image.exct.net/lib/fefc1774726706/d/1/
SearchEngines_Jan09.pdf, 10.07.2013
6http://royal.pingdom.com/2012/01/17/
internet-2011-in-numbers/, 02.05.2013
http:
fining the search and gaining deeper information the user satisfies
the initial need for it. These different traces span a map in the end,
representing the whole search and its processing. When someone
is learning about something this map is refined and expanded. The
learner may track back to a certain node and deepen the
understanding about it by adding new queries, and therefore new branches. Or
he may discard a whole part of the map because it turned out that
the contained information was not relevant to him. When the user
is satisfied with the gained information this map is encapsulated
and represents the whole development of this complex information.
According to this concept the result is not a single object. It is a set
of sources, representing the learning process for a specific user.
Looking at the current process of information gathering in the
Internet there are only two places. The Internet itself, containing the
pool of existing information, in an unstructured form and a mental
model about the information (space) that is constructed. This
system may work perfect when dealing with short, exact search queries
like postal code New York City, but when it comes to complex
information needs, where the user needs to access a lot of information
and generate more detailed search queries while looming through
pages this system reaches it boundaries. The user might retrieve
only partial facts. For example, if the user needs explanation of a
term used in its initial query. The user is now in need of another
place, where he can store information, reorder it and put it into the
context of other information pieces.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. STATE OF THE ART</title>
      <p>
        Looking at Google, the most used search engine today [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], the user
interface of a modern search engine is mostly static. Google’s
features include some dynamic elements like real time search. For
example “[..] Google Suggest which interactively displays
suggestions in a drop-down list as the searcher types in each character of
his/her query. The suggestions are based on similar queries
submitted by other users.” [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] Dynamic previews of results will be offered
when clicking on the double arrow beside a result. But the core of
the interface has not changed a lot since its launch in 19977. While
adopting fast to new information sources like Facebook and Twitter,
Google discarded the adoption of new HCI methods in favour of a
clean, slim interface. With increasing touch support on the devices,
a richer user interface can be designed to provide the user with
immediate feedback and allows haptic interaction with the search
process. Some mobile clients take advance of the additional
information available, like the iOS search client, which switches to
voice queries when the phone is lifted to the head, but there is no
full extension of Google’s search services. While Google is an
adequate tool for short queries and queries calling for a direct answer,
features for deep research on complex topics are missing.
One way to integrate dynamic elements into existing SUI
infrastructure is to build an overlay. Thereby, dynamic UI utilize existing,
well known search engines and provide a benefit by enriching them.
This approach is shown in the Boolify8 search engine, which
provides a dynamic drag and drop interface on top of Google’s search
engine. This engine is relatively new and was build to promote the
understanding of boolean queries. Users build a query by
dragging jigsaw like parts onto a search surface. These parts contain
words (general or exact) and linkers like AND and OR. Additional
parts have been added to provide search on a specific page or for
7http://www.google.com/about/company/
history/, 02.05.2013
8http://www.boolify.org/, 02.05.2013
synonyms. By adding and linking those parts the user constructs
a boolean query which will be submitted to the Google search
engine. Boolify was built for children and elderly. Tests in a third
grade technology class showed that children without any
knowledge of boolean queries were able to construct complex queries
just by pulling them together piece by piece9. A similar approach
was implemented at SortFix10. This tool offers the user the
“ability to drag and drop search terms in between several buckets” [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
to in- and exclude them in the query. With a Standy Bucket users
are “able to keep track of all [their] inspirations and alternative
search words off to the side, ready to be dragged and dropped into
your search box if needed.” [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] Another possible use of dynamic
interface elements is the weighting of search terms based on their
font size as used at SearchCloud.net11. The ranked keywords are
shown in a Tag Cloud like manner and additionally the site shows,
based on the ranking, “the calculated relevance score for each
[result]” [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Not only the query building process can be enchanted
by dynamic elements, also the presentation of the result can benefit
from it. Dynamic side loading can provide the user a lens like view
to parts of the result where keywords occur. Microsoft’s WaveLens
“[...] fetches a longer sample for the page containing your
keywords, without you having to download it.” [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] Microsoft Research
shows that in a study using WaveLens, presenting the participants
with a normal interface and two versions of WaveLens’ UI (instant
zoom and dynamic zoom), “participants were not only slower with
the normal view than the other two, but they were more than twice
as likely to give up” [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Another way of result presentation was
shown at SearchMe12: “Fragmentation into multiple sites, domains
and identities becomes a huge distraction. User don’t know which
site to visit for which purpose, and the lack of consistent, intuitive
inter-site search and navigation makes it hard to find content [..]”
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. All these dynamic features can be used as a mask over
traditional SUIs to extend them. By hiding the dynamic part, dynamic
elements can be added to an existing search engine and let the user
make a choice which part should be shown and used. The proposed
concept is similar to Byström &amp; Hansen’s approach in [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
Issues. Comparing the state of the art with the process of
information gathering some issues appear, which may be resolved or at
least damped by using of dynamic elements. While collecting
information pieces for solving complex questions the user discovers
new sources, containing more information. These sources may not
form a linear search process every time. Sometimes there will be a
split and the user needs to decide which trace to follow first. This
issue is also noted in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Today’s search engines offer only little
support for this. The user needs to save web pages to favourites or
organize them himself for later reading. Searching different terms
one by one allows users to follow new pages like traces through
the Internet. By connecting these traces and setting them into
relation the user can retrieve the whole information needed to cover
his query. Most modern search engines discard this feature, it is
again something the user needs to do by himself. This leads to
another more general problem, the enclosing of search queries.
Google for example handles every search term as a new
operation. Data is stored, but contains only general information about
the user, queries are not related to each other and therefore
miss9http://ed-tech-axis.blogspot.de/2009/03/
boolified.htm, 02.05.2013
10SortFix.com, offline since 11/2011, Firefox plugin:
https://addons.mozilla.org/en-us/firefox/
addon/sortfix-Extension, 02.05.2013
11http://searchcloud.net/, 02.05.2013
12http://www.searchme.com, offline since 2009
ing its broader context. But when learning about a complex topic
refining the search query is more important to the user. In the
iteration of search processes, to narrow down the mass of information
and to tap new sources, the searcher needs to rewrite and modify
the query, to link it to other related search tasks. Building a
connection between parts of information and evaluating it against each
other is a core principle of learning. This leaves the user targeting
a broader, intense search, in the need to build a custom solution to
extract knowledge and manage it. This is strictly against the
guideline for online interfaces which suggests to “[..] not require users
to remember information from place to place on a Web site” [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] as
this is a distraction from the main process of searching and destroys
the interaction flow triggered by the search process.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. COMPOSING A DYNAMIC SUI</title>
      <p>
        The proposed approach shows a design based on today’s search
engines, enriched with dynamic UI elements to provide a plus for the
user. The design includes principles to form web based learning
applications [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] to focus on the completion of complex search tasks.
By adding dynamic elements internal states can be visualized for
the user to give a better overview about the current position in the
search process. Furthermore it will allow the serialization of search
processes and to step in at every point of the process later on. As
stated in Beyond Box Search “different interfaces (or at least
different forms of interaction) should be available to match different
search goals” and “[t]he interface should facilitate the selection of
appropriate context for the search” [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Both of this quality
measurements should be regarded when conceptualizing a SUI. The
first point will be covered by a modular UI, the user may move,
hide and scale elements to fit his current need. The second point
is strongly bounded to the use of dynamic items in the UI design.
By giving immediate feedback to the user it is easier to classify
the current results. The context of the whole search process will
be persistent over multiple search queries and provide a method of
accumulation parts of the search process into a single object.
Four features are proposed and explained in this paper, showing a
use-case for dynamic search interfaces and giving a suggestion how
this can be accomplished. Together these features build up a mid
instance to accumulate into a bigger context for a search process.
This clipboard (Fig. 1) reshapes the search process and provide the
place to store information between search queries. Instead of trying
to accumulate knowledge and information directly the user is able
to construct a solution of the search query in this buffer and save it
as a complete collection of the information retrieval process.
Reordering. Giving users the opportunity to reorder and therefore
to rate a search result is an important step towards dynamics in
SUIs. Every result is handled as a single item and can be picked
by the user and dropped in another place. The other items reorder
fluently, giving user feedback while the user moves on. The SUI
holds an array of parameters, which is used to evaluate every item.
Possible criteria are Accuracy, Clarity, Currency and Source
Novelty. These and more criteria are mentioned and explained in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
When a user reorders items to fit his preferences the search engine
may use the information provided by this ranking to weight the
existing parameters to yield better results in the future. The engine
will be able to present results ranked according to the user’s
preference. This can be done for all users and also search process wide, as
some search tasks require documents and papers while others may
focus on web pages or media. This addition to classical user
interfaces can make great use of the up-trend for touch based devices, in
2012 89% of mobile phones and smart-books support touch [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
Designing the SUI responsive to touch and gesture is maybe one
of the most natural solutions for human computer interaction and
adds an amount of possible actions based on gestures.
Workbench. The workbench targets the issue of loosing
information while switching between different searches. It adds a third
place to the proposed search process, located outside of the search
scope but still related to it. The user may drop queries here to keep
them throughout the whole search process. When entering a query,
indicators show how relevant items on the bench are. This allows
the user to classify new results in terms of integrity towards already
selected snippets. The workbench acts as a buffer between search
queries, adding a broader context to every entry. Like a frame, it
contains information exclusively attached to the current search
process, leading to the possibility of customization and user centred
search environments. When the user switches between queries he
can immediately determine how well the new results fit into already
selected items. This allows identifying false positive as well as
exploratory search [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] results. Users may just enter queries that lead
to a peripheral topic and check the indicators whether the result is
relevant to his initial information.
      </p>
      <p>
        Tag Cloud. The tag cloud is another feature to guide the user in the
search process. As shown in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] a tag cloud supported retrieval
system can increase the find rate of adjacent data nodes by nearly
15%. When adding an item to the workbench its most relevant tags
are extracted and visualized in the tag cloud. It is able to show how
often a tag occurs and how different tags are related to each other.
When entering a new search query the tag cloud displays the
relevant tags and reorders the cloud to revolve around the current tags.
By combining distance and size of the entered tag with their direct
neighbours the user can directly spot how homogeneous its current
query is in terms of the whole process. The tag cloud can also use
the existing tags to show the user other closely related tags and
suggest query refinement based on tag proximity. Colours can indicate
the state a tag is currently in. A possible color scheme for western
culture can be based on the three colors used in traffic lights. The
concept of three-coloured traffic lights also work for color-blind
people, since they do have a given position. Therefore, we also use
second coding paradigm: form. A green triangle is proposed for
tags resulting from the current query, which are contained in the
overall tag cloud spanned by the workbench. An orange circle
indicates a warning for tags, either in the current query result or the
bench, which are not related to the rest of the cloud. A red square is
avoided for the reason that uncontained tags may not be bad, they
can lead to a new direction or add a reasonable value to the whole
search process. The tags are scaled depending on their frequency.
When the user selects any item from the bench or the search
result the corresponding tags are centred. The other tags are located
based on their coherence with the selected tags; closer means the
tag is in a direct relation to the selected item. A user can quickly
check the integrity of his search process by looking at the tag cloud.
A slim, packed cloud means the results are all related to each other,
an open, wide cloud indicates a broad result field, covering many
aspects. False positives may be filtered out, when enough items
exist, as they stick out the rest of the cloud.
      </p>
      <p>
        Search Map Support. The search map (Fig. 2) acts as a
representation of the whole search process, by storing every query and
following up querying and visualize it in a chronological order. The user
may select single nodes in the map to get into the state of search
process at this moment and refine it. The map provides a kind of top
view to the path of the search and shows where the user branched
out into new queries. It allows the user to cut off nodes and whole
branches if they are not needed any more to fulfil the need for
information. As it contains every action and some data in the current
search process, the search map might be serialized and stored to
retrieve the search process later on. With this map at hand a user can
save whole search tasks just like he saves favourite web pages. He
can step back into the process at any time and reconstruct the whole
learning process or correct parts of the search which has proven to
be not correct. This kind of Story Telling helps to visualize the
given data, “[...] lead to findings, which prompt actions [...] [and]
can indicate the need to forage for new data.” [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] The search map
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] features two ways of expanding. The user may follow a result to
expand it vertically. The result is added as a new node and resides
in the map until it is processed further. When the user selects an
existing node he steps back to the vertical position of this node and
can now branch out horizontally. This deals with an issue of
berrypicking [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], where the new sources has to be processed one by one.
While not abolishing this the search map provides a visual
representation to simulate parallelism. The map also allows scoping of
the analysis by creating a horizontal or vertical bound. Only tags
and items inside this bound will be considered, the rest is greyed
out. This allows the user to dig deep into a certain topic (small
vertical bounds) or create a better understanding of a certain term
and add more results to a certain query (horizontal boundary). This
can help the user to concentrate on smaller pieces of a big search
process and to narrow down problems one by one.
      </p>
    </sec>
    <sec id="sec-5">
      <title>5. CONCLUSION</title>
      <p>This paper has shown certain design flaws of today’s search engines
and some proposed dynamic design principles to counter them. The
application of the envisioned elements can extend a search engine
towards a software capable of complex research tasks. With the
current up-trend of online learning this unlock a new way of using
them. The surplus resides not only in the dynamic and vivid
interface, it prepares a whole new tier of online search solutions. The
process of learning can be preserved and shared with others. One
can come back at any time, jump right into the saved search process
and reconstruct the development of certain knowledge. With this
tool chain at hand learning becomes a social and an integrative part
of the WWW. The next step in deploying dynamic elements into
search user interfaces would be prototyping them. Design snippets
need to be tested for usability and acceptance in the real world.
Starting as overlays and additional feature of existing search
engines may develop and emerge into independent solutions.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgement</title>
      <p>Part of the work is funded by the German Ministry of Education and
Science (BMBF) within the ViERforES II project (01IM10002B).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Sandvig</surname>
            ,
            <given-names>J. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Deepinder</surname>
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>User Perceptions of Search Enhancements in Web Search</article-title>
          .
          <source>In: J. of Comp. Inform. Syst</source>
          .
          <volume>52</volume>
          , no.
          <issue>2</issue>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>White</surname>
            ,
            <given-names>R. W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchionini</surname>
          </string-name>
          , G.:
          <article-title>A Study of Real-Time Query Expansion Effectiveness</article-title>
          .
          <source>In: SIGIR Forum 39</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Marchionini</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Exploratory Search: From Finding to Understanding</article-title>
          .
          <source>In: Comm. of the ACM 49</source>
          ,
          <issue>4</issue>
          .
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Bates</surname>
            ,
            <given-names>Marcia J.:</given-names>
          </string-name>
          <article-title>The design of browsing and berrypicking techniques for the online search interface</article-title>
          .
          <source>Univers. of Calif</source>
          . at
          <string-name>
            <surname>L.A.</surname>
          </string-name>
          ,
          <year>1989</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Purcell</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brenner</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rainie</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Search Engine Use 2012</article-title>
          . In: Pew Internet &amp; American Life Project,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Bates</surname>
            ,
            <given-names>M. E.</given-names>
          </string-name>
          :
          <article-title>Make Mine Interactive</article-title>
          . Vol.
          <volume>31</volume>
          ,
          <string-name>
            <surname>Issue</surname>
            <given-names>10</given-names>
          </string-name>
          , p.
          <volume>63</volume>
          ,
          <issue>12</issue>
          /
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Heer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Viégas</surname>
            ,
            <given-names>F. B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wattenberg</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Voyagers and voyeurs: Supporting asynchronous collaborative visualization</article-title>
          .
          <source>In: Commun. of the ACM</source>
          ,
          <volume>52</volume>
          , No.
          <issue>1</issue>
          , pp.
          <fpage>87</fpage>
          -
          <lpage>97</lpage>
          , ACM, New York, NY, USA, 01/
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>MS</given-names>
            <surname>Research: Cutting Edge</surname>
          </string-name>
          . New Scientist 181, no.
          <issue>2434</issue>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Paek</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumais</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Logan</surname>
          </string-name>
          , R.:
          <article-title>WaveLens: A new view onto Internet search results</article-title>
          .
          <source>In: Proc. of the SIGCHI Conference on Human Factors in Computing Systems (CHI '04)</source>
          , pp.
          <fpage>727</fpage>
          -
          <lpage>734</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Morville</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Callender</surname>
          </string-name>
          , J.:
          <article-title>Search Patterns - Design for Discovery</article-title>
          .
          <source>In: O'Reilly</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>U.S.</surname>
          </string-name>
          <article-title>Department of Health and Human Services, Research-Based Web Design and Usability Guidelines</article-title>
          . Washington, D.C.: GPO, n.d.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Jayasimman</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nisha</surname>
            <given-names>Jebaseeli</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Prakashraj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.G.</given-names>
            ,
            <surname>Charles</surname>
          </string-name>
          , J.:
          <article-title>Dynamic User Interface Based on Cognitive Approach in Web Based Learning</article-title>
          .
          <source>In: Int. J. of CS Iss. (IJCSI)</source>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Buck</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nicholas</surname>
          </string-name>
          , J.:
          <article-title>Beyond the search box</article-title>
          .
          <source>Reference &amp; User Services</source>
          <volume>51</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>235</fpage>
          -
          <lpage>245</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Beresi</surname>
            ,
            <given-names>U. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Song</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruthven</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Why did you pick that? Visualising relevance criteria in exploratory search</article-title>
          .
          <source>In: Int. J. on Dig. Lib</source>
          .
          <volume>11</volume>
          (
          <issue>2</issue>
          ), pp.
          <fpage>59</fpage>
          -
          <lpage>74</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>D:</given-names>
          </string-name>
          <article-title>The State of the Touch-Screen Panel Market in 2011</article-title>
          . In: Walker Mobile,
          <string-name>
            <surname>LLC</surname>
          </string-name>
          ,
          <source>SID Information Display Magazine</source>
          ,
          <volume>3</volume>
          .
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>White</surname>
            ,
            <given-names>R. W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kules</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drucker</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          , schraefel, m. c.:
          <article-title>Supporting Exploratory Search</article-title>
          .
          <source>In: Comm. of the ACM 49</source>
          ,
          <issue>4</issue>
          .
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Trattner</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : QUERYCLOUD:
          <article-title>Automatically linking related documents via search query (Tags) Clouds</article-title>
          . In
          <source>: Proc. of the IADIS Int. Conf. on WWW/Internet</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Mackinlay</surname>
            ,
            <given-names>J. D.</given-names>
          </string-name>
          : Technical Perspective:
          <article-title>Finding and Telling Stories with Data</article-title>
          .
          <source>In: Comm. of the ACM 52</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Byström</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hansen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Conceptual framework for tasks in information studies: Book Reviews</article-title>
          .
          <source>In: J. Am. Soc. Inf. Sci. Technol</source>
          ., Vol.
          <volume>56</volume>
          ,
          <issue>10</issue>
          , pp.
          <fpage>1050</fpage>
          -
          <lpage>1061</lpage>
          , John Wiley &amp; Sons, Inc., New York, NY, USA,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>