...
This interface is more or less self explanatory (large instructions to drag files to the interface or enter a URL, similar to attachment drag and drop for many e-mail applications). Once the import process has begun, the empty text boxes denote fields the user is required to fill in for the album. The user may not know that these must be filled in to add the album to the playback library. The efficiency feature of filling in details for the zip automatically propagating those details to tracks may go unnoticed until the user actually does it, which can be partially circumvented by forcing the user to enter album-level details before being able to edit the individual tracks (except for track nameother than individual track names, which should always be editable immediately).
Efficiency
This design's purpose is to maximize efficiency, and the asynchronous import process and propagation of album -level details further this objective. The system automatically picks up non-music files from the zip files, such as cover art or liner notes and attaches them to the album. The system state is always preserved, so a music director short on time can always leave import work to assistants or a later time. One area in which this design is not maximally efficient is if an e-mail contains multiple albums, multiple links must be pasted to the textbox for importinto KaJaM!, one at a time. Extracting multiple URLs from an e-mail automatically would be more efficient, but presents logistical/efficiency challenges (we need the raw HTML of the e-mail to get the links, which would require first saving the e-mail, or giving our system access to the user's inbox).
Safety
Songs and albums can accidentally be included in the drag and drop. However, these can be easily cancelled and removed from the import process. Because all fields are directly editable (textboxes), it makes accidental keyboard focus typos likely. Unnoticed, these typos may get put This can create accidental typos which end up in the library. An obvious mistake one can be corrected by someone accessing the playback system, but a more else (e.g. an assistant) at a later date, but an innocent looking typo may lead to problems. This is a result of the efficiency and safety tradeoff present in this designsurvive. In this case, safety is sacrificed for efficiency.