User:Kuno/Recording Suggestions

From MusicBrainz Wiki
< User:Kuno
Revision as of 11:29, 12 April 2011 by Kuno (talk | contribs) (New page: There are several different scenarios the Recordings tab has to deal with. In this document I try to describe what the tab should be doing in each situation. = Tracklist level = When ad...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

There are several different scenarios the Recordings tab has to deal with. In this document I try to describe what the tab should be doing in each situation.

Tracklist level

When adding a release or medium the supplied tracklist is compared against existing tracklist.

Scenario Action Confirmation Implement
The supplied tracklist is identical (or identical with only case changes) to a tracklist in the database. Recording suggestions are taken from the existing tracklist, no other suggestions are offered. not required NGS
The supplied tracklist is similar (case/punctuation changes, possibly other small changes calculated with some distance algorithm) to a tracklist in the database. Recording suggestions are taken from the existing tracklist, no other suggestions are offered, confirmation is required for the tracklist as a whole. required Post-NGS
The supplied tracklist is identical to the first X tracks of some other tracklist. Presumably the existing tracklist has bonus tracks, false positives would be likely with a limited number of tracks so this match should not be attempted for short tracklists. Recording suggestions are taken from the existing tracklist, no other suggestions are offered. required Post-NGS
The first X tracks of the supplied tracklist are identical to some other tracklist. Presumably the new tracklist has bonus tracks, false positives would be likely with a limited number of tracks so this match should not be attempted for short tracklists. Recording suggestions are taken from the existing tracklist, no other suggestions are offered, confirmation is required for the tracklist as a whole. required Post-NGS

Any confirmation prompts should be a single prompt for the entire tracklist.

Track level

NOTE: the following should all be implemented in NGS. Most of this should have been fixed as part of MBS-1515.

New track has exactly one identical recording

Description: When adding a track the new track title + artist preview combination has one exact recording title + artist preview match in the database.

Action: Suggest the recording, no other suggestions are offered, confirmation is not required for this track.

New track has exactly one similar recording

Description: When adding a track the new track title + artist preview combination has exactly one similar recording title + artist preview match (case and puncturation changes allowed).

Action: Suggest the recording, no other suggestions are offered, confirmation is required.

New track has several identical recordings

Description: When adding a track the new track.

New track has several similar recordings

Edited track would cause recording to be orphaned

Edited track is now identical to associated recording

Edited track is still similar to associated recording

Edited track differs significantly from associated recording