SFMOMA-DAM Digital Asset Management System San Francisco Museum of Modern Art

1. SFMOMA-DAMDigital Asset Management SystemSan Francisco Museum of Modern Art Margo Dunlap, Thoreau Lovell, Joanna PlattnerSIMS 213 May 1, 2001

2. Overview • Problem Statement • Design Process • Evaluation • Design Iterations • Formal Experiment Design • Lessons Learned & Future Work • Demo Joanna Plattner | Margo Dunlap | Thoreau Lovell

3. Problem Statement • SFMOMA needs to manage its growing digital asset collection • Existing collections management system is inadequate • Doesn’t support image metadata needs • Limited to permanent collection art works Joanna Plattner | Margo Dunlap | Thoreau Lovell

4. DAM System Overview: Four key components Diagram Joanna Plattner | Margo Dunlap | Thoreau Lovell

5. Design Process Discovery Design Exploration Design Refinement Production Joanna Plattner | Margo Dunlap | Thoreau Lovell

6. Design Process Needs Assessment • User Interviews • Personas • Paper Prototype Discovery Design Exploration Design Refinement Production Joanna Plattner | Margo Dunlap | Thoreau Lovell

7. Design Process • 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 Discovery Design Exploration Design Refinement Production Joanna Plattner | Margo Dunlap | Thoreau Lovell

8. Design Process • Interactivity • Interactive Prototype 2/3 • Still no graphic design • More iteration necessary! Discovery Design Exploration Design Refinement • Prepare design for handoff Production Joanna Plattner | Margo Dunlap | Thoreau Lovell

9. Evaluations Joanna Plattner | Margo Dunlap | Thoreau Lovell

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

11. Heuristic & Exploratory Evaluation: Key Points • Image Request Management • IR form layout • IR selection • Search documentation • Cataloging interaction flow Joanna Plattner | Margo Dunlap | Thoreau Lovell

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

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

14. Object Record: Key improvements Before After Follows new interaction design rule: Where there are images there are “add to” icons Not actionable – a static page Joanna Plattner | Margo Dunlap | Thoreau Lovell

15. Image File Request: Key improvements Before After Users had to page down to view the images that they had just added to the image request Used the “contact sheet” to close the Gulf of Evaluation - “is this the form I think it is?” Joanna Plattner | Margo Dunlap | Thoreau Lovell

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

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

18. Formal Experiment Design • Blocking and Repetitions Three trials per block, 18 total participants. Record set order (1-15) same for each block. 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 Joanna Plattner | Margo Dunlap | Thoreau Lovell

19. Formal Experiment Design • Hypotheses • Allowing users to chose the order of record creation would result in faster record creation. • Requiring users to add object records first, then image records would result in fewer data entry errors. • Hiding Parent / Child relationships would result in faster record creation. • Always displaying Parent / Child relationships would result in fewer data entry errors • 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

20. Lessons Learned • Put interaction design front and center • Differentiate client feedback from user feedback. • Hard to test an immature system Joanna Plattner | Margo Dunlap | Thoreau Lovell

21. Future Work • More iteration to refine conceptual model • Find the right metaphors • Refine the interaction design • Add additional interactivity • Add additional DB interface screens • Stress-test the database Joanna Plattner | Margo Dunlap | Thoreau Lovell

22. Demo Joanna Plattner | Margo Dunlap | Thoreau Lovell