If the tagger buttons are telling Picard to add a non-album track, then isn't this an MBS issue?

Thanks for letting me know, I'm not aware of the technical side of Musicbrainz/Picard.

This happened to me too. I clicked lookup for one of the unmatched files, clicked the tagger button next to the release name in the search results and it got loaded as a standalone track which really wasn't what I was expecting.

Yeah, see my post on http://forums.musicbrainz.org/viewtopic.php?id=3078 - although I haven't really followed up yet, unfortunately.

Users are finding this part very confusing. The solution indeed has to be on MBS, IMO - but not really sure how the taglookup page (for a recording/track) should be differentiating the recording tagger link from the release tagger link.

Actually, now I think about it; this is indeed a bug as it's different behaviour to pre-NGS doing a track/recording taglookup. The link should always go to a release "openalbum" link; unless the recording is a standalone recording. If a user actually wants to force-pull it into Picard as a standalone recording; they can always go to the recording's page to do this.

Apologies for not picking this up when I tested the "fixed" taglookup from MBS-1520 and MBS-3545

Submitted for review (but without any testing as my env is still broken :/ ) at http://codereview.musicbrainz.org/r/1605/

Assigning to Ollie for merging to test; as I probably should have done before.

Merge to test done