Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gallery
A set of image collections group into a resource collection. Initially, there will only be one of these either hard-named to "Galleries" or identified by the user.

Use Cases

These use cases were suggested by Daphne Ogle of UCB.

Instructors

  1. Create collection (deferred)
  2. Organize images within a collection (deferred)
  3. Organize collections (within the gallery) by subject, class session , ?????(deferred)
  4. Assign students a collection for review (for an exam for instance) (deferred)
  5. Assign students an image for review (deferred)
  6. Assign students a certain group of images (may come from a variety of collections) for review (all images of Frank Lloyd Wright's early work from the semester for instance) (deferred)
  7. See what students see

Students

  1. Browse collections in the course
  2. Find a collection and review it
  3. Find a particular image and see details for reviewFind
  4. Manually sequence through images in a collection and review itBrowse collections in the course
  5. Play (auto-sequence) through the images in a collection
  6. Study for an upcoming exam (review course images)
  7. Find image(s) for an assignment

Once we have a solid design to support the primary goal, we can start thinking about how we might be able to tweak things to support the secondary goal if time, resources, etc. allow.

To be clear, I'm not assuming that users will be able to complete each activity (use case) above in the system (and likely they won't). To understand the user's experience though I like to think through how the set of activities that help meet the goal will be affected by the system. So, for instance, for "assign students an image for review"... it's not likely we'll support the "assignment" of the image but understanding the complete activity will help me understand the experience without thinking about the gallery tool as a silo. It will also help me get real with trade-offs. Already this list reminds me how much we will be depending on the resources tool and the ability for users to create their collections in meaningful ways via the Resources tool.

...

  1. (deferred)

Not all of the use cases will be implmented in the initial version of the Gallery Tool. Editing, in particular, is deferred to later work.

Viewing and Sequencing

The Gallery tool provides five six main functions at this time:

  1. Navigate to an image-collection.
  2. View and edit metadata associated with an image-collection. (deferred)
  3. View the image-collection as an array of thumbnails.
  4. View an image full sized, perhaps in a pop-up window.
  5. View the image-collection sequentially (manual), perhaps in a pop-up window.
  6. View the image-collecton by playing it (auotmatic).

When an image is displayed full size, it should include it's name and description text (if any). It may be possible, when a single image is select for display, to jump into the sequence for that image. That would allow the user to then move back and forth in the sequence and see near by images (etc).

...

The application is considered to have two main states:

  1. NavigationGallery View (and navigation)
  2. Image View (and sequencing)

...