History:Next Generation Schema/Release Editor

Problematic Cases

• 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)

• 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 discussion we had with dmppanda/Jugdish/brianfreud on Track Merging)?

• Adding/removing a track.
  • Should it create a new tracklist?
  • Should it modify the tracklist, which will most likely change many other releases?

• 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?

Use Cases

Note: The cases that are struck out means that they have been addressed in the UI design, but may not actually be fully implemented yet.

Track Level

• Fixing a typo in a track title/artist
• Changing one tracklist entry to a different track/recording
• Reordering tracks
• Adding a track
• Removing a track

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

Cleaning up the work for review

• OliverCharles will write new templates for the release editor.
  • Initially a static page with the structure for the release editor
  • Brian will be given the task of gradually integrating his work one step at a time, as specified by Oliver
  • After some functionality is integrated, the code will be subject to a brief review and then accepted
  • Rinse and repeat until we have a release editor that meets the requirements of the September beta milestone