Archive for February, 2009

Reading Notes for Intro to IA, 20090223

February 23rd, 2009  |  Published in Information Architecture

Week 5 – (Feb 23, 2009) Analysis – User Modeling, Browsing and Searching Primary Readings

Rosenfeld, Information Architecture: Chapter 7 (Navigation Systems) and 8 (Search Systems)

  • Navigation adds windows and doors to the site.
  • UX Design includes IA + IXD + Info Design + Visual Design + UX Engineering (collaborative design across disciplines works best — with experts blurring the lines between disciplines)
  • Note the flashback reference to Gopher (strict hierarchical navigation which limited flexibility)
  • Note that frames violate the page paradigm.. bad for usability, accessibility
  • Navigation needs to: Balance context & flexibility
  • Consists of Global, Local and Contextual navigation + supplemental nav tools such as sitemaps, indexes, guides, wizards, configurators
  • Newer tools include personalization, visualization, tag clouds, collaborative filtering, and social navigation

Issues to consider when implementing search: Sear is not an IT thing. It needs to managed as an information problem — not a technical problem.

  • Does the site need a search tool?
  • The anatomy of a search engine.
  • What should be searchable?
  • Note retrieval algorithms.
    • Pattern Matching: compare search string to index of content
      • Recall: # relevant docs retrieved/#relevant docs in the collection
        • automatic stemming: expand search term to include other terms with same root (stem)..for higher recall
      • Precision: # relevantdocs retreived/# total docs in collection
        • Search using meta data results in higher precision
      • These terms are inversely related… can’t have your recall and precision too
      • Document Matching: using a good doc as the basis for additional searches
        • Returning docs with similar meta data
        • Collaborative filtering and citation search
  • Query Builders: spell-checkers, phonetic tools, stemming tools, natural language processing, controlled vocabulary and thesauri
  • Careful how you present search results.
    • display less for people who know what they want; more for people who aren’t sure.
  • Consider the design of the search interface: level of search expertise, type of info need, type of info being searched, amount of info being searched. Surprising note in the book: Just say no to advanced seearch — it isn’t used much, so low ROI.

Choo, C. W., Detlor, B., & Turnbull, D. (2000). Information Seeking on the Web: An Integrated Model of Browsing and Searching. First Monday, 5(2).

  • Browser capabilities & other tech environment issues have a huge impact on usage patterns
  • Motivations and search tactics are related
  • Searching incorporates multiple, complementary methods of collecting quantitative and qualitative data

Tauscher, L. M., & Greenberg, S. (1997). Revisitation patterns in World Wide Web navigation. Paper presented at the ACM SIGCHI ‘97, Atlanta, GA.

  • Designing history mechanisms in browsers — using empirical data as a foundation
  • Showing the last few recently visited URLs with dupes removed is helpful. Most browsing is to previously viewed pages (58%)

Secondary Readings
Bates, M. After the dot-bomb: Getting Information Retrieval Right This Time. First Monday. 2002.

Kobayashi, M., & Takeda, K. (2000). Information Retrieval on the Web. ACM Computing Surveys, 32(2).

Maglio, P., & Barrett, R. (1996). How to Build Modeling Agents to Support Web Searchers. Paper presented at the Sixth Internation Conference on User Modeling, New York.

Hearst, M. (2000). Next Generation Web Search: Setting Our Sites. Bulletin of the IEEE Computer Society Technical Committee on Data Engineering

Reading Notes for Intro to IA, 20090216

February 16th, 2009  |  Published in Information Architecture

1. Rosenfeld, Information Architecture: Chapter 9. Thesauri, Controlled Vocabularies, and Metadata

  • Metadata: data about data and documents/assets. Hooks used by software and vocabulary systems to deliver meta data-driven websites
  • Controlled Vocabularies: a defined subset of natural language
  • Synonym ring: a list of equivalent terms (may not be true synonyms): dramaticlly improve recall – but decrease precision.
  • Authority file: a list of preferred terms. Useful for authors and indexers.Good for ‘teaching’ a common language, good for facilitating switch between search and browse.
    •  – Term rotation example: aspirin, see Bayer
  • Classification scheme (Taxonomies): hierarchical relationships (broader/narrower) defined, like Dewey/LC. Can be use front-end (yahoo-like browse function) or backend (tool for IAs to organize and tag documents)
  • Thesaurus: a model of equivalence, hierarchicl, associative relationships between concepts used to facilitate information retrieval.
    • –Prefered term/Variant term, Broad/Narrow term, Related term, Use (U), Use For (UF), Scope Note (SN – definition of preferred term)
    • Example site using thesaurus: PubMed from NLM
  • Semantic relationships: Equivalence, Hierarchical, Associative.
  • Preferred Terms:
    • Term form (standardization having to do with grammar, spelling, singular/plural, abbreviation/acronyms)
    • Term selection
    • Term definition
    • Term specificity
  • Polyhierarchy
  • Faceted Classification. S.R. Ranganathan.
    • Five universal facets (dimensions) proposed by SRR: personality, matter, energy, space, time
    • Common facets in busines world: topic, product, document type, audience, geography, price
    • see Wine.com for faceted classification.

2. Morrison, J. B., Pirolli, P., & Card, S. K. (2001). A Taxonomic Analysis of What World Wide Web Activities Significantly Impact People’s Decisions and Actions. Proceedings of CHI 2001, Seattle, WA.

  • Defining and building a set of tasks that represent the real user behaviors so that those behaviors can be modelled and studied.
  • Purpose Taxonomy (Compare/choose, Find, Understand), Method taxonpmy (collect, find, monitor, explore),
  • Content Taxonomy (Product Info & Purchase, Medical, People, Travel, Education, Job search).

