Mike Taghizadeh's Blog

Great investigation!  Thanks!

This article implies support for stemming but it does not seem to be enabled by default. Stemming =...

Ah, didn't realise it was switched off by default.  I've just chatted about this in more detail over at my blog, but if you are looking to switch it on, here's my quick and dirty method:

- Go to the search page, enter any old query to return the search results page

- Under Site Actions, select 'Edit page'

- Locate the 'Search Core Results' web part (usually in the bottom zone)

- From the Edit button, select 'Modify shared web part'

- In the task pane that appears on the right hand side, under 'Results Query Options', check the box labeled 'Enable Search Term Stemming'

Hey presto, stemming is switched on.  Be warned, it will increase your index size and potentially impact search performance

Recommended Reading for January (click here for previous recommendations): · MOSS Search Word Stemming:

Is there a way to turn on stemming just for People search?

Wildcard Search (e.g. "Share*") doesn't work on my MOSS Box. Even if I enable stemming.

Is there anything else that I need to configure?

The only thing that I found in the SDK regarding wild card search involves building a custom web part. Is there no way to simply flip a switch to allow for wild cards in search?

Va recomand sa citi cu caldura aceste articole.... · MOSS Search Word Stemming: Part 1 and Part 2 – written

I think because the performance would suffer... but I also think this is needed out of the box.

I agree with the responder just above me - WHERE can we find the steps to create the custom SQL query.  Wildcards do not work 'out of the box' in MOSS 2007.  Get over it.  Help us create a custom SQL part for it then!

Mike Taghizadeh covering MOSS 2007 Search Capabilities

I followed your instructions (thanks!!!!), checked the checkbox for enable stemming in the search core results webpart.  Next I did a full crawl.  After the crawl, when I searched for "egger" I got a hit, but "egg" still got me nuthin.  Went back and checked that the box was still checked, which it was.  Am I missing something?

Ok, if a search engine cannot support wildcard search OOTB as MS says, when its a total failure. I mean why do i have to write a custom web part for a very basic requirement, I  can write a custom web part for custom client needs for example, but not for something that should be out of the box. All what I am saying to my clients, after installing sharepoint, is that to not rely on its search engine. Prove us the contrary and provide wildcard search out of the box!!!!

I cannot get this to work as well. I am using an English MOSS environment where the "Enable Search Term Stemming" checkbox is unchecked in the search results page.

I have done the following:

Uploaded a text file with the term "new york" to a MOSS site;

replaced the tsneu.xml in C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications\<GUID>\Config with the following contents

<XML ID="Microsoft Search Thesaurus">

<thesaurus xmlns="x-schema:tsSchema.xml">

 <diacritics_sensitive>0</diacritics_sensitive>

 <expansion>

  _detroit

  _{new york}

 </expansion>

</thesaurus>

</XML>

Restarted Office SharePoint Server Search and performed a full crawl afterwards.

Searched for "detroit" expecting to retrieve the "new york" file.

But I did not get the expected results. Dit I miss something.

I hope you can help me.

Best regards,

Andries

I have turned on the Word Stemming and it works find if you go to the Search Subsite but what if you use the Search Box on the Home Page. This displays the results in the OSSSearchResults.aspx page in the _layouts folder and does not seem to return the same results. i.e it will not implement Word Stemming. Is there a way to make this work the same as the Search Subsite?

In response to the question by Keutmann. Yes stemming is supported on the danish language. I have it running in a solution.

This is absurd!  I too am flabbergasted that such a BASIC search feature is not included by default!  I am not going to sit here and write a custom web part for a feature that is included in *every* search engine in the world.

If Windows Desktop Search can do this, why the *hell* can't MOSS 2007?  We are in the pilot stage for MOSS 2007 and if I have to code this by hand, then trust me, we will not be buying such a POS.