History:Next Generation Schema/Release Editor: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Fix typo.)
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Problematic Cases ==
= Use Cases for Testing =


Earlier in the UX phase of the release editor user interface we defined three users, each with their own use case:
* Editing a track title/artist.
** Should it modify the linked recording?
** Should it automatically break the link to the recording, if it's changed? (e.g. editor trying to change a track on a tracklist)
** Should it just change the track, keep the link to recording and the recording itself untouched? (we will probably get incorrectly linked recordings)


=== Joe (simple) ===
* Do we want to allow changing the link between a track and a recording in the release editor? If so, how? JS lookups like for artist credits? Or do we want to only allow creating new recordings (this was the result of a [[Track Merging|discussion we had with dmppanda/Jugdish/brianfreud on Track Merging]])?


A brand new user that is entering his first single artist release. Joe is new to MB and hasn't read a whole lot of guidelines - he would like to get in, get it done, and go away. Given that he wants to enter the minimum amount of data and not focus on adding lots of details. Joe has copied the track listing from Amazon.com and wants to get moving.
* Adding/removing a track.
** Should it create a new tracklist?
** Should it modify the tracklist, which will most likely change many other releases?


=== Sally (various artists & guess case) ===
* Not directly related to the release editor, but the above issue affects this. CD TOCs are currently linked to tracklists. That means creating new tracklists automatically is not possible. Should CD TOCs be on medium, rather than tracklist?


A user who is entering a various artist release and wants to be lazy about capitalization. She's ok with spending a little more time making things right and adding a release date and a label. However, sally doesn't like copying text from another site. She would prefer to enter the data into separate fields.
== Use Cases ==


=== Track Level ===
=== Maggie (DJ mixed release) ===
* Fixing a typo in a track title/artist
* Changing one tracklist "position" to a different track/recording
* Reordering tracks
* Adding a track
* Removing a track


A user who is entering a DJ mix set and she's found the track listing at discogs. She's not afraid to dig for more data and ensure that all the data she can find is properly covered.
=== Medium Level ===
* Editing medium title/format
* Reordering mediums
* Adding a new medium with a new tracklist
* Adding a new medium with an existing tracklist
* Removing a medium

=== Release Level ===
* Editing release name/status/barcode/etc.
* Editing release artist credit (should affect all tracks for SA releases?)
* Adding/removing/changing release labels -- label, catalog number pairs

Latest revision as of 16:21, 4 November 2011

Use Cases for Testing

Earlier in the UX phase of the release editor user interface we defined three users, each with their own use case:

Joe (simple)

A brand new user that is entering his first single artist release. Joe is new to MB and hasn't read a whole lot of guidelines - he would like to get in, get it done, and go away. Given that he wants to enter the minimum amount of data and not focus on adding lots of details. Joe has copied the track listing from Amazon.com and wants to get moving.

Sally (various artists & guess case)

A user who is entering a various artist release and wants to be lazy about capitalization. She's ok with spending a little more time making things right and adding a release date and a label. However, sally doesn't like copying text from another site. She would prefer to enter the data into separate fields.

Maggie (DJ mixed release)

A user who is entering a DJ mix set and she's found the track listing at discogs. She's not afraid to dig for more data and ensure that all the data she can find is properly covered.