information architecture & design

28
Information Architecture & Information Architecture & Design Design Week 5 Schedule - Planning IA Structures - Other Readings - Class Work: User Analysis - Project Plan Review - Group Work: Planning the Project Site

Upload: ida

Post on 09-Jan-2016

37 views

Category:

Documents


2 download

DESCRIPTION

Information Architecture & Design. Week 5 Schedule Planning IA Structures Other Readings Class Work: User Analysis Project Plan Review Group Work: Planning the Project Site. Class Work: Planning a Site. What kind of site will you build? Informational Entertainment Portfolio - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Information Architecture & Design

Information Architecture & Design Information Architecture & Design

• Week 5 Schedule- Planning IA Structures- Other Readings- Class Work: User Analysis- Project Plan Review- Group Work: Planning the Project Site

Page 2: Information Architecture & Design

Class Work: Planning a SiteClass Work: Planning a Site

• What kind of site will you build?- Informational- Entertainment- Portfolio- Content display- Context with links

• What resources do you have?- Content- Ideas- Circumstance

• Discuss up your ideas (10 min)

Page 3: Information Architecture & Design

Group Work: Building a Site PlanGroup Work: Building a Site Plan

• Discuss your ideas with your neighbor• Do you have too much initially planned?• Who is your user audience?• What will the site be used for?• Why would someone want to use your site?• What are the goals of the site?

Page 4: Information Architecture & Design

Thesauri, Vocabularies & MetadataThesauri, Vocabularies & Metadata

• The Structure of Your Content (Part of the Plan)• Models the Information for the User (Content Modeling)• What Do You Do With Your Project Data (Content)?

- Context

• Descriptive• Prescriptive

- Quality

• Accuracy• Recency

- Characteristics

• Media / MIME type• Uses

• Represent the Relationships Between Systems

Page 5: Information Architecture & Design

What do we mean by Metadata?What do we mean by Metadata?

• What are some examples of metadata?

• “…descriptive information about the context, quality and condition, or characteristics…”

• Variability (does it depend on the situation?)• Intended uses?- Is there a ideal world of (forms) metadata out

there?

• Metadata can define the context

Page 6: Information Architecture & Design

Controlled VocabulariesControlled Vocabularies

• Establish Consistencies• For the Content• For the Developers• On the Site – Apparent to the Users

• Just Synonyms?• Lists of Equivalents (Index)• Aliases (Authority File)• Also an Implied or Overt Hierarchy

• “Synonym Ring” (which isn’t) p178

• Based on User’s Understanding• Improved Upon by IA• Iterative Process to Discover Alternate Words & Concepts• Not Just for Search

Page 7: Information Architecture & Design

Building Your “Authority File”Building Your “Authority File”

• List of preferred terms or acceptable values p180

• The Mission Statement for your Content- Acronyms, Abbreviations- Multiple terms (“term rotation”?)- Cases (Upper, Lower and Mixed)- Labels for Button & Graphics too

• Use a Central File to Keep Current- Authority.txt

- Keep updated throughout the project

Page 8: Information Architecture & Design

Classification SchemesClassification Schemes

• Taxonomy (more than one?)- Front End

• Users (Personalized)• Interface (Browse)

- Back End• Information Architecture• Content Management• System (Search)

- Technical Approaches• LIS & CS• Top-Down & Bottom-Up• Content & Task• All of the above?

Page 9: Information Architecture & Design

Semantic RelationshipsSemantic Relationships

• Equivalence (Alternate Names)- Derived (Rules)- Vocabulary (Uses)

• Hierarchical (Relationships)- Strong (Inherited)

• City - Austin- Instance (Classes)

• Texas - Austin

• Associative (Checklist for Approval)- Based on Understanding of Content- Based on Understanding of Users

Page 10: Information Architecture & Design

Thesauri - What kind do you need?Thesauri - What kind do you need?

• Hierarchical Relationship• Equivalence Relationship• Associative Relationship

- Preferred Term- Varian Term (synonyms)- Broader Term (preferred’s parent)- Narrower Term (preferred’s child)- Related (“see also”, synonyms)- Use (rules for where and when)- Scope (restricts meaning)

Page 11: Information Architecture & Design

Thesaurus TypesThesaurus Types

• Classic- Links- Keywords

• Subject Index• LoC

• Index- Browsable

• Appearance• Ordering (Multiple orders)

- Relational• See also• Hierarchy

• Document versus Site

Page 12: Information Architecture & Design

Faceted ClassificationFaceted Classification

• Multiple Dimensions• Now More Applicable to Digital Information- Personality, Matter, Energy, Space, Time- Topic, Product, Document Type, Audience,

Geography, Price

• Commerce Examples• What other kinds of views?

• Flamenco

Page 13: Information Architecture & Design

