SOLVED

Remove need for wildcards in searches

%3CLINGO-SUB%20id%3D%22lingo-sub-240166%22%20slang%3D%22en-US%22%3ERemove%20need%20for%20wildcards%20in%20searches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240166%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EYou%20still%20have%20to%20use%20wildcards%20like%20*%20to%20get%20correct%20search%20results.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EIf%20I%20search%20for%20the%20word%20%E2%80%9Corange%E2%80%9D%20I%20don%E2%80%99t%20get%20results%20that%20would%20be%20found%20with%20%E2%80%9Coranges%E2%80%9D.%20You%20have%20to%20use%20%E2%80%9Corange*%E2%80%9D%20to%20find%20those%20files.For%20end-users%20this%20is%20not%20intuitive.%20End-users%20don%E2%80%99t%20like%20wildcards%20or%20don%E2%80%99t%20even%20know%20they%20exist.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-240166%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251163%22%20slang%3D%22en-US%22%3ERE%3A%20Remove%20need%20for%20wildcards%20in%20searches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251163%22%20slang%3D%22en-US%22%3EIn%20one%20interface%20I%20use%20regularly%2C%20search%20defaults%20to%20a%20case%20insensitive%20%22contains%22%20search%2C%20so%20you%20don't%20have%20to%20worry%20about%20case%20or%20if%20there%20is%20a%20space%2C%20dash%20or%20lower%20case%20s%20before%20your%20main%20keyword.%20A%20quick%20click%20throws%20open%20an%20%22Advanced%22%20search%20where%20you%20can%20use%20wild%20cards%2C%20case%20sensitivity%2C%20etc.%20It%20is%20literally%20the%20only%20thing%20I%20like%20about%20that%20particular%20SaaS.%20I%20hope%20SharePoint%20can%20get%20there%20some%20day.%20It%20never%20has%20been%20good%20at%20a%20contains%20search%3B%20always%20preferring%20a%20starts%20with%20approach.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240175%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20need%20for%20wildcards%20in%20searches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240175%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20also%20great%20feedback%2C%20Denis.%26nbsp%3B%20We%20have%20some%20users%20who%20like%20the%20ability%20to%20use%20wildcard%20operators%20like%20that%20in%20search%2C%20but%20in%20your%20case%20we%20hear%20your%20feedback%20that%20you%20should%20not%20need%20to%20use%20these.%26nbsp%3B%20We%20will%20take%20that%20back%20and%20the%20team%20will%20have%20more%20to%20share%20about%20search%20plans%20and%20capabilities%20coming%20at%20Ignite.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

You still have to use wildcards like * to get correct search results.
If I search for the word “orange” I don’t get results that would be found with “oranges”. You have to use “orange*” to find those files.
For end-users this is not intuitive. End-users don’t like wildcards or don’t even know they exist.

2 Replies
Highlighted
Solution

That's also great feedback, Denis.  We have some users who like the ability to use wildcard operators like that in search, but in your case we hear your feedback that you should not need to use these.  We will take that back and the team will have more to share about search plans and capabilities coming at Ignite.

Highlighted
In one interface I use regularly, search defaults to a case insensitive "contains" search, so you don't have to worry about case or if there is a space, dash or lower case s before your main keyword. A quick click throws open an "Advanced" search where you can use wild cards, case sensitivity, etc. It is literally the only thing I like about that particular SaaS. I hope SharePoint can get there some day. It never has been good at a contains search; always preferring a starts with approach.