SharePoint Wildcard Quaerere: “Pro” Non est caule “Vestibulum”

In foro MSDN quaerere, Sic frequenter interrogare:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ quaero, non inveniet eam."

Ut non sentiant eam, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Si fodiat meaning in quaero partes, youll 'reperio a checkbox, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() Huiusmodi functio.

Haec sunt quosdam caulibus:

  • "fish" is a stem to "fishing"
  • "major" is a stem to "majoring"

Isti caules non:

  • "maj" is not a stem to "major"
  • "pro" is not a stem to "programmer"

The WSS/MOSS search engine does support wild card search through the API. Here is one blog article that describes how to do that: http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/03/06/how-to-use-the-moss-enterprise-search-fulltextsqlquery-class.aspx

A productum parte 3rd, Ontolica, provides wild card search. I have not used that product.

</finem>

Scribet ad mea blog.

Technorati Tags:

3 cogitationes on "SharePoint Wildcard Quaerere: “Pro” Non est caule “Vestibulum”

  1. Josh Noble

    Ontolica est meaning pars probatur quod subiungit wildcard capabilites per omnia quaerere sharepoint searches. De exitibus cum erroribus ego venit trans in comprehendo solutiones alias conatur uti prepending *, Optimum sponsionibus, Quatenus Keyword, Populus Quaerere, RSS, Quaerere foederatae et Faceted Quaerere. Non est libera, sed non nimis restringere users basic usus wildcard. Sentire liberum ad email me pro magis notitia.

    jno@surfray.com

Leave a Reply to Josh Noble Cancel reply

Tua inscriptio electronica non editis. Velit sunt insignis *