Navigate Up
Sign In
Supporters of Developer
Web

What's new within SharePoint 2013 Search - Part 3: Search Dictionaries, Query Builder, Query Client Type and more

Item is currently unrated. Press SHIFT+ENTER to rate this item.1 star selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+ESCAPE to leave rating submit mode.2 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.3 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.4 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.5 stars selected. Press SHIFT+ENTER to submit. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.

You may also be interested in: Sharegate No-Brainer Migration Tools

 

Editor's note: Contributor Nicki Borell is a SharePoint Evangelist & Consultant for Experts Inside. Follow him @NickiBorell.

New / Updates Ranking Model functions:

Custom ranking models are managed through PowerShell using XML files as it was in SharePoint 2010. Ranking Model for a specific query can be selected at query time by setting the RankingModelId of the query otherwise the default is used.

The PowerShell cmdlet is: New-SPEnterpriseSearchRankingModel

For more details about the underlying XML schema have a look here.

This example shows all Ranking Models in my demo system. You can see which is the default:

2012-08-29-2013Search-Part03-01.jpg

You can use the configured Ranking Models, for example, in the Query Builder (see details below in the Query Builder Section):

2012-08-29-2013Search-Part03-02.jpg

Query Spelling Correction:

This function is hosted in the Termstore. We can now easily configure “Exclusion” and “Inclusion” Terms. Another big benefit is that Terms configured in the “Inclusion” Termset can also be used for “Did you mean” functionality.

2012-08-29-2013Search-Part03-03.jpg

The example shown in the picture would result in searching for ”EI” which didn’t get any results so the system will suggest “Did you mean ExpertsInside

Query Rules:

Query Rules are new in SharePoint 2013. It is a feature that gives us the option to tailor results in a very flexible way. Query Rules are set on Site Collection Level.

A Query Rule has 3 main parts:

  • Query Conditions
    • The conditions defined when and in which context the rule became active:
  • 2012-08-29-2013Search-Part03-04.jpg

  • Query Action
    • In this section we can defined what happened if the rules matched. This is just a little bit similar to what we know as “Best Bets” or “Visual Best Bets” from SharePoint 2010, but much more powerful.
  • 2012-08-29-2013Search-Part03-05.jpg

  • Publishing Options
    • These settings control when the rule can fire

Query Client Types:

Query Client Types are also new in SharePoint 2013 Search. At this time there aren't many details are available on this new function. The idea behind the function is using the client the query is sent from to do specific throttling etc: “Applications are prioritized by tiers. Top tier has the highest priority. When resource limit is reached, query throttling becomes ON, and search system will process the queries from top tier to bottom tier.”

Query Builder:

Query Builder is a tool in SharePoint 2013 Search which we can find in different places. For example the Query Builder is available in the “Result Sources” section (Result Sources are in the next Part IV – Admin Stuff) and also in the “Query Rule” section etc. Query Builder is available when we have the option to manipulate search query or refine it. The Query Builder has 3 tabs:

  • Basic:
    • The Query is built here. You can use Keyword Query Language to add keyword filters and property filters. Keyword filters query the full-text search index.
  • 2012-08-29-2013Search-Part03-06.jpg

    This call for example will only show content where the “Author” is the logged on user.

  • Sorting:
    • Here we can manage how the results are sorted. We can use a Ranking Model ore use a Managed Property for that job
  • 2012-08-29-2013Search-Part03-07.jpg

  • Test:
    • Test tab in the Query Builder is to evaluate the query that you built. You can experiment there to see whether changing variables would have the effect that you want on the query.
  • 2012-08-29-2013Search-Part03-08.jpg

Stay tuned for the next parts in this series:

Part IV: Admin Stuff
Part V: Frontend Stuff

Categories: SPF 2013; Search; FAST Search; dev; MOSS; WSS; PowerShell

Comments

i:0e.t|liveid|00037ffe89cc6961@live.com

Ranking model in SharePoint 2013 is not the same as in SharePoint 2010

Hi,
 
Thanks for an interesting blog post. I just want to inform the readers that the schema you have linked to on top has nothing to du with the schema of Microsoft.Office.Server.Search.Administration.RankingModel and the RankingModelXML property.
 
You can investigate the schema using the following power shell code:
 
$rankingmodel = Get-SPEnterpriseSearchRankingModel -SearchApplication $ssa -Owner $owner -Identity <Guid of the model you want to inspect>
$rank.RankingModelXML > "c:\rankmodel.xml"
 

Nicki Borell

Ranking model in SharePoint 2013 is not the same as in SharePoint 2010

Hey, thanks for your input – ok, maybe you be right, it can be unclear. The link brings you to the msdn page the custom ranking model XML schema is described in common. Not how to analyze a specific ranking model in you environment

Posted 03-Sep-2012 by Nicki Borell
Stefan Ulrich

Query spelling inclusions/exclusions

Hi, Unfortunately the spelling inclusions example is a bit misleading. The inclusion terms are just a flat list with terms that will be suggested if the user enters a (sufficiently similar, mis-typed) term. So the fact that you can define term hierarchies in termstore has no application for the spelling inclusion or exclusion lists. This example is more akin to the thesaurus feature, which lets you define query terms that will be expanded to other terms (see e.g. http://technet.microsoft.com/en-us/library/jj219579%28v=office.15%29.aspx).

Posted 05-Nov-2012 by Stefan Ulrich
Nicki Borell

Query spelling inclusions/exclusions

The example in the text is absolutely correct, maybe the screen shot could potentially be misunderstood.

Posted 06-Nov-2012 by Nicki Borell
Stefan Ulrich

Query spelling inclusions/exclusions

Sorry for being picky, just trying to avoid misconceptions about this feature ;)
 
The example seems to suggest that "EI" could be corrected to "ExpertsInside". But that would never happen, since the edit distance is too large. Spelling correction will only suggest terms (both from the built-in dictionaries, or the user inclusion dictionary) that have a sufficiently small edit distance to the user's input terms.
 
To trace query spelling correction, you can check the ULS log messages for event aizf6, which will show the suggestions and their scores if there are any.

Posted 08-Nov-2012 by Stefan Ulrich
Nicki Borell

Query spelling inclusions/exclusions

To end this misery: For all definitely want to know how the feature works follow this links.
Manage query spelling correction in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj591607(v=office.15).aspx
Set-SPEnterpriseSearchQuerySpellingCorrection:
http://technet.microsoft.com/en-us/library/jj219497(v=office.15).aspx
Hope that help to eliminate all potentially misconceptions.

PS: no, I didn’t excuse. No one likes wisenheimer. A helpful link focused on the stuff “query spelling correction” should have had been welcome.

Posted 08-Nov-2012 by Nicki Borell
Steve - SharePoint Developers

grt post

Thanks for the in detail analysis of sharePoint 2013, worth reading

Posted 12-Dec-2012 by Steve - SharePoint Developers

Notify me of comments to this article

E-mail:
   

Add Comment

Title:

 
Comment:
Email:

   


Name:

 
Url: