Search function too broad
Thread Starter
Registered User
Joined: Jul 2005
Posts: 1,494
Likes: 0
From: Colorado
Search function too broad
For most on this forum, it is annoying to find new (or veteran) users post "reposts."
Often, however, I've come to find that while the search function is very useful, it is also sometimes too broad and irrelevant. Granted, using the appropriate search key words is essential to good results, it is frustrating when I sift through pages on a thread, sifting through all the BS, all the irrelevant info, then finally seeing some words highlighted in red that are completely out of context with what I was searching for.
In short, I have two questions (one directed to the moderators):
1) Is there a way to make the search function more relevant to the search query?
2) Does anyone else find it frustrating, or am I misguided?
FlameSuit on
Often, however, I've come to find that while the search function is very useful, it is also sometimes too broad and irrelevant. Granted, using the appropriate search key words is essential to good results, it is frustrating when I sift through pages on a thread, sifting through all the BS, all the irrelevant info, then finally seeing some words highlighted in red that are completely out of context with what I was searching for.
In short, I have two questions (one directed to the moderators):
1) Is there a way to make the search function more relevant to the search query?
2) Does anyone else find it frustrating, or am I misguided?
FlameSuit on
Trending Topics
Originally Posted by davidv
I would like to see a posts with photos only option.
Even though I can often search for something after someone says, "Don't flame I searched!", and find many valid results, I do believe the search function leaves something TBD. For example,
I think some search engines you can say SEARCH: "injen" and "exhaust" and "clip" if you are looking for a soundclip of the Injen SES Exhaust. It will bring up only results with ALL THREE words searched. However, I don't believe the "and" / "or" functions work on this search engine. So, basically you can search "Injen" , "SES", "Exhaust", etc., get a million results, and sift through 3 pages until you find the clip.
It is somewhat helpful limiting your search to "Search in Titles Only", as opposed to entire threads. That cuts out some of the BS, but not enough.
EDIT: I search "Injen" and "Clip" in titles only mode and I came up with 5 pages of results. Many exhaust soundclip threads, but I still need to page 5 pages of results to find the one related to injen (if it even exists).
Clean this search function up and we wouldn't have so many newbs claiming, "I searched and did not find."
I think some search engines you can say SEARCH: "injen" and "exhaust" and "clip" if you are looking for a soundclip of the Injen SES Exhaust. It will bring up only results with ALL THREE words searched. However, I don't believe the "and" / "or" functions work on this search engine. So, basically you can search "Injen" , "SES", "Exhaust", etc., get a million results, and sift through 3 pages until you find the clip.
It is somewhat helpful limiting your search to "Search in Titles Only", as opposed to entire threads. That cuts out some of the BS, but not enough.
EDIT: I search "Injen" and "Clip" in titles only mode and I came up with 5 pages of results. Many exhaust soundclip threads, but I still need to page 5 pages of results to find the one related to injen (if it even exists).
Clean this search function up and we wouldn't have so many newbs claiming, "I searched and did not find."
Last edited by Silkk; Aug 14, 2006 at 07:46 AM.
Lost in Transit
Joined: Oct 2004
Posts: 10,003,830
Likes: 0
From: Houston, TX
I do believe you have access to both boolean and natural language searching as premier members do.
This has been covered a lot, the server can NOT handle everyone doing boolean searches all day long. To do this I would have to split the DB to two machines and replicate changes off to the slave server. Then configure the search to do searches off the replication server only. This is a major change that is not overnight and very straightforward.
We will get there but you are talking a large chunk of cash just in the hardware itself.
This has been covered a lot, the server can NOT handle everyone doing boolean searches all day long. To do this I would have to split the DB to two machines and replicate changes off to the slave server. Then configure the search to do searches off the replication server only. This is a major change that is not overnight and very straightforward.
We will get there but you are talking a large chunk of cash just in the hardware itself.
Originally Posted by Silkk
Even though I can often search for something after someone says, "Don't flame I searched!", and find many valid results, I do believe the search function leaves something TBD. For example,
I think some search engines you can say SEARCH: "injen" and "exhaust" and "clip" if you are looking for a soundclip of the Injen SES Exhaust. It will bring up only results with ALL THREE words searched. However, I don't believe the "and" / "or" functions work on this search engine. So, basically you can search "Injen" , "SES", "Exhaust", etc., get a million results, and sift through 3 pages until you find the clip.
It is somewhat helpful limiting your search to "Search in Titles Only", as opposed to entire threads. That cuts out some of the BS, but not enough.
EDIT: I search "Injen" and "Clip" in titles only mode and I came up with 5 pages of results. Many exhaust soundclip threads, but I still need to page 5 pages of results to find the one related to injen (if it even exists).
Clean this search function up and we wouldn't have so many newbs claiming, "I searched and did not find."
I think some search engines you can say SEARCH: "injen" and "exhaust" and "clip" if you are looking for a soundclip of the Injen SES Exhaust. It will bring up only results with ALL THREE words searched. However, I don't believe the "and" / "or" functions work on this search engine. So, basically you can search "Injen" , "SES", "Exhaust", etc., get a million results, and sift through 3 pages until you find the clip.
It is somewhat helpful limiting your search to "Search in Titles Only", as opposed to entire threads. That cuts out some of the BS, but not enough.
EDIT: I search "Injen" and "Clip" in titles only mode and I came up with 5 pages of results. Many exhaust soundclip threads, but I still need to page 5 pages of results to find the one related to injen (if it even exists).
Clean this search function up and we wouldn't have so many newbs claiming, "I searched and did not find."
So wait, is there any way to ensure that a search brings back ONLY threads with ALL the words you specified?
Like I searched for "greddy emanage ultimate parameters" and like 99% of the threads didn't have "parameters" anywhere.
Like I searched for "greddy emanage ultimate parameters" and like 99% of the threads didn't have "parameters" anywhere.
Lost in Transit
Joined: Oct 2004
Posts: 10,003,830
Likes: 0
From: Houston, TX
https://my350z.com/forum/search.php
Change your search type to boolean, this is only available to premium members due to the strain on server at this time.
http://library.albany.edu/internet/boolean.html
Change your search type to boolean, this is only available to premium members due to the strain on server at this time.
http://library.albany.edu/internet/boolean.html
Originally Posted by silvrhand
I do believe you have access to both boolean and natural language searching as premier members do.
This has been covered a lot, the server can NOT handle everyone doing boolean searches all day long. To do this I would have to split the DB to two machines and replicate changes off to the slave server. Then configure the search to do searches off the replication server only. This is a major change that is not overnight and very straightforward.
We will get there but you are talking a large chunk of cash just in the hardware itself.
This has been covered a lot, the server can NOT handle everyone doing boolean searches all day long. To do this I would have to split the DB to two machines and replicate changes off to the slave server. Then configure the search to do searches off the replication server only. This is a major change that is not overnight and very straightforward.
We will get there but you are talking a large chunk of cash just in the hardware itself.
Thread
Thread Starter
Forum
Replies
Last Post
Lt_Ballzacki
Brakes & Suspension
39
Aug 6, 2021 06:19 AM
Colombo
Forced Induction
35
Nov 9, 2020 10:27 AM