New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support search operators #5572
Comments
Commented by: ywwg It would be nice if we could also search ratings. Maybe interpret "***" as "three stars"? Or "rating: 5" to be consistent with the description above. Furthermore, since typing while DJing isn't pretty, I'd like short versions of the terms also. "g:" could also be interpreted as "genre:" as a shortcut. Oh and BPM ranges too: "b:120-125". |
Commented by: bloodybeet-deactivatedaccount All said functionality has been implemented in my branch. If you check out my branch, check out the user manual under "temporary fts doc" for the FTS to see the resulting functionality. I think it would be good to include the FTS functionality as "experimental" to some public release, so users can check it out and test in the long term. I'm expecting a lot of comments on how the syntax can be refined etc. |
Commented by: rryan As a stopgap before Bart's Full-Text-Search branch is finished I hacked up a dead-simple query parser tonight. It's currently in trunk.
For text filtering, you can do queries like:
Note it doesn't matter if you have a space between the colon and the argument or not. For numeric filtering you can do either either exact number or range filtering:
Note that you can put a space between the colon but currently there must be no space between the operator and the number. I left fuzzy-matching (e.g. "~bpm" to specify tracks with similar BPMs to currently playing tracks and "~key" to specify harmonically compatible tracks) as stub methods in the SearchQueryParser class. If anybody wants to tackle those it should be pretty easy to get started. |
Commented by: rryan I forgot to mention, of course you can combine these operators. List all Danger tracks that are rated 4 or 5.
There's no way to do an OR right now. That's another thing that isn't too hard but I don't have time to tackle right now. |
Commented by: esbrandt Thanks for implementing this RJ - a great addition to all users. We should emphasize that in the 1.11 release changelog . Can you briefly outline what Bart's Full-Text-Search branch is missing in order to qualify it for inclusion in the trunk? |
Issue closed with status Fix Released. |
Reported by: rryan
Date: 2010-10-15T20:39:41Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp661454
The library search feature could include some nicer search features such as :
title: FOO artist: BAR genre: BAZ
We could even support some operators within the sections like:
year: >=2005
year: =2005
Since this would be an "advanced" feature, the mini-language could have some degree of complexity, though the basic Google-like ones above should be easy for anyone to get.
The text was updated successfully, but these errors were encountered: