Difference between revisions of "Track Merging"

From MusicBrainz Wiki
((Imported from MoinMoin))
(TODO (Imported from MoinMoin))
Line 10: Line 10:
 
* When release tracks will have their own titles, and somebody completely changes the title, should it automatically create a new track?  
 
* When release tracks will have their own titles, and somebody completely changes the title, should it automatically create a new track?  
 
* Should the "release editor" have an option to re-use existing tracks, instead of always creating new ones and then merging them?  
 
* Should the "release editor" have an option to re-use existing tracks, instead of always creating new ones and then merging them?  
 +
 +
==TODO==
 +
 +
* "Release track" titles.
 +
* Disambiguation comments for tracks.
 +
* Warnings on merge if:
 +
** Track durations differ
 +
** Merging tracks from Album/Single/EP/... and Live releases together.
  
 
----
 
----

Revision as of 05:55, 17 March 2008

TrackMerging

TrackMerging is a simplified version of TrackGrouping. The basic idea is to allow a single "track" object to be shared by multiple "release" objects. A "track" object contains a collection of "release track" objects. This would clear up a significant amount of redundant data and allow us to pool similar PUIDs into a single object such that there would be absolutely no PUID collisions between the objects. Implementing this concept will be one of the many incremental steps toward the NextGenerationSchema goal.

Unresolved Issues

  • Are EditTrackTimeEdits and EditTrackNameEdits linked to no releases or all attached releases, now that there can be more than one release?
  • How should removing of a track work? Automatic removing when the last "release track" is removed? Only manual removing?
  • How do you separate merged tracks?
  • When release tracks will have their own titles, and somebody completely changes the title, should it automatically create a new track?
  • Should the "release editor" have an option to re-use existing tracks, instead of always creating new ones and then merging them?

TODO

  • "Release track" titles.
  • Disambiguation comments for tracks.
  • Warnings on merge if:
    • Track durations differ
    • Merging tracks from Album/Single/EP/... and Live releases together.


(OLD) Below is a collection of all the various ideas/notes we've had regarding this feature:

Here are some notes from an IRC conversation we had some time ago (LukasLalinsky, Jugdish and BrianFreud). But I can't remember some details, and somehow find it on chatlogs, so it's possible that something is incorrect. (If somebody can find the IRC log, please add the link here.) -- 147.251.51.78 16:04, 02 October 2007 (UTC)

  • Adding new album will always add new master entities.
  • Masters have no explicit titles, everything is derived from attached tracks.
  • It will be possible to merge masters.
  • It will be possible to split some tracks of a master.
  • The release editor can be used only to edit tracks, not masters or track<->master associations.
  •  ? Significant change to track title will automatically detach the track from the current master (if more than one track is attached to it)
  • There are no track ARs, adding an AR to track will transparently add it to the master.
  • PUIDs are attached to masters. (theoretically, no two masters should share the same PUID)
  •  ? Durations are attached to masters, not tracks.