Search, find and destroy

2,305 views

Published on

A short presentation made on the 3rd of november at the Jboye10 conference (UX track) in Aarhus, Denmark.

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,305
On SlideShare
0
From Embeds
0
Number of Embeds
625
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Keep the search result page response time under (an average of) 0,2 seconds.
    Our goal is to reduce the response time to 0,1 seconds (on average).
    This is a very important principle for us.
    Read more about the users experience of response times.
    http://www.useit.com/alertbox/response-times.html
  • All sources/systems are in one index.
    We have 10 different systems/information sources indexed, 4 more will be added in the coming months which adds up to more than 1 million documents in total for the index .
    One basic search GUI for all systems/sources that are indexed.
    This is sometimes called “universal search”.
    All informationtypes can have a different set of facets.
    Our goal is to also use “federated search”, meaning that a search query is sent to more than one search function (=more than one index/database). For example, a search query is sent to our search engine and it’s index and at the same time is sent to a database for scientific articles.
    Search results are then blended in one search result page.
  • A scope is a defined smaller part of the larger index, could be seen as a chapter in a book.
    A scope can overlap another scope.
    A scope can also consist of several smaller scopes.
    Limit the recall by using scopes.
    Allow the organisation to have their own scopes in the search index .
    Allow a specific subject (e.i. “HR”) to have a scope.
    Limit the site-search to the site’s scope.
  • Use filters/facets to:
    narrow the search
    increase precision
    “navigate” the search results
  • Not all results are the same.
    Treat the individual search results differently on the same search result page.
    Use Tiles to differentiate search results from different sources.
    For example, an event is not shown the same way as a document.
    Use key-matches to show a set first result, based on a given number of keywords.
  • Give everyone the possibility to:
    access to basic search statistics
    see all key-matches
    suggest new key-matches
  • Allow users to give structured feedback.
    This is done via a simple web form (that fetches a little information about the users operating system, web browser, IP-address etc in order to help with support issues and troubleshooting)
    We get feedback, not a lot, but all the feedback so far has been useful. A few issues every week.
    We always answer whoever has given us the feedback (if they filled out contact info).
    This builds trust.
    Typical feedback: A user can’t find a series of documents. We investigate, and address the problem. This is sometimes related to bugs, the relevancy model or the content itself that must be improved, eg. adding metadata, better headings etc. This often boils down to helping content editors and training them to do “the right thing”.
  • Q&A
  • Q&A
  • Search, find and destroy

    1. 1. Search, find and destroy? A live experience Kristian Norling IT strategic department Region Västra Götaland KristianNorling
    2. 2. “It’s not Google, but it’s a nice effort.”
    3. 3. Design principle #1 0,2
    4. 4. Design principle #2 One
    5. 5. Design principle #3 Slice ‘n dice
    6. 6. Design principle #4 Filters
    7. 7. Design principle #5 Tiles
    8. 8. Design principle #6 Transparency
    9. 9. Design principle #7 Feedback
    10. 10. Demo
    11. 11. Questions?
    12. 12. Thank you!
    13. 13. kristian.norling@vgregion.se www.slideshare.net/kristiannorling twitter.com/kristiannorling www.linkedin.com/in/kristiannorling sys64738.se More about this subject on my blog:

    ×