Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Legend (relevant for prototype iteration 1 only, note that reporting interfaces were identical in both designs for this iteration):

(U) - This point specifically references the user-friendly design

(E) - This point specifically references the high-efficiency design

...

The drag and drop interface was intuitive and easy (learnability,efficiency). Confused about how to pull up album details once the albums are uploading, lacks visual affordance for clicking on the uploading albums (learnability).
The now modified delete upload button was extremely obvious and easy to find (learnability).
Confused about where different fields go in the album information panel (e.g. she thought the "Unknown" was producer name and not album name, and she thought "Date Unknown" was today's date instead of album release date) and require more visual affordances for what each field denotes (learnability).
Consistently looking for a help button on the interface ("Is there help available for that?") (learnability).
Intuitive and easy for this user (learnability).
Advanced Tables - Table Plus
width100%
columnAttributesstyle="width:60px50px;",style=width:200px;"

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #1

  • User found the drag and drop interface to be intuitive and easily learnable, but isn't familiar with the fact that file start importing as soon as the mouse button is released. Instead, user searched for an "OK" button to start importing officially. This is a tradeoff we made to achieve more efficiency, but sacrifices some safety because the user may inadvertently drop the wrong file on the interface.
  • Learnability
    User recognized the play button beside the track right away
    Efficiency (learnability)
  • User's single click on the play button starts playing the track right away 
    Safety away (efficiency)
  • If user clicked on play accidentally, a pause button appears in place of the play button to stop track (safety)
  • (U) Learnability On the user-friendly interface, the user had some trouble locating the trash can because it was placed far away from the user's line of visionvision (learnability)
  • (E) On the high-efficiency interface, User quickly found the "X" delete button beside the uploading album
  • Efficiency:
    • High-efficiency interface requires very little mouse movement to reach the "X" button, whereas the user has to move the cursor all the way across the screen in the user-friendly version of the interface.
  • Safety:
    • User prefers that the user-friendly interface gave a confirmation warning before deleting album
  • Learnability
    • User found the both interfaces to be easy to understand in terms of what information is being displayed
    • Both interfaces lack affordances in terms of what is editable and what isn't, user had to experiment by single clicking on the fields
  • Efficiency
    • User liked how both interfaces showed all the album and track information on one screen
    • User noted the directly editable fields are very convenient 
    • (E) User liked the comments text box in the album approval screen for adding notes for DJ (e.g. "This is the first album by this artist")
  • Safety
    • User noted a mistake in adding the genre can be easily fixed by clicking the "x" beside the genre tag
  • Learnability
    • User was confused about how to "approve" the album on both interfaces because he did not associate approval with the "checkmark" button
  • Efficiency
    • Again, a tradeoff was made between efficiency and safety: single click on the "checkmark" button will approve the album immediately
  • Safety
    • User prefers a confirmation message
  • album (safety)
  • Both interfaces lack affordances in terms of what is editable and what isn't, user had to experiment by single clicking on the fields (learnability)
  • User noted the directly editable fields are very convenient (efficiency)
  • User noted a mistake in adding the genre can be easily fixed by clicking the "x" beside the genre tag (safety)
  • User was confused about how to "approve" the album on both interfaces because he did not associate approval with the "checkmark" button (learnability)
  • Again, a tradeoff was made between efficiency and safety: single click on the "checkmark" button will approve the album immediately (efficiency)
  • User prefers a confirmation message (safety)

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #2

Music Director #2

  • Learnability
    • Drag and drop was very straightforward, no problem
  • Efficiency User really likes being able to type in the URL instead of downloading then dropping the file
  • Safety
    • No issues with safety
  • file (efficiency)
  • Learnability (U) Had a hard time finding how to open the album information, tried to click on "Recently Uploaded" tab** Found the play button rather fast, but double clicked instead of single click, figured out it pauses it by double clicking
  • No trouble with efficiency or safety
  • tab (learnability)
  • For a long time, user had trouble finding the trash can (learnability)
  • Tried clicking on the trash can
  • Learnability
    • For a long time, user had trouble finding the trash can
    • Eventually discovers the delete function when she hovers over the icon and the text changes to "delete"
  • Safety Tried clicking on it but surprised to find it deletes without asking her to confirmLearnability confirm (safety)
  • User figured out how to edit fields rather fast, but not sure how to "save" the entry (tried clicking inside the textbox when she really just wanted to exit the textbox - (safety issue)
  • Tried clicking on "checkmark" icon, which could cause further problems as that will approve the entire album and make the edit screen disappear altogetherEfficiency Prefers when all the information is in front of her and not hidden behind some buttons (need to be activatedaltogether (safety)
  • User used the comments section before approving, found it to be a really good ideaNo other issues

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #3

Learnability

  • Did not understand the "drag and drop" instructions (learnability)
  • User had trouble uploading the files due to lack of clarity in instructions and also did not understand the “Today’s Upload” tab, tried clicking on other tabstabs (learnability)
  • User struggled with learnability insomuch that efficiency and safety were not concerns
  • User found the play button very quickly and had no other issuesissues (learnability)
  • (E) User liked having all the information in one place (play button, album information etc.) for all albumsLearnability
  • (U) User saw the trashcan and assumed that it works the same way as the Windows Recycle Bin
    • Tried to look for a way to drag the album into the trashcan
    • Looked for a delete button by hovering over the currently importing album on the left pane
    • Eventually the user hovered over the trashcan and saw the delete but did not click on it and tried to drag albums over to it
    • Tried clicking on everything in the end to delete the album (e.g. tried to click on "don't approve" button, which did nothing but close the album view)
    • User notes usually the trash can is for dropping files on it, you don’t open the trash can ever
  • Efficiency
    • User can drop multiple files into a trash can, is there a way to quickly delete multiple albums?
  • Safety
    • User likes a place where you can open the trash can to look at deleted albums
  • No problem with interpreting the track detail view and editing the fields
  • User looked for a save button to confirm edits to the field (safety)
  • Date pop up is unnecessary, people usually only care about the year of release, not exact date
  • User likes the add genre feature to allow for sub-genres and easy deletion of wrongly labeled genres (safety)
  • No issues with approval

"Elf"

  • Learnability
    • User tried to unzip all files first then drag and drop the content directly onto the KaJaM interface
    • Our interface did not make it explicit that users are to drop zip files directly
  • Efficiency
    • User noted that he will want to drop multiple files at a time
  • Safety
    • User also noted that there doesn't seem to be a way to cancel a file dropped accidentally
  • Learnability
    • User was confused that the right side of the screen was completely blank, and instead clicked on "recently uploaded" tab to look for the tracks within currently uploading album
    • The tabs are not labelled clearly to communicate what it is really for
  • Efficiency
    • Quickly found the play button to preview each track
  • Learnability
    • Found the trash icon quickly due to its red color
    • Trying to kill the progress bar (to stop it from uploading)
    • User wants a feature that allows for stopping the import but not delete it (pause it for now)
    • Want to drag and drop the tracks onto the trash can to delete instead of clicking
  • Efficiency
    • Had trouble deleting all 3 separate tracks quickly, just deleting one at a time
    • Repetitively delete everything is a concern: no expedient way to delete everything
  • Safety
    • Don't need confirmation message, especially if it acts like a recycle bin like on Windows
  • Learnability:
    • Quickly decided to double click on the song track name, then figured out the single click is better
    • User suggested offering more affordances for single click because he is a "double-click" guy (learnability and efficiency)
    • He got that "Unknown" is the album name rather quickly
    • Don’t know what unknown date is (import date or release date?). Also English styled date is not good
  • Efficiency
    • What if there are different artists in each album (compilations are very frequent), want the ability to change the artist name for each track versus for the album (efficiency versus customizability)
    • Various artists for the entire album, but separate artist name for each song
    • User wants to potentially change the genre for each track
    • User does not value visual album art as much and prefer to have everything displayed as he considers himself to be a database guy
  • Safety
    • No issues with safety
  • No issues with learnability, efficiency or safety but want to see what he has approved during the current session (want to see what other people have uploaded recently)

Prototype Iteration 2

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Student User #1

Student User #2

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Student User #3

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Learnability:
Efficiency:
Safety:

Back to the top

Reporting Tasks

...

Prototype Iteration 1

User

Switch to Reporting Mode

Filter View by Genre

Sort View by Play Count

Export Reporting Data to Excel File

Music Director #1

  • User found switching modes via the tabbed interface to be easy and intuitive (learnability)
  • Single click on another tab switched the mode immediately (efficiency), and user noted he can easily switch back if he accidentally clicked on another tab (safety)
  • Learnability
    • User struggled with understanding the "filter" button and what it means - he thought it brings up another "filter" window&nbsp
  • Efficiency
    • User did not like how selecting a genre from the drop down menu did not filter the genres right away
    • Not efficient to require 2 user clicks every time a genre needs to be filtered
  • Safety
    • Requires user to confirm genre choice by explicitly clicking on "Filter", but user did not like this
  • Learnability
    • User did not know how to sort the rows (no affordances offered to suggest that clicking on the header row sorts it)
    • User noted that having an arrow displayed beside the header would really help to indicate the sort function
  • Efficiency:
    • Single click on the head column sorts the table in descending order, second click sorts the table in ascending order. User thought this was convenient
  • Safety:
    • User did not know how to "clear" the sort, but eventually just noted that he could just click on another head row to sort by another row instead
  • User found the export button very quickly and no troubles with this task (learnability)
  • User liked that the file started downloading right away without prompting him to confirm (efficiency versus safety)

Music Director #2

  • No issues with switching to reporting mode
  • User did not struggle with the filtering steps at all
  • Interface is a bit too busy and overwhelming (learnability and safety, but may help efficiency)
  • User noted that the reporting data does not filter by date range (e.g. everything in the last 6 months)
  • User finished sorting rather quickly as she knows to click on the header row from knowledge in the head
  • No issues with exporting to excel file

Music Director #3

  • No issues finding the reporting mode
  • User had no trouble with filtering the genre
  • Struggled in understanding what date range the reporting data covered (learnability and safety)
  • User had trouble sorting by play count, did not realize that the header row can allow sorting (learnability)
    Eventually tried to export to Excel for further manipulation
  • No issues with exporting

"Elf"

  • No problem finding the "Reporting" tab
  • Made a comment implying the filter button was redundant ("You have to click filter now?")
  • No issues with filtering but user wants to report multiple genres (e.g. not jazz or world, but only want electronica and rock)
  • No issues with sort because the user is knowledgeable with Excel
  • However, user does not see what the play counts are for? Is this one week or two weeks?
    • Want to filter play count in each column by date
  • No issues with export, user thought the button was very clear

...

Prototype Iteration 2

...

User

...

Switch to Reporting Mode

...

Filter View by Genre

...

Sort View by Play Count

...

Export Reporting Data to Excel File

...

Student User #1

  • Bin (learnability)
  • User can drop multiple files into a trash can, is there a way to quickly delete multiple albums? (efficiency)
  • User likes a place where you can open the trash can to look at deleted albums (safety)
  • User looked for a save button to confirm edits to the field (safety)
  • User likes the add genre feature to allow for sub-genres and easy deletion of wrongly labeled genres (safety)
  • No issues with approval

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

"Elf"

  • Our interface did not make it explicit that users are to drop zip files directly (learnability)
  • User noted that he will want to drop multiple files at a time (efficiency)
  • User tried to unzip all files first then drag and drop the content directly onto the KaJaM interface (efficiency)
  • User also noted that there doesn't seem to be a way to cancel a file dropped accidentally (safety)
  • User was confused that the right side of the screen was completely blank, and instead clicked on "recently uploaded" tab to look for the tracks within currently uploading album (learnability)
  • Quickly found the play button to preview each track User tried to unzip all files first then drag and drop the content directly onto the KaJaM interface (efficiency)
  • User wants a feature that allows for stopping the import but not delete it 
  • Had trouble deleting all 3 separate tracks quickly, just deleting one at a time (efficiency)
  • Don't need confirmation message, especially if it acts like a recycle bin like on Windows (safety)
  • User suggested offering more affordances for single click because he is a "double-click" guy (learnability and efficiency)
  • What if there are different artists in each album (compilations are very frequent), want the ability to change the artist name for each track versus for the album (efficiency versus customizability)
  • Various artists for the entire album, but separate artist name for each song
  • No issues with learnability, efficiency or safety but want to see what he has approved during the current session (want to see what other people have uploaded recently)

Prototype Iteration 2

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Student User #1


The drag and drop interface was intuitive and easy (learnability,efficiency).


Confused about how to pull up album details once the albums are uploading, lacks visual affordance for clicking on the uploading albums (learnability).


The now modified delete upload button was extremely obvious and easy to find (learnability).


Confused about where different fields go in the album information panel (e.g. she thought the "Unknown" was producer name and not album name, and she thought "Date Unknown" was today's date instead of album release date) and require more visual affordances for what each field denotes (learnability).

Consistently looking for a help button on the interface ("Is there help available for that?") (learnability).


Intuitive and easy for this user (learnability).

Student User #2


Readily dragged and dropped files to the interface (learnability,efficiency), but dragged the second file to the smaller space (once the right-pane came in). User remarked that it was not clear whether he was to drag and drop the zip files or the contents, or whether both zip files could be dragged together.


User may not have known how to get into track details to view the song tracks. User remarked about the lack of affordances on the upload rows. (learnability)


User had no issues deleting the file, but paused the upload before deleting the upload. User remarked that it wasn't obvious that the .zip file corresponded to an album. (learnability,safety) User inquired about whether it was possible to delete on a per-track level, although it wasn't a task. (efficiency)


User remarked that they didn’t know if one of the items was the band or album name (but knew that “Unknown” was the other name), but acknowledged the affordance of the highlight (learnability). The user also remarked about the intuitive nature of the date picker. (learnability)


CRITICAL INCIDENT: User was slightly confused about upload vs. approve and wasn’t sure if leaving would approve (learnability,safety), user also remarked that it may not be the case that users want the approved album to disappear. (efficiency)

Student User #3


No significant issues.


Double-clicked on the row and paused a moment to search for the play icons.


No significant issues.


No significant issues.


No significant issues.

Back to the top

Reporting Tasks

Anchor
observations_reporting
observations_reporting

Prototype Iteration 1

User

Switch to Reporting Mode

Filter View by Genre

Sort View by Play Count

Export Reporting Data to Excel File

Music Director #1

  • User found switching modes via the tabbed interface to be easy and intuitive (learnability)
  • Single click on another tab switched the mode immediately (efficiency), and user noted he can easily switch back if he accidentally clicked on another tab (safety)
  • User struggled with understanding the "filter" button and what it means - he thought it brings up another "filter" window (learnability)
  • Dislikes how 2 user clicks are required every time a genre needs to be filtered (efficiency)
  • Requires user to confirm genre choice by explicitly clicking on "Filter", but user did not like this (safety)
  • User did not know how to sort the rows (no affordances offered to suggest that clicking on the header row sorts it) (learnability)
  • User noted that having an arrow displayed beside the header would really help to indicate the sort function (learnability)
  • Single click on the head column sorts the table in descending order, second click sorts the table in ascending order. User thought this was convenient (learnability)
  • User found the export button very quickly and no troubles with this task (learnability)
  • User liked that the file started downloading right away without prompting him to confirm (efficiency versus safety)

Music Director #2

  • No issues with switching to reporting mode
  • Interface is a bit too busy and overwhelming (learnability and safety, but may help efficiency)
  • User noted that the reporting data does not filter by date range (e.g. everything in the last 6 months)
  • User finished sorting rather quickly as she knows to click on the header row from knowledge in the head
  • No issues with exporting to excel file

Music Director #3

  • No issues finding the reporting mode
  • Struggled in understanding what date range the reporting data covered (learnability and safety)
  • User had trouble sorting by play count, did not realize that the header row can allow sorting (learnability)
  • Eventually tried to export to Excel for further manipulation
  • No issues with exporting

"Elf"

  • No problem finding the "Reporting" tab
  • Made a comment implying the filter button was redundant ("You have to click filter now?") (efficiency)
  • No issues with filtering but user wants to report multiple genres (e.g. not jazz or world, but only want electronica and rock)
  • No issues with sort because the user is knowledgeable with Excel
  • However, user does not see what the play counts are for? Is this one week or two weeks? (learnability)
    • Want to filter play count in each column by date
  • No issues with export, user thought the button was very clear

Prototype Iteration 2

User

Switch to Reporting Mode

Filter View by Genre

Sort View by Play Count

Export Reporting Data to Excel File

Student User #1


Easily found the reporting tab (learnability).


Removing the piazza-like tag for blue dot was immediately intuitive (learnability, efficiency), at which point adding the electronica genre was also easy.


Immediately decided to click on the correct column header, as she noticed the arrow cue and affordance in the column header (learnability).


The button for exporting to excel was obvious (learnability).

Student User #2


No significant issues.


Readily identified the "x" button to switch the genres. User remarked on the salience of the genre selectors. (learnability)


No significant issues.


No significant issues.

Student User #3


No significant issues.


No significant issues.


No significant issues.


No significant issues.

Back to the top

Prototype Iterations

Anchor
iterations
iterations

Design

First Iteration

Second Iteration

Importing

The efficient design featured a text box and button, while the "friendly" design featured neither.

A text box added to the "friendly" design to provide affordances for pasting or typing URLs

Managing Imports

The efficient design had a more visible "stop" button, next to the progress bar, while the "friendly" design placed its "delete" button far from the user's focus

The "friendly" design added a 'pause upload' button near the progress bar and changed the "No (do not approve)" button to a visible, red "Delete Upload" button

Organization

The efficient design used a button to switch between upload and reporting modes and featured recent uploads on the same "upload" page, while the "friendly" design separated current from recent uploads, and used tabs for navigation

The "friendly" design reworded its tabs to be more clear as to their purpose

Navigation

The efficient design assumed that scroll-bars would be used normally to scroll through recent uploads, while the "friendly" design used a button to scroll through the details while keeping the approve buttons static.

A scroll-bar replaced the "scroll-button" for scrolling through details in the "friendly" design.

Reporting

The interface featured a single-genre drop-down box which required clicking on a "filter" button to filter. The release dates included and date ranges of playback counting were unclear.

Genre was converted to a Piazza-like tagging design much like that of the "friendly" design and removed the requirement to click on a "filter" button; release date ranges were made explicit and columns were added to clarify over which date ranges counts were collected

Miscellaneous Features

N/A

Added a hover-based mechanism to view per-track artists for compilation albums; tooltips were added to clarify what each text field represented in the editor pane

...

Student User #2

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

...

Student User #3

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

...

Learnability:
Efficiency:
Safety:

Back to the top

Prototype Iterations

...

Design

First Iteration

Second Iteration

 

 

 

 

 

 

 

 

 

Back to the top