Suggestion and Policy
Actually, we have addressed this issue in the past. Good idea, just need to implement it. One of the big problems is the performance of the search. TER gets between 100-300 search requests per second. Currently those searches are for numeric values in a 25000+ record provider table. To do this, we would have to do a SQL “like” query on a the review table (where the text is stored) which has over 200,000 reviews to search. This would be a huge performance issue for the site.
I am not sure if the performance problems this would cause would outweighs the benefit. Sorry for getting techie on you guys 
-- Staff
Actually, we have addressed this issue in the past. Good idea, just need to implement it. One of the big problems is the performance of the search. TER gets between 100-300 search requests per second. Currently those searches are for numeric values in a 25000+ record provider table. To do this, we would have to do a SQL “like” query on a the review table (where the text is stored) which has over 200,000 reviews to search. This would be a huge performance issue for the site.
I am not sure if the performance problems this would cause would outweighs the benefit. Sorry for getting techie on you guys
-- Staff