View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000566 | HTML & PERL | Feature Request - Interface | public | 2007-01-07 18:30 | 2007-01-21 22:54 |
Reporter | ncmaothvez | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | won't fix | ||
Summary | 0000566: Some ideas on how to modify Advanced Search page | ||||
Description | Let's say I want to find animes that have at least 100 votes and a vote-rating between 7.0 and 7.4. With the current Advanced Search system, this is not possible because: 1. The 250 reuslts limit prevents all results from being displayed. 2. The returned results are sorted alphabetically. It's true that some (43% on a search I just did) of the results meet the criteria but a vast majority fall outside my area of interest. Also, unless I'm totally mistaken, there are titles that will never (or at least very unlikely) be found with the advanced search since they're too far down in the alphabet (like 'Yokohama Kaidashi Kikou' for example). I guess what I'm trying to say is that when using any search tool, one should, assuming the appropriate search param are used, be guaranteed to find _all_ items (not necesarily in one huge batch on one page though) that match the criteria and not be cheated on some results due to performance issues. So, while keeping the 250 limit I'd like to suggest the following changes (see attached picture): 1. Add an 'at most' parameter to Votes and Reviews. This way the user can be more specific and thus reducing the risk of reaching the 250 results limit and/or 'wasting' result positions on results outside the area of interest. In my example above, the other 57% that were 'wasted' on results outside my area of interest could have been replaced by additional valid results if I had been able to specify a rating upper limit of 7.4. 2. Add a 'Priority' parameter. Currently the search results are always sorted alphabetically. In my example above, the aplphabetical sorting doesn't seem logical since I'm more interested in rating rather than the first char in the title. I guess this could be replaced by a single parameter sort (like suggested by case 0000010 http://tracker.anidb.info/view.php?id=10) if multi-param ordering puts too much load on the server. | ||||
Tags | No tags attached. | ||||
related to | 0000010 | resolved | epoximator | Sort Advanced Search Result page |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-01-07 18:30 | ncmaothvez | New Issue | |
2007-01-07 18:30 | ncmaothvez | File Added: AdvSearch_mod.png | |
2007-01-19 15:07 | epoximator | Relationship added | related to 0000010 |
2007-01-19 15:20 | epoximator | Note Added: 0001142 | |
2007-01-21 22:54 | epoximator | Status | new => closed |
2007-01-21 22:54 | epoximator | Resolution | open => won't fix |