<!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>Users2Story - On the Importance of Understanding Searchers' Information Needs</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Udo Kruschwitz University of Essex</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Uncovering the storyline of events can be of interest for numerous reasons. For example, looking at it through information retrieval glasses (with a touch of personalisation), one might want to string together the various search requests and browsing patterns of an individual user to understand what this user might be after, what information needs are actually hidden behind those queries with the aim of o ering better information access support. We all know what interesting stories can actually be derived like this as illustrated by the analysis of the AOL query logs, and the \AOL search data leak" also demonstrates the problems with privacy when analysing user's Web search logs. If however we move from a Web search scenario to a professional search scenario such as search within an organisation, then we note that privacy issues turn out to be much less of a problem. At the same time, it becomes even more desirable to capture the search and browsing patterns of users because nding information in this context can be very di cult and without understanding the user it can become a very frustrating exercise for the searcher trying to nd the document(s) relevant for the task at hand. The talk will explore this use case in some detail and in the best case will be seen as a di erent take on the main theme of the workshop (and in the worst case will be judged as \o topic" with no chance of re-invitation).</p>
      </abstract>
    </article-meta>
  </front>
  <body />
  <back>
    <ref-list />
  </back>
</article>