-
-
Notifications
You must be signed in to change notification settings - Fork 783
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
[Feature] Improved Search Functionality #1210
Comments
possible duplicate of #612 |
Sure, other porn sites might use OR for search but I'm not sure that those sites are anything to aspire to. I will use % in the meantime but I'm not sure this is ideal? It's not very intuitive, especially for new users. I apologize that I don't have a solution for this problem as I'm not well versed in how programming the search should actually work. Maybe AND by default would be a better option? From the other issue you mentioned, it does seem like this is an issue for users or at least not the expected functionality. Thanks. |
Bumping this issue. I run into this issue almost every time I use Stash, unfortunately. Today I searched "One More Time", hoping to find the scene with that exact name. Instead, I got 1,245 results. I understand this might be difficult to solve programmatically but it's pretty frustrating. I'm willing to put a bounty on this feature if necessary. |
If you wrap the search term into quotes, you will get an exact match. Actually, a single quote at the beginning already triggers this behavior |
Gotta say...I agree with OP. Putting my search query into quotes really is a workaround, and imo, bad UX.. Ex: A query of |
Can I piggyback on this issue for tag filters? Example: Suppose I want to see all cat videos that don't include dogs, I'd set two filters at once: Tags includes cats Right now that operation would be treated as an OR. I'd like it to be AND by default. TIA! |
@bnkai I’m not sure I fully agree here. I think a lot of sites, both NSFW and SFW, use a hybrid. Top results are AND as that is going to be the most accurate. Following that are the OR results as it’s less accurate (one of the conditions isn’t met, but it will hopefully get you close enough to find what you’re looking for). They results are presented as one list to the end user, and usually have the right result in the first few options. |
prepending a search with "+" seems to imply the following phrase must appear in the results pretty much everywhere, no? |
@GsMumbo you are not saying anything different. My main objection was the |
I agree that searching by query string should AND the terms by default. I'd propose a similar syntax to Google and Bing:
This will bring the search functionality more in line with conventions, while allowing access to the old behaviour. |
would also add "+" to require a thing in the search results, to do for example anabolic OR Diabolic +"initiations" |
$40 bounty added. |
$30 bounty added - $70 total bounty. |
$30 bounty added - $100 total bounty. |
Hello,
I think the current search functionality is unintuitive. For example, when I search "red head kitty", I expect to find the scene titled "red head kitty" as the first result. Instead, I am presented with every single scene I have that has the words "red", "head", or "kitty" in the title or description. As someone who has descriptions for almost every scene, this presents a large problem for searching. I know that I can enter that title in quotes and get the scene I want but there are other examples of this type of search causing an issue. For example, when I search "skye blue", I typically want just the scenes with Skye Blue, not all the scenes with the word "blue" somewhere in the title or description. I know that there are workarounds for these issues like searching by performer or even using regex but I am not proficient in regex. No other porn site has these same search issues. Apologies if this sounds a bit nitpicky but it greatly affects my regular use of Stash. I would be happy to provide more examples if needed. Thanks!
The text was updated successfully, but these errors were encountered: