[Edit]Submitted a ticket http://tickets.musicbrainz.org/browse/PICARD-827 [/Edit]
I think my request requires two parts, one a new webservice to be created and two a (change/choice) to the way Picard scans a cluster.
I don’t know about other people but if you scan a cluster to use the audio fingerprinting information your one album can get smeared across a number of different albums, sometimes nearly as many as there are tracks.
I think it would work better if it did this, scan a cluster and get all the possible recording mbid’s from Acoustid for each track, not just the first one. Do one batch submission to a new MusicBrainz web service that contains all the possible mbid’s for all songs in the cluster then using a query like the one below MB would return the most likely release mbid by number of tracks contained.
I have downloaded the MusicBrainz database and found this method is not only quick and accurate but also reduces the number of web-service calls dramatically.
If anyone can tell me where to make an official Feature Request then I will send it there too, however googling mainly sent me to the defunct forums.metabrainz.org which returns a 502 at the moment.
SELECT TOP 5 rl.gid, rl.NAME, Count(rc.gid) AS [COUNT] FROM recording rc JOIN track t ON rc.id = t.recording JOIN medium m ON m.id = t.medium JOIN release rl ON rl.id = m.release WHERE rc.gid IN ( GUID, GUID, GUID, GUID, GUID, GUID, etc . . . ) GROUP BY rl.gid, rl.NAME ORDER BY 3 DESC