Platform and Software Requirements:

- Tested on Chrome (latest version v26) in a MacOSX environment
- Should work on Firefox (although only with the latest version, v20). We welcome any feedback that helps in making our application browser-agnostic.
- Should work in Chrome on other OSes (Windows, Linux), but not fully tested.

Instructions for Testing Our Specific Scenario:

  1. Download the following zip files:
    Starmarker.zip
    KaJaM.zip
  2. Go to http://mv.ezproxy.com.ezproxyberklee.flo.org/dj3000/.
  3. Login with username "kajam", password "kajam".

Scenario Tasks

Scenario

Task

Imagine you are a music director, Lana, and you wish to upload some albums to the digital library via the KaJaM! interface

Open KaJaM! and log into the system

You have downloaded 2 albums onto your computer: Starmarker.zip and KaJaM.zip and wish to import them to the library

Import Starmarker.zip and KaJaM.zip into the digital library

Before approving the KaJaM! album, you want to listen to one of the tracks

Play a track in the KaJaM! album

The track from KaJaM! album sounds familiar, and you quickly realize you have already imported the album and don't need it again

Delete the entire KaJaM! album

The Starmarker.zip file finishes importing, and you wish to make sure all the track details are correct

Inspect track details*

You find incorrect and incomplete track details you want to fix

Edit track details to reflect the correct information**

You wish to approve the album to officially file it in the digital library

Approve the album

Before you leave, you wish to complete College Media Journal reporting for the month

Take a look at the reporting data in the digital library

You notice the reporting data is displaying all genres, but you want to look at only "Electronica"

Filter the reporting data to show only "Electronica"

Now all reporting data is on "Electronica" only, but it is not sorted by play count in the last month

Sort the reporting data by play count in the last month, in descending order

Everything looks good, but you still want to make adjustments to the reports based on physical CD play count before submitting them

Export the reporting data to Excel file format for further editing

Now that you are all done, you wish to go home

Done!

*The album contains tracks with pre-tagged information, but some are incorrect or incomplete:

Track #

Track Name

Artist

Album

Label

Release Date

Genre

1

While I'm Dead

Starmarker

Unknown

 

 

 

2

Sand Beauty

Starmarker

Unknown




3

Silvre Lining

Starmarker

Unknown




**The facilitator assumes Lana Googles the album information, so facilitator provides all the correct information to the user on a separate sheet of paper:

Track #

Track Name

Artist

Album

Label

Release Date

Genre

1

While I'm Dead

Starmarker

Killer Kilometer

Polyvinyl

2013-02-20

Electronica

2

Sand Beauty

Starmarker

Killer Kilometer

Polyvinyl

2013-02-20 

Electronica 

3

Silver Lining

Starmarker

Killer Kilometer

Polyvinyl

2013-02-20 

Electronica 

Implemented Parts of the Prototype

  1. Files are uploaded to the application, and stored to a backend database (sqlite)
  2. Changing album details or approving an album saves the album (along with all the music) onto the server.
  3. Album information listed on the "Reporting" tab are all retrieved from the server (sqlite database)
  4. Album play count information is also retrieved from the server

Shallow Parts of the Prototype

  1. The contents of the "All Uploads" tab is not a part of our scenario, or our design (it's more focused on managing uploaded music, rather than importing new music). As such, it has not been implemented at this time.
  2. Album play count information on the "Reporting" tab is retrieved from mock contents in a database table rather than live population from some source, since this information comes from the playback application at WMBR, which is separate from our application that focuses on importing only.

Miscellaneous (Troubleshooting)

- Most problems should be related to the wrong version of browswer (make sure Chrome is v26 and Firefox is v20)
- Other times your local browser settings may affect the aesthetics (font, color settings etc.)

Contributions

- Ian and Dominic collaboratively worked on the uploading interface (with Ian handling all of the backend + the uploading action; and Dominic handing all album editing + some UI components)
- Daniela worked on the reporting interface

  • No labels

1 Comment

  1. Sarah E Lehmann

    Usability: There are a lot of instructions that the user has to remember after clicking upload, especially if they need to rearrange tracks into different folders.
    Completeness: Sometimes, I get a stack trace when I click on the ""Reporting"" tab (there appears to be a type error with regards to a play date).
    Overall: Overall, very nice job!
    Thanks for all your hard work this term!