|
5.1 Revised Interface Design
Task Scenarios for 1st Interactive Prototype
Task Scenario 1: As Sophie, a curatorial assistant,
you need to search for images for the planning of an exhibit called "Exits."
You need to check on the existence of digital images for several art pieces.
- Search for art pieces using keyword "blue."
- Print list of art objects with thumbnails.
- Return to Home.
Task Scenario 2: As Robin, a multimedia content
developer in the Education Department, you need access to digital image
files of varying resolution quality for an interactive presentation in
support the upcoming exhibit called, "Exits."
- Request use of a high resolution digital image of
"blue" by Richard Diebenkorn.
- Request use of a low resolution digital image of "Blue
Kerrig" by James Brooks.
- Go to your Image Request.
- Complete Image Request specifying due date April 1,
2001 and resolution quality.
- Return to Home.
- Review status of Image Request# IR789.
Task Scenario 3: You are
a Digital Imaging specialist at SFMOMA and you spend virtually 100% of
your time creating, documenting, and managing digital images. You process
a high-volume of images and like to work quickly. Robin in Interactive
Educational Technologies needs images of three Richard Diebenkorn prints
for a project called California Arts Revisited. The Image Request for
this job IR123. This scenario includes the following tasks:
- Review Image Request No.123 and answer the following
questions: · Do master images exist, or will you have to create them?
- What resolution image files are being requested?
- When is the requested delivery date for the job?
- Following standard digitizing procedure, you created
both Source and Browse class images for Image Request IR123.
- Indicate that you created Source class images for
all three paintings using CIA Source Class 3 settings. Save this
information.
- Indicate that you created Browse class images for
all three paintings using CIA Browse Class 1 settings. Save this information.
- For Tri-Color only, change the compression ratio
to 4:1 for the Browse class images.
- Save this information.
- Deliver the images requested on IR123.
Design Changes
| Low-fi |
First Interactive |
|
Single interface for:
a. Users & Creators
b. Standard & Advanced image requests.
|
Separated interfaces and added several
screens to better support user tasks. |
|
Liberal use of specialized terminology, links to
help screens were ignored
|
Relegated specialized terms to new Advanced image
request screen. |
|
Vague navigation labels; were misunderstood more
often than not
|
Simplified nav bar, made labels more task oriented
|
|
Unstructured search (like google), left one user
uncertain about what to put in. He was fearful the result set would
be too high.
|
Added explanatory text to basic search, added “Advanced
search” to support search by attribute (artist, title, etc.) |
|
Used a tabbed interface to distinguish “access”
requests from “new digitiza-tion” requests.
|
Eliminated new digitization requests (for now) -
a challenging problem! |
|
Minimal feedback, no confirmation that an image
request had been submitted
|
New confirmation screens for saving and submitting
image requests. |
| No attempt to support image file distribution
or pickup process. |
Added screen in support of image creator's
"file delivery" task. (Not part of the current three scenarios).
Added screens in support of the image requestor's "file pickup"
process. Users drill-down to image file directory via hyperlinks. |
top
Storyboard
5.2 Prototype Overview
The first interactive prototype of
SFMOMA DAM supports key tasks for image creators and image users. The
interface specifically supports search, requests for image access, and
cataloging of new images.
The interface includes the following pages:
- Home
- Search
- Search Results
- Manage Image Requests
- Image Request Form
- Image Request Status
- Image File Directory (file pickup)
- Image Request Processing/Catalog Form
- Image File Delivery Form
Items left out of Interactive Prototype
Groups/Portfolios/Projects
Museum staff currently create and manage customized groups of objects
in Embark, the collections management system. We believe the concept of
groups is a powerful feature that must be supported by the DAM system.
Implementation has been tabled due to our unfamiliarity with the use and
functionality of portfolios in Embark. We estimate that the implementation
of DAM groups will resemble image requests.
Scrolling Search Results
The Interactive prototype includes one canned search result limited to
four records. Longer search results will be displayed on multiple pages
limited to ~10 hits per screen and will inform user of number of pages.
All Purpose Search
We modified Search to a quick search and advanced search. Quick Search
limits queries to keywords including artist, title, and accession number.
Advanced Search supports multiple word queries across multiple data fields.
Browse
Browse of objects and workflow items (such as image requests and groups)
is tabled. Previous needs assessment for an information visualization
project identified that users prefer specific queries on artist, title
or accession id.
Request Digitization of Image
We modified Robin's task scenario to request use of existing images instead
of the previous request for digitization. We are still debating whether
an object record would exist in the DAM system if the object did not have
an associated digital image. See discussion on Object Records vs. Image
Records
Secondary Images
We provide a non-supported link to secondary images because
it does not support the task scenarios.
Object Record We provide a non-functional screen for all
object records because it does not support the task scenarios.
Imaging Guidelines and Standards
Not relevant to task scenarios.
top
Discussion Topics/ Outstanding Issues
Object Records vs. Image Records
Does the DAM system manage images or objects with associated images or
all collection objects? The low-fi prototype forced users to drill down
to an object record in order to access images. The emphasis on the object
record presents an apparent conflict with the concept of image management.
For now we've retained the emphasis on objects because of the relation
of many images to one object.
Shopping Cart
The Image Request process is predicated on the shopping cart metaphor.
Users must add images to their "cart" in order to request access to image
files. This step may disrupt the fluency of using images that users see
on the screen, but the project sponsors are intent on tracking digital
image use through a gatekeeper role in the near term.
top
Tools
| Tool |
Benefits |
Problems/ Limits
|
| Dreamweaver |
Allowed for rapid development of hardcoded
pages, easy object/form manipulation, library "objects"
reduced development time. |
HTML Weirdness
Inconsistent formatting when viewed in browser.
|
| Paper & Post-its |
Endless hours of entertainment. Enabled quick iterative
design.
|
|
| White Board |
Enabled quick iterative design.
|
Poor access to white boards
in South Hall |
|
Blackboard & Digital Camera
|
Enabled quick iterative design.
|
|
|
Artsconnected.com
Lunaimaging.com
Thinker.org
|
Reinforcement of design ideas.Access to images
and basic metadata for hard coding content.
|
|
top
5.3 Screen Shots
top
5.4 Description of Interface
- This
interactive prototype is non-dynamic.
- Optimally
displayed in Explorer
- All
pages are hard coded to support specific user tasks included in the
task scenarios.
- Follow
the task scenarios in the given order.
- Enter
recommended data in appropriate data fields.
- Follow
links.
- Be
prepared that some features are not currently supported.
Please
review Vocabulary
for assistance
with technical vocabulary.
top
|