Corey Roth [MVP]

Does this work with people search? :)

Top News Stories Cisco Takes Aim At Microsoft's Stronghold (bMighty) Small and midsize businesses

you are doing really gr8 job. keep it up.

will this web-part work with Faceted Search 2.5?

Thanks,

Nilang

Unfortunately I have not identified a good way to handle people search (www.dotnetmafia.com/.../wildcard-search-with-moss-people-search.aspx).

Thanks for the comments.  It doesn't work with Faceted Search out of the box unfortunately.  From my understanding it reads the user's query from the querystring.  It could be possible to write an interface to connect the web parts, but would require development in both projects.  This is definitely something I would like to see done though.

Corey

Thank you for great web part, I have a question: when this web part is added to results.aspx page "Did you mean...” stop working. Is it because keywords are set to null?

Yes, I believe that is the reason why.  I think the Search Summary web part only works with keyword queries.  

Pingback from  Links (9/18/2008) « Steve Pietrek - Everything SharePoint

Hi,

I have installed MOSS Wildcard Search Web part onto my sharepoint server.

I have added, deployed the solution through Central Adminstration... and also activated the same thru Site Collection Features option in the site settings.

The wildcard search is working fine.

BUT I AM FACING A PROBLEM after installing the Wildcard Search Core Results web part, BEST BETS are not working.

Please do help me in this regard.

Thanks,

Owens Jesse

That is correct.  Best bets do not work with wildcard search (since they are keyword based).  More info here.  www.dotnetmafia.com/.../what-you-give-up-with-full-text-sql-queries-using-wildcard-search.aspx

Hi there, I have installed, deployed and activated the wildcard search in my MOSS and no different results are generated on wildcard searches, it seems like it doesn't work since my faceted search still works fine, could anyone advise on this. This is how I installed it:

1) Stsadm -o addsolution ...... as in the readme (I had to run it from folder PACKAGE)

2) Deployed from MOSS admin - Solution Management

3) Activated from Site Collection Features

4) Added Webpart to Search Center

....... run queries with asterix without having any hit generated due to the asterix.

Thanks

Make sure you modified the results.aspx page (as opposed to the default aspx page) in your search center.  Also be sure that you have removed the existing CoreResultsWebPart from your results page.

If you want to properly do a wildcard search in something more advanced such as people search, faceated or federated search you may need to move to something more robust like Ontolica Wildcard.  This is not free, but it does get around those issues as well as the RSS and Best Bets problem.  Corey has developed a good wildcard search if you only need basic google-like search functions.  

like it

Great job man! It's been invaluable for me for use with scoped lists. I drop it just above the scoped list and it works great. Thanks!

Excellent, glad it works for you.

Hello Corey.

A problem with web part. It doesn't work setting properties in weba part task pane. For example I i set the scope or change xml nothinh happens. Is it by design?

Thanks

Alberto

Hi, for the advance search, how's the property mean? the document property? My company hope to have a "tagging" solution. I wanted to make use of the property "Description" but i can't get it to work. please reply.

@Doreen I'm afraid I'm not understanding what you're trying to do.  Can you provide more information?

I had previously encountered an issue sorting the search results returned by your web part (by clicking on the column headers); there was some XSL that needed to be put in the Parameters Editor. However, I didn't save that XSL, and when I had to recreate the part, I now can't find it... I thought I'd found it on one of these forums, but no dice.

Any idea what I'm talking about? Thanks.

@jwer I am familiar with what you are talking about but don't have the XSL handy.  The one issue with XSL sorting is that it doesn't work when you go between pages in the resultset.

Found it, thanks. This is what it looks like:

<ParameterBinding Name="dvt_sortfield" Location="Postback;Connection" />

<ParameterBinding Name="dvt_sortdir" Location="Postback;Connection" />

I'm disappointed in the result-page-only sort, too, but we decided it was not a big enough deal to worry about.