Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Overview of Design

Composite Design 3 This is a web application designed with safety in mind design that focuses on safety while striving for reasonable efficiency. Such a design should assist more error-prone users who might be less computer-savvy while still remaining efficient enough for high-volume music directors to get their job done without much fuss.  Unlike other designs, this design has been designed without a focus on playback, instead focusing on the editing and uploading portions of the task, since these are common tasks for both music directors and elves.  The

  • Motivation: This design focuses on the most critical task of the three identified in GR1 (importing music). The CMJ lists, which are used less often (submitted on the order of once a week) are not a major focus of the design, but may be accessed through a tab interface at the top.
  • Design Idea: This design keeps editing separate from uploading by fusing a master-detail design like those used on iPad applications with the pane-based design of Windows 8 applications for the purpose of selecting editable components in a modal interface ("Metro"-style)
  • Scope: Since importing and reporting are the most important tasks of a music director, these tasks have been emphasized for the purposes of this interface.
  • *Pro: *By emphasizing safety, more error-prone users who might be less computer-savvy will be able to be sure that they will not import data with incorrect data. The compromise in using a master-detail design should add efficiency for high-volume music directors to get their job done without much fuss.
  • Con: Aspects of the interface (including the questions asked and modal nature of most of the detail view) may be less efficient than would be ideal for high-volume music directors.

An overview of the entire interface is shown here, details regarding each component will be explained in the storyboard below.

A detailed example of the main KaJaM! interface

The KaJaM! interface when editing an album

...

Sketch

Explanation

Lana sits down to upload some releases

She opens up her e-mail to view some digital downloads



She opens up the KaJaM! interface

And drags and drops the link from her e-mail to the interface

It automatically starts to download

She continues to drag and drop links for upload...

And will be prompted if the file is password protected

When she's done uploading, she looks over what's been loaded for each album

Interested the an album, she plays a track from it

If it's got correct data, she clicks "YES" (It's okay)

And the album is loaded and saved and disappears from the list

When she finds the error on Starmarker's album, she clicks "NO" (It's not okay)

And is given options to change the release

Image Removed Image Added

She selects "Track Names" and

Image Added

And is given a list of the names to edit

She edits the names and clicks "Done"

And is returned to the "What's Wrong?" screen, where she clicks "Nothing," as everything is now correct

Since everything has been corrected, she clicks "YES" when asked again whether the album is now okay

Running out of time to do more work, she leaves the remaining albums to be handled by Adam (he will see them when he logs in)

Hurrying to submit her CMJ lists, she opens the CMJ submission for in another window

And switches to the charts tab in KaJaM!

She clicks the RPM genre tab and uses the top plays listed there to populate CMJ

Her job done, she logs off, content in the knowledge that more digital media has been catalogued than ever before

...