|
I disagree with redirecting because (unlike before) the custom search page always shows the form and I don't think people should be shown the custom search fields unless they actually want to do custom/advanced searches. I also really like how the current predefined searches have useful page titles (e.g. "Edits for Some Artist") and links in the title back to the entity in question. The custom searches have nothing like that, it just says "Search for Edits" in the title. I do completely agree that it should be a lot easier to switch from the predefined searches to custom searches though. It's really annoying how there's no way to switch to a custom search at all. Agree with nikki here re: redirect. Also agree that it is indeed super-annoying that there's no easy way to filter an editor/artist/release's edits for those of a particular type (for example) so we need some sort of solution My edits also asked for common URL base for all searches. Something like "Advanced Search", yeah - maybe "Customise this search" perhaps. Subscribed entities actually can't be done with edit search – you'd need '(artist is in my subscriptions OR label is in my subscriptions) AND status is open' and you can only choose conceptual AND or OR – no mixing. Subscribed editors can't either, because we don't have a subscribed editors filter. http://codereview.musicbrainz.org/r/2083/ Woaw ! Thanks very much I'm really eager to see this live ! About the redirect, nikki and voice, maybe you see a problem with client-side redirect indeed it's clumsy but wouldn't it be ultra-awesome to have a server-side redirect ?! Either server-side redirect or HTTP 302 (like chatlogs' today
Putting in 09-03 fix version based on the assumption comments on codereview will get responded to. Moving to the next release as we're in freeze now. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Good suggestion, I plan to actually make all these little searches use the same edit search system, so this is certainly something I plan to add in