This page has not been reviewed by our documentation team (more info).

This EditType deletes a release licon from the database.

How to do it

Guidelines

Editing

  • Merge duplicate releases:

  • Cancel accidental edits:

    • If you entered an AddReleaseEdit but realize that it was a mistake (perhaps you clicked Submit twice), the quickest fix is to cancel your pending edit (see HowToCancelEdits).

  • Don't remove NonAlbumTracks:

    • Although it is possible to use the RemoveReleaseEdit to remove the special "release" [non-album tracks] it is better to use RemoveTrackEdit to remove NonAlbumTracks individually, since it allows other editors to "split" their vote if they agree with some removals but not others. This also prevents mistakenly removing another non-album tracks being added after the RemoveReleaseEdit has been submitted. If the non-album tracks you want to remove are the ones you mistakenly added, it may be better to cancel the pending edit. Since the [non-album tracks] SpecialCaseRelease of the artist will be automatically removed when the last NonAlbumTrack is removed, it is not necessary to apply a RemoveReleaseEdit to remove it.

Voting

  • Only vote "yes" for RemoveReleaseEdits if they are accompanied by an EditNote justifying the deletion; otherwise, useful data may be lost.

  • If it looks like the release is valid and there are DiscIDs or PUIDs, suggest that the editor should instead MergeDuplicateReleases.

  • There are a few exceptions to the general rule that removing releases is rarely correct. One of them (which should be in the StyleGuidelines, but probably isn't yet) is for "releases" that have only data tracks. MusicBrainz is a database about Music, and while releases for a MusicDVD or a GameSoundTrack should be kept, it's OK to remove releases that consist only of DataTracks (even if they have music files in them).

Notes

This edit is always put to a vote, even if made by an AutoEditor.

Dependencies

A RemoveReleaseEdit will fail due to a FailedDependency if it is merged into another release by MergeReleasesEdit. [Can someone confirm this? --ZeroGravitas]

  • I haven't tested this, but I believe it to be true. As I understand it, a MergeReleasesEdit effectively deletes the unique identifier for the "bad" album. Any open edits for it (be they ARs or others) will therefore fail on their expiry date. Various items (PUIDs, Release events etc) are transferred to the merge target, but open edits are not. The RemoveReleaseEdit will not be applied to the "good" album that was the target of the merge, if that is what you are worried about. --ArtySmokes

Symbolic name and id

MOD_REMOVE_ALBUM (12)


CategoryEditTypes Authors: ZeroGravitas

 
Creative Commons EFF GPL LGPL This material is Open Knowledge Valid XHTML 1.1 Valid CSS 2.0
Original Design|vacubomb.com Contact details Server version: RELEASE-20071014