We have an interesting case where we perform 2 different attribute searches looking for CAD objects but the wildcard search shows less results than the non-wildcard search!
For example if we search by our ECN attribute:
ECN Attribute Search | Number results | Type of results |
0046945 | 2 | asm and dwg |
*46945 | 1 | asm only |
*46945* | 2 | asm and dwg |
46945* | 0 | none, as expected |
Notes about the above tests:
Things I tried:
My questions
Thanks, Lawrence
Solved! Go to Solution.
I initially liked the idea of the checkboxes, however, after further thought, I think they may overcomplicate it, especially if you do more complicated searches (wildcards in the middle, multiple items, etc).
It seems better to me if WC handles spaces the same with or without asterisks/stars and then ideally give some visual indication on the results page what was happening. I can understand the rationale that if there is a space before or after the text it will find it, even if a star is not used, however, if a star is used on one side I think that it should absolutely find the item if the space is on the opposite side. So for example:
Attribute Search Criteria | Should show results for: |
0046945 |
"0046945" “0046945 ” " 0046945" |
*0046945 |
|
0046945* |
|
*46945 |
|
*46945* |
|
0046945 |
Note: No spaces were entered in any of the above search criteria. I would have shown with quotes to show exact text but didn't want anyone to interpret as actual search quotes! 😕
Sorry to weigh in late here; I had to temporarily let a lot of forum stuff go amidst other duties...
Implied wildcard searching should be
1) Simple and Consistent. If it is implying wildcards then it should be the same for both front and back of your search string.
2) Controllable using a checkbox to use implied wildcards or not (on the search page). This also would provide a visual so the user knows if extra wildcards are being used (without having to drown themselves in convoluted and contradictory documentation). Default action should be controllable via Preferences.
3) Consistent wildcard behavior. Implied wildcards (e.g. only for spaces) working differently than stated wildcards is very confusing. This is compounded by the search results not actually containing a space even when one is there (because it removed it in the search results database but not the actual database!).
4) Comprehensive but simple documentation. Search documentation should be complete, however, if it takes many pages to explain how a search works then the documentation is probably trying to compensate for a lack of functionality. Searching should be very intuitive unless it is using more advanced search functionality such as Regular expressions.
Even more annoying however is that even when you use wildcards correctly you may still not find what you are working for as shown by the following examples in the documentation (which we have butted up against):