this article https://developers.coveo.com/display/public/SupportKB/What%27s+Happening+Behind+the+Scenes+When+You+Use+a+Wildcard explains the complication of wildcards and why often times the wildcard search will not find the expected results. The Coveo search experience could be improved to help regular users understand why their search with wildcards is not giving them the answers that they know exist, which are not found at all by the wildcard search. To begin with, when a wildcard search is done, the search should warn the user if it is known that all the matching results are not going to be in the results.This can be done by counting the matching items in the lexicon for the wildcard, and displaying that number with a warning and a call to action. Perhaps count up to 100 or 1000, or whatever has an acceptable performance impact and then display the information on the screen above the search results. EXAMPLE: We found over 1,000 matching items for abc* with over 987,xxx results. For performance reasons, we are unable to show you all these results. Please perform a more exact wildcard search or review the following list of sorted matches and select the ones you wish to include in your search. The user would then: 1. be made aware of the issue with the results of the wildcard search and 2. have two options to get better results, re-run a more exact search or review a well-sorted pop up of the matching items and pick and choose the ones of interest. This would make the wild card search much more intuitive and the end user would have a chance of finding the correct results with Coveo search.
|I need it...||Yesterday (let's go already)|