1. One-minute paper debriefing
Big Points:
User control
Sometimes user control may not be what users really want or need
Design and implementation are embedded in organizational culture/politics
International perspective on research
Control demands attention, sometimes being lazy is smart; cognitive intertia mitigates change

Questions:
 How do multidisciplinary HCI teams work in industry?
 How can we offer control to users with overwhelming them?
 Why so much re-invention of interfaces (e.g., a conference kiosk for one conf should be adopted in another)
 Readings on automatic XML “indexing”?
 Readings on recommender systems?
 How is HCI interfaces related to design of cars/cities/etc.

2. Christel’s paper:
Well-stated design goal: “…communicate essential content of a video on an order of magnitude less time.”
The skim as a surrogate (4 variations)
How to embed the skims in a retrieval system?

3. HCI Roots and Trends
(note N&O cell phone browsers article)

4. Move to lab for white board session on query design

Design exercise.  Develop a query screen mockup.  The mockup should allow people to articulate queries to a retrieval system.  The context could be anything you define, e.g., WWW retrieval with a webpage; a mobile device to retrieve voice mail; a web page to retrieve video clips; etc.  The mockup can be paper sketches (e.g., with sticky notes to show “depth”); an HTML page, etc.  The following must be specified in accompanying ‘documentation.’
Document space (the database(s) upon which queries are cast)
Query form (the input mode, e.g., type, speak, gesture, click)
Query rules (whether queries are qualified, if so, how—e.g., Boolean connectives)
 

5. One-minute paper
What was the big point you learned in class today?
What is the main, unanswered question you leave class with today?