UsageScenarios

Erland Isaksson edited this page Dec 31, 2015 · 1 revision

Introduction

The purpose here is to describe how common usage scenarios are supposed to be performed from a user perspective.

Note! The scenarios described below are just samples, we haven't decided if this is how it is supposed to work yet.

Adding new music

Scenario 1: Adding new local music (no automatic import, online lookup)

  1. User adds some music files to the music folder using the file manager of their choice
  2. SBS performs an automatic scan and the new music shows up in the SMD user interface as new available music that can be added to the library
  3. In SMD user interface, the user selects the new music files and/or folder and selects to add it to the library * User is asked if musicbrainz id's and similar online identities should be found * If selected, the user is offered a list of matching search result and is asked to select the one that matches the added music.

Result after scenario:

  • Only selected new music has been added to SMD library and gets available in the SMD browse/search menus. Unselected music is not added to SMD library and are only available through the standard SBS menus.
  • Online id's for the new music is stored in SMD library

Scenario 2: Adding new local music (automatic import, online lookup)

  1. User adds some music files to the music folder using the file manager of their choice
  2. SBS performs an automatic scan and the new music is automatically added to the SMD library.
  3. In SMD user interface, the user is shown that new music has been added to the library but is missing online identifiers. User is asked if musicbrainz id's and similar online identities should be found.
  4. If selected, the user is offered a list of matching search result and is asked to select the one that matches the added music.

Result after scenario:

  • All new music has been added to SMD library and gets available in the SMD browse/search menus
  • Online id's for the new music is stored in SMD library

Updating music

Scenario 3: Updating local music (no automatic import)

  1. User updates some of the existing music files with some tagging software
  2. SBS performs an automatic scan and the updated tag values the SMD user interface indicates a list of files that have been updated. User selects to view changes through the SMD interface and can optionally select to overwrite SMD data with the new updated tag values.

Result after scenario:

  • Only selected music is updated also in SMD library and gets available in the SMD browse/search menus. Unselected music still keeps its old attribute values in SMD database.

Scenario 4: Updating local music (automatic import)

  1. User updates some of the existing music files with some tagging software
  2. SBS performs an automatic scan and the updated tag values are automatically overwriting the corresponding information in the SMD library.

Result after scenario:

  • All updated music is updated also in SMD library and gets available in the SMD browse/search menus

Listening to Music

Scenario 1: Exploring music by external influence (community sources)

Pre-requisite: User has access to one or more external sources that can present new music. Examples are Last.FM, Pandora or Amazon for 'top tracks', or social networks that can present recommendations from friends.

  1. User browses an external source. Trusting in the wisdom of crowds, user quickly gets suggestions for the most popular tracks for a number of new / unknown artists. 1. extension: user chooses a preferred and/or weighted mixture of external sources
  2. User plays selected tracks from available sources (online or local disc) and marks track, album or artist based on personal opinion. 1. variant: add tracks to static playlist 1. variant: add tracks, albums or artists to a dynamic playlist by setting metadata ("rank", "star", "like", etc) 1. variant: add previewed tracks (not currently available in user's library) to wishlist for later action (buy CD, buy online, find in not-yet-subscribed service). This is only relevant if user is exploring music thru a service that allows "previewing".

Result after scenario:

  1. User has a zero, one or many new tracks, albums or artists in playlist(s) or wishlist(s).
  2. Regular playlists (static or dynamic) are ready for use.
  3. Wishlists can be used to preview music if such a service is available, or as a manual "shopping list". Wishlists are not formatted for automatic purchase with any online music sources.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.