Edit Track Number Edit: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(s/TRM/PUID/ (Imported from MoinMoin))
(No difference)

Revision as of 18:39, 5 December 2008

Edit Track Number (sequence)

This edit changes the sequence number of a track in a release notes.gif.

How to do it

  • The Edit link to the right of a track title on a release page (or other pages where release details are displayed) takes you to a page where you can edit the track's title (EditTrackNameEdit) or number (EditTrackNumberEdit).
  • The Edit all link below the release's name on a release page (or other pages where release details are displayed) takes you to a page where you can edit the release's title (EditReleaseNameEdit) and/or attributes (EditReleaseAttributesEdit), as well as the title (EditTrackNameEdit) and number (EditTrackNumberEdit) of any or all tracks on the release.

Guidelines

Editing

  • Rather than making wholesale changes to the track order on a release to match the version you have, consider the possibility that there are different versions of the release with different track orders. If you can find an entry in FreeDB with the order you want, it is easier to simply import that FreeDB release than to change the track numbers on an existing release (and the new release is available immediately, without waiting for votes).
  • When changing the track order, the times for the tracks will move as well. If the track times don't match the titles, changing the track order is the wrong solution, and you should either use EditTrackNameEdit (only if there are no PUIDs or they are incorrectly tagged) or re-import the release as suggested above.

Voting

  • Manually added tracks (those with track times of  ?:?? ) are more likely to have been added in the wrong order or with the wrong track number, so the standard of proof for changing these is lower than for tracks imported from FreeDB (with actual track times).
  • When voting on track number changes, look for links to a discography entry with the proposed order.
  • Vote not just on one, but on all track number changes for a release; this helps prevent DuplicateTrackNumbers (listed in this SuggestionReport).
  • If the moderator making the track number changes is the one who added the release originally (use View release mods link to see this), it's more likely that they actually have the release and/or know what they're doing and aren't just messing up a correct release that somebody else has.

Notes

Q: Are PUIDs associated with the track title or track number on a release? How are PUIDs automatically moved if the track listing of a release changes? For example, if I rename a track on a release, I assume the PUID stays associated with it. But if I want to change the order of the tracks on an release, do the PUIDs move?

A: PUIDs are associated with a track (using the track id) so when the title of the track or the number of the track changes, the association stays. Therefore if you use the EditTrackNumberEdit PUIDs are moved with the track.



NonAlbumTracks do not have numbers, so their Edit pages do not have an option for changing the track number.

Releases with valid DiscIDs cannot have their tracks renumbered; this is because the tracks in the DiscID cannot be changed. If you determine that the TOC of the DiscID does not match the release as listed, you should [http:#reimport re-import or add] the release and move the DiscID to the new release using a MoveDiscIDEdit. After doing that, it might be reasonable to renumber the tracks and then enter a MergeReleasesEdit.

Prerequisites

An EditTrackNumberEdit will fail due to a FailedPrerequisite if another EditTrackNumberEdit changes the track number.

Dependencies

An EditTrackNumberEdit will fail due to a FailedDependency if the release containing the track is deleted by RemoveReleaseEdit or RemoveReleasesEdit or merged into another release by a MergeReleasesEdit. It will also fail due to a FailedDependency if the track is deleted by a RemoveTrackEdit.

Symbolic name and id

MOD_EDIT_TRACKNUMBER (5)


Authors: @alex