3. Wilson, T. D. (2000). Human Information Behavior. Informing Science: Special Issue on Information Science Research, 3(2).

  • I appreciate the definition of “knowledge” as something that is unknowable except to the knower. Therefoer, there is no such thing as a “Knowledge Management System”.  Only informaiton about knowledge cna be transmitted. Knowledge management systems are really just information management systems.
  • The idea that researchers in a well-defined and researched field like organic chemistry might have less need for a “skilled intermediary” and are more prone to be effective independent users of internet search engines and online search systems is curious.
  • It seems that the premise is that these researchers would be beter at assigning appropriate metadata to the descreet documents — allowing for easier retrieval. That may or may not be true, as researchers  may or may not think like IA’s or catalogers.
  • I also am curious to see what Palmer reported from interviews (1991) about male/female diferences in information behavior.
  • It’s interesting that in the 1980’s the author noted a shift from system-centered to person-centered and quantitative to qualitative approaches to the study of information seeking behavior.

4. Millen, D. (2000). Rapid Ethnography: Time Deepening Strategies for HCI Field Research. Paper presented at the DIS ‘00, Brooklyn, NY.

  • Understanding users and their activities quickly. Focus on context of use, interrelationships between users in work groups.
  • Ethnographer is a cultural broker — a translator. Use key informants, and a field guide (person in the study group who can help focus researchers).

5. Krug, Steve. “How do we really use the web?” from Don’t Make Me Think! A Common Sense Approach to Web Usability. 2000. QUE.

  • Web use compared to looking at t billboard going by at 60mph.
  • We often scan web pages.
  • We satisfice (choose the first reasonable option).
  • We muddle through without understanding how things work. (using sites effectively in ways never intended)

6. Smart, K. L., Rice, J. C., & Wood, L. E. (2000). Meeting the Needs of Users: Towards a Semiotic of the Web. IEEE Technology and Teamwork, 593-605.

  • 6 elements often used to describe/evaluate web designs:
    • Typography (use of typeface, layout, color to convey meaning of text)
    • Site structure/cognitive design (how information is organizeed on a site)
    • Medium use (the appropriate/optimal use of Web features)
    • Message content (narrative style)
    • Appeal
    • Accessibility
  • See table for a list of questions used to guide effective web design. (page 603)

Notes for IA Class Readings – 20090209

February 9th, 2009  |  Published in Information Architecture

Structure & Memorability of Websites. Modjeska & Marsh (1997)

  • Strongly hierarchical sites are more usable
  • Nodes high in the hierarchy (closer to the root) are more memorable
  • Strongly hierarchical sites are perceived as smaller than weakly hierarchical sites.
  • Site size has little impact on user nav & mental models

Boxes and Lines over Bullets and Arrows: Deliverables that Clarify, Focus and Improve Design. Fulcher, Glass, Leacock

  • Concept Maps: capturing users’ mental models
  • Wireframes & Storyboards: great for iterative prototyping.
  • Flow Maps: navigation & high-level product behavior
  • Detailed Mockups & Functional Specs: Production-ready materials

Web Page Design: Implications of Memory, Structure and Scent for Information Retreival. LArson & Czerwinski.

  • Balancing breadth and depth ouperforms broad & shallow web structures

Information Architecture — Notes, Chapter 5 – Organization Systems

February 9th, 2009  |  Published in Information Architecture

Continued notes from Information Architecture for the World Wide Web by Peter Morville& Lou Rosenfeld.

Classification is difficult because: language is ambiguous; heterogeneity (collections of unrelated parts)(variety of granularity, format),  differences in perspectives (mental models of labeling and organization), internal politics.

Organization systems = schemes (shared characteristics of content) + structures (kinds of relationships between content items & groups)

Simple Schemes:

  • Alphabetical – great for known-item searching (phone book)
  • Chronological – (archive of press releases)
  • Geographical – (map-based select a location)

Ambiguous (subjective) Schemes: support serendipitous searching –like Dewey, LC

  • Topic
  • Task
  • Audience
  • Metaphors (requires a lot of familiarity and may accidentally limit applications online –watch scalability)
  • Hybrids (shallow use of hybrid schemes may work well to define a limted set, but scalability is difficult. Group like-themes together instead of mixing a variety of schemes together)

Organizational Structures

  • Hierarchy (top-down): Generally, categories are mutually exclusive, but may need to cross-reference items to boost findability. If too many items are cross-listed, the hierarchy loses value. (exclusivity vs inclusivity). Also consider balancing breadth and depth of the taxonomy (too many choices vs. too many clicks)
    • taxonomy – hierarchical arrangement of categories in a user interface
    • facets – different ways of  looking at the same information yields differents facets
  • The Database Model (bottom-up approach): enabling dynamic indexes, see also links, advanced searching (fielded searches?), filtering & sorting of search results
  • Hypertext -great compliment to a strong hierarchy

Social Classification

Folksonomies are very popular. Is there evidence yet of their performance vs. traditional approaches to organization?

Most sites use a variety of organizational structures.

Introduction to IA – Professor Turnbull – Class notes 20090202

February 7th, 2009  |  Published in Information Architecture

Mentioned in class:

Primary Readings for next week

Secondary Readings