Lesson overview
Introduce information retrieval as the design of systems that connect users with useful information, whether the user is searching directly, browsing categories or refining an unclear need.
Starter
Write down the user need, the data being stored or searched, and the decision the system has to support. Then predict which representation, index, query method or governance control will matter most in this lesson.
Learning objectives
- Distinguish retrieval from simple data lookup.
- Classify user information needs as known-item, fact-finding, exploratory or monitoring tasks.
- Explain how browsing, querying and feedback support query formulation.
Learning outcomes
- Students can distinguish retrieval from simple data lookup.
- Students can classify user information needs as known-item, fact-finding, exploratory or monitoring tasks.
- Students can explain how browsing, querying and feedback support query formulation.
Key vocabulary, acronyms and terminology
- information need
- A gap between what a user knows and what they want to know.
- known-item search
- A task where the user is trying to find a specific item already partly known.
- exploratory search
- A broad task where the user learns, reformulates and narrows the need.
- browsing
- Navigation through categories, facets or links rather than direct keyword entry.
- query formulation
- The act of expressing an information need in words, filters or other system inputs.
- relevance
- Usefulness of an item for the current user need.
Detailed teaching notes
Core concept
Information retrieval is not just storing records and returning exact matches. A retrieval system must interpret a human information need, represent the collection, compare the need with candidate items and present ranked or browsable results.
Representation choice
The same need can be expressed as a keyword query, a set of filters, a natural-language question, a clicked facet or a trail of browsing behaviour. The system should preserve enough context to support reformulation without pretending that the first query is always the real need.
Method and reasoning
Begin by classifying the search situation. Known-item tasks reward exact identifiers and metadata. Exploratory tasks need suggestions, facets, snippets and feedback because the user may not yet know the vocabulary of the collection.
Risk and limitation
A common design error is to optimise for exact matching when the user actually needs sense-making. If the user is exploring, an empty result is not enough; the interface should reveal adjacent terms, categories or examples.
Degree-level deep dive
Intent before interface
At degree level, retrieval starts with the user's information need, not the search box. A known-item search, a fact-finding search and an exploratory search can use the same words but require different support, ranking evidence and browsing structure.
Query as evidence, not truth
A query is a partial expression of a need. Strong answers explain what the query reveals, what it hides, and how the system can use snippets, facets, spelling suggestions, related terms and click feedback to help the user reformulate.
What excellent work shows
A strong response names the user goal, classifies the need, chooses search or browsing support, then states how success would be judged. It should avoid treating relevance as a property of a document alone; relevance is document usefulness in a situation.
Concrete example to study
Mini query log
User A: q='1984 Orwell' -> known-item need
User B: q='causes of database deadlock' -> fact-finding need
User C: q='how communities preserve local history' -> exploratory needReasoning
- User A needs exact matching, title/author metadata and perhaps edition filters.
- User B needs a concise answer path, reliable sources and vocabulary support around 'deadlock'.
- User C needs browsing by topic, place, period, format and related terms because the final information need will develop while searching.
Reveal takeaway
The same search interface can serve all three users, but a degree-level answer explains why each need requires different ranking, browsing and feedback support.
Worked example
Scenario
A student wants material on 'how websites find pages' but does not know the term crawler.
Worked solution
- Classify the need as exploratory because the student has a topic but not the right technical vocabulary.
- Identify likely vocabulary bridges: web search, crawler, spider, index, sitemap.
- Choose interface support: suggestions, related topics and a browsing route under retrieval architecture.
- Judge success by whether the student can reformulate the need as a more precise query after seeing results.
Reveal model result
The system should not simply return zero results for an imprecise phrase. It should support query formulation by connecting the user's wording to crawler and indexing vocabulary.
Applied retrieval task
Design the first screen of a search tool for a small university archive.
Deliverables
- List three different information needs: known-item, fact-finding and exploratory.
- Choose whether each need is best served by search, browsing, filters or a mixture.
- Write one interface feature that helps the user reformulate a weak query.
Success checks
- The design names the need, not only the widget.
- The features are tied to realistic user behaviour.
Common misconception
Students often describe retrieval as if it were exact database lookup. Retrieval is usually uncertain: the query is an approximation, relevance is contextual and browsing may be part of the answer.
Quick checks
1. In this lesson, why does information need matter?
2. Which answer best shows degree-level understanding of information retrieval, browsing and user needs?
Digital exam practice
Example exam task
A digital library receives the query 'old climate policy speech' from a user who wants to learn the topic rather than locate a named document. In your answer, define the relevant objects or data structures, use course-specific vocabulary, show the method rather than only the result, and finish with a decision about the storage or retrieval system.
Notation and technical toolkit
What a good answer is expected to show
A strong answer for Information Retrieval, Browsing and User Needs the answer should classify the need as exploratory, explain why the query is only a partial expression of that need, and propose retrieval and browsing support that helps the user reformulate. It should connect the formal or technical representation to the user's information need instead of listing terms without using them.
How to solve it
- Classify the user's information need before designing the response.
- Explain why exact keyword matching may miss relevant records.
- Add browsing support such as topics, dates, speaker facets and suggested terms.
- State how feedback from clicked results can improve the next query.
Model answer
Reveal model answer
The need is exploratory because the user is trying to learn a topic and does not yet identify the exact speech. I would treat q = 'old climate policy speech' as an imperfect expression of N, return ranked candidate speeches, and offer facets for date, speaker, country and policy topic. Suggestions such as 'climate legislation', 'environment speech' and named policy bodies would help the user reformulate. Relevance should be judged against the information need, not only against the literal words in the first query.
Practise next
- Classify three search tasks from a museum website as known-item, fact-finding or exploratory.
- Write two query-reformulation suggestions for a weak query in a course catalogue.
Self-marking criteria
- Defines the scenario objects, data forms or system components before solving.
- Uses the lesson vocabulary accurately and in context.
- Shows a clear method with enough working for a marker to follow.
- Connects the result back to retrieval, storage, analytics or governance.
- States a limitation, trade-off or quality risk rather than presenting the answer as absolute.
Extension
Compare the same information need on a search engine, a library catalogue and a video platform. Identify which system gives the strongest support for reformulation.
Study route
Save a short worked answer from this lesson using this pattern: define the need or data, choose the representation, show the method, state the result and interpret the implication for the system.
Next lesson: Structured, Semi-Structured and Unstructured Data.
