SFMOMA-DAM Digital Asset Management System San Francisco Museum of Modern Art
description
Transcript of SFMOMA-DAM Digital Asset Management System San Francisco Museum of Modern Art
SFMOMA-DAMDigital Asset Management
System
San Francisco Museum of Modern Art
Margo Dunlap, Thoreau Lovell, Joanna Plattner
SIMS 213 May 1, 2001
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 2
Overview
Problem StatementDesign ProcessEvaluationDesign IterationsFormal Experiment DesignLessons Learned & Future WorkDemo
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 3
Problem Statement
SFMOMA needs to manage its growing digital asset collection
Existing collections management system is inadequateDoesn’t support image metadata needsLimited to permanent collection art works
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 4
DiagramDAM System Overview: Four key components
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 5
Design Process
Production
Design Refinement
Design Exploration
Discovery
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 6
Design Process
Production
Design Refinement
Design Exploration
DiscoveryNeeds Assessment
User InterviewsPersonasPaper Prototype
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 7
Design Process
Production
Design Refinement
Design Exploration
Discovery
* Develop a number of design possibilities * Straight to HTML pages?
* Or Focus on Interaction Design (Information & Navigation design)
* IA Diagrams* Storyboards * Then HTML pages
* No graphic design* Awkward Transition
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 8
Design Process
Production
Design Refinement
Design Exploration
Discovery
* Interactivity* Interactive
Prototype 2/3* Still no graphic
design* More iteration
necessary!
* Prepare design for handoff
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 9
Evaluations
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 10
Task Scenarios
Low-fi, 1st Interactive & Heuristic Evaluation 1. Search 2. Request Image 3. Catalog Image
Pilot Usability 1. Search 2. View Images 3. Create DAM record
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 11
Heuristic & Exploratory Evaluation: Key Points
Image Request ManagementIR form layout IR selectionSearch documentationCataloging interaction flow
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 12
Pilot Study: Key Points
Navigation Clarity of terminology Ease of adding new records Search View images Object Relationships Documentation, descriptions, and labels
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 13
Search Results: Key improvements
Before After
Large thumbnails meant lots of scrolling or “next page” clicks to see all results
Tighter layout reduces navigation steps, added icons as links to image request and saved results (“damfolio” )
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 14
Object Record: Key improvements
Before
Not actionable – a static page
After
Follows new interaction design rule:
Where there are images there are “add to” icons
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 15
Image File Request: Key improvements
Before After
Used the “contact sheet” to close the Gulf of Evaluation - “is this the form I think it is?”
Users had to page down to view the images that they had just added to the image request
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 16
Image File Request: Key improvements
. . .
Before After
Moved Save/Submit buttons to end of image list where evaluators expected to find them. Also added “step by step” instructions at the top of the page to guide users.
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 17
Formal Experiment Design Experiment focus
Data entry speed and accuracy Varying the interface on two dimensions:
The order of record creation Display of parent / child relationships.
Response Variables (dependent variables) Time & Errors
Factors / Levels (independent variables) Order of record creation
Object Records first Image Records first User’s choice: Either Object or Image Records
Default Display of Parent / Child relationships Always displayed Hidden: User chooses to display
Within-groups design
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 18
Formal Experiment Design Blocking and Repetitions
Displayed Hidden
Obj Img
Img Ch
Ch Obj
Displayed = P/C relationships always displayed
Hidden = P/C relationships hidden until user requests
Obj = Object records created first
Img = Image records created first
Ch = Users choice
Three trials per block, 18 total participants.
Record set order (1-15) same for each block.
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 19
Formal Experiment Design
Hypotheses1. Allowing users to chose the order of record creation
would result in faster record creation.
2. Requiring users to add object records first, then image records would result in fewer data entry errors.
3. Hiding Parent / Child relationships would result in faster record creation.
4. Always displaying Parent / Child relationships would result in fewer data entry errors
5. The time it takes to add a single record set (object and images) would be slowest for records 1-5, would increase dramatically for records 5-10, and would level off between records 10-15.
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 20
Lessons Learned
Put interaction design front and centerDifferentiate client feedback from user
feedback.Hard to test an immature system
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 21
Future Work
More iteration to refine conceptual modelFind the right metaphorsRefine the interaction designAdd additional interactivityAdd additional DB interface screensStress-test the database
Joanna Plattner | Margo Dunlap | Thoreau Lovell IS213 Spring 2001 22
Demo