Taxonomy of Decisions & ActionsTaxonomy of Decisions & Actions

• Now – not just the taxonomies of content, but how people work

• Purpose of the Search• Method to Find Information• Content of the Information Being Searched• GVU Survey Question- Recent instance of important information found

• Critical Incident Technique- Complete Instances- Known Consequences (Results)

• Morrison 2001

Page 14: Information Architecture & Design

Taxonomy pt. 2Taxonomy pt. 2

• Taxonomies of Web Activities- Why people searched the Web- How search the Web- What information searched

• Analysis of Responses from Survey into Experiment

• Purpose Taxonomy• Method Taxonomy• Content Taxonomy

Page 15: Information Architecture & Design

Human Information BehaviorHuman Information Behavior

• Information Seeking (Strategies)• Information Searching (Strategies)• Information Use- Physical Actions- Mental Actions

• Focus on the User

• Wilson 2001

Page 16: Information Architecture & Design

New Models of Info Behavior pt. 2New Models of Info Behavior pt. 2

Page 17: Information Architecture & Design

New Models of Info Behavior pt. 3New Models of Info Behavior pt. 3

• Problem Solving• System Actions• Integration of Actions

Page 18: Information Architecture & Design

Rapid EthnographyRapid Ethnography

• Like Rapid Prototyping & Usability Inspection• Field Work (is being there half the work?)

- Wide-angled lens

• Ethnography- People (Practice)- Environments (Native)- Activities (Context)

• Cultural Observation and Analysis• Elicit User Requirements• More Focused (Decisions)

• Millen 2000

Page 19: Information Architecture & Design

Rapid Ethnography pt. 2Rapid Ethnography pt. 2

• Short Studies• Comparisons to Other Studies• Zoom in On Key Activities• Multiple Datasets (Critical Incidents)

- Observations- Recording- Activity Walkthroughs- Interviews (Structured)

• Selection of Instances that Yield Incidents- Key Times- Key Users

Page 20: Information Architecture & Design

Rapid Ethnography pt. 3Rapid Ethnography pt. 3

• Automated Data Analysis• Team Data Analysis• Scenario Analysis (storyboards)• Pictorial Storytelling (metaphors)• Lightweight Deliverables

- Drawings (Sketches)- Notes (not Reports)- Incomplete- Prototypes

• Cognitive Mapping (assumptive)

• Substitute for Full or Complete Studies

Page 21: Information Architecture & Design

How Do We Really Use the Web?How Do We Really Use the Web?

• Reading vs. Scanning- Quality of Elements- Quantity of Elements- Purpose of Pages

• Satisficing- Guessing with Speed- Low Penalties (Back)- Testing Boundaries

• Muddling and Forging Ahead- Stick with what works- Not concerned with understanding

• Krug 2000

Page 22: Information Architecture & Design

Design vs. PracticeDesign vs. Practice

Page 23: Information Architecture & Design

Semiotics of the WebSemiotics of the Web

• Site Structure and Cognitive Design- Typography

• Medium use- Browsers

• Message content- Paper- Web

• Appeal- Attention (interest)- Relevance (needs and motives)- Confidence (expectation & achievement)

• Accessibility- Culture- Physical

• Smart, et al. 2000

Page 24: Information Architecture & Design

Learning and Interests (Users)Learning and Interests (Users)

• Learning is Remembering What You’re Interested In

• Cultivating Interest• Relevance• Interests vs. Obligations• Examples for Understanding- Metaphors- Content Presentation

• “Architecture is Making Connections”

Page 25: Information Architecture & Design

Designing for UsersDesigning for Users

• Permutations• Connections• Facts vs. Ideas• Discovery vs. JITI

Page 26: Information Architecture & Design

Class Work: Who Will Use the Site?Class Work: Who Will Use the Site?

• Who are your target users?• All of the possible users?• What do you want users to get from your site?• Is the site a Searching (JiTi) site?• A Browsing and Learning site?• Do you need different taxonomies for each

type of user?• What’s the best general taxonomy for

describing and organizing your site?

Page 27: Information Architecture & Design

Group Work: User AnalysisGroup Work: User Analysis

• What do your users have in common?• What are their differences?• What design decisions need to be specifically

planned for as essential for your users?• What will the information on your site be used

for? (Wilson)• Rapid Ethnography – take on the role of some

of your users and ask questions.

Page 28: Information Architecture & Design

Deliverables for Next WeekDeliverables for Next Week

• Sitemap diagram of your proposed project- One page, printed

• Include your name and email address

• User model (scenario starter) - One page, printed- Include your name and email address

• What the site is about• In two sentences (at most)

- Briefly describe • Who will use the site• Why?• When?

• Save this digital document for part of your class project portfolio• Due at the beginning of class next week• Start thinking about the controlled vocabulary for your site