I sometimes see worse-than-expected results from tag lookup searches initiated by Picard’s “Lookup in Browser” action. (I think that this is an MBS and/or search issue, not a Picard issue.)
When I tried to look up local files tagged with the artist name “Jake Kaufman” and the release name “Mighty Switch Force OST” today, https://musicbrainz.org/taglookup/index?tag-lookup.artist=Jake+Kaufman&tag-lookup.release=Mighty+Switch+Force+OST was loaded (I’ve removed some empty parameters that don’t appear to affect the results).
I was hoping to see Mighty Switch Force! Official Soundtrack near the top of the list, or at least one of the other releases from the same release group, but instead I get what seems like all of the artist’s releases in an arbitrary order (the release that I want is on the final page).
If I change the URL to use “Mighty Switch Force” as the tag-lookup.release parameter, I see the expected results at the top of the list. It seems like the presence of a search term that isn’t in the release name (“OST”, in this case) makes the server give up on ordering the results. Is this expected?
I tried adding a “Mighty Switch Force OST” search hint alias to the release I was looking for, but it doesn’t appear to affect the results. Are search hints expected to be used in this case?