Skip to main content

SharePoint 2013 Search Center My Experience

In SharePoint 2013 the best of two Search Engines “SharePoint Search” and “FAST Search Server for SharePoint” was combined to make one Search Engine that would provide greater redundancy and for better scalability.

Microsoft did lots of change in search center as compare with new search center. New search center home page the wide text box without any search tabs i.e. “All site”, “People”  no more exist.


Now the tabs are the part of result page in SharePoint 2013. “Search tabs” name changes to “search Vertical”.

There are 4 Search verticals default available in search center.



Everything: Everything vertical comes all results that includes peoples, content, conversations and videos.



The search result depends upon the search term example. 
  • Simple term: Display the result; show the preview in hover cards. There is a option to open document view and edit the item directly. Hover card also display the result directly.
  • People name: If a search term contains user name. The new search result page display the people information also the document created by that person and conversion of that persons 
People: People vertical not only display the people information. If you enter the text in people it will display the name of the person written the same text.



Conversation: it displays the conversation going on or some on mentioned about something that matched by will display on the result page.



Videos: Display all the list of videos at the same time you will play the videos. To Play the document not required any active x control, it runs on HTML 5.



At the end of each result page is links

Alert me: Sends alert with this specific search key words via email. You received email Daily or weekly. Just need to specify type of alert you want to received.
  1. New item in a search result 
  2. Existing item changed 
  3. All Change 
Preference: Similar to Google,  you can save you preference like language, alert option also search history, Opening Documents in the Browser etc.

Search with in document libraries: In large document library, it is difficult to search the specific document within the large library. So in SharePoint 2010 to search document either we create custom view, or filter library items ascending or descending order to get the exact result. In SharePoint 2013, Microsoft added a new feature that allows the user to search the document within a document library.


Query builder: In search center you will find the query builder many places. That help you to create the query and check the result on the fly.
You will find the query builder at following locations.

  1. Core result web part.
  2. Result source
  3. Query rules


Federation Location: We are using federation location to get the external indexed result in the form of RSS (ATOM feed). In SharePoint 2010 to configure the custom federation location we need it to navigate to the CA click to the federation location. This is only available at the Application level.SharePoint 2013 this issue has been removed a now federation location is the part of result source. Check the below image in protocol section there is option button for "OpenSearch 1.0/1.1". 


Contextual Search: So there is no more search drop down in 2010. In 2013 result source displayed at other places, below image is the SharePoint 2013 contextual search box.



Content enrichment web service: This is used for entity extraction. This new service replacement to FAST search document processing pipeline/Processing pipeline extensibility. For that you need to create the custom web service, the custom web service contains the custom code. The code used is customized the manage property during indexed. It is very powerful for extensibility.

Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis