ShareCafe SharePoint 2010 Search


Published on

What is enterprise search?
Why is good enterprise search important?
What’s new in 2010?
Configuring Search
Search Service Application
Site collection
Search site
What about FAST Search?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

ShareCafe SharePoint 2010 Search

  1. 1. Raas van Gaverestraat 83 B-9000 GENT, BELGIUM E-mail Website Tel. +32 9 330 15 00 VAT BE 456.457.353 Bank 442-7059001-50 (KBC) Thijs ter Beek 30 January, 2015 ShareCafe: SharePoint 2010 Search
  2. 2. 30 January, 2015 Title2 Agenda What is enterprise search? Why is good enterprise search important? What’s new in 2010? Configuring Search Search Service Application Site collection Search site What about FAST Search?
  3. 3. What is enterprise search? 30 January, 2015 Title3 Definition: Enterprise search is the practice of making content from multiple enterprise-type sources, such as databases and intranets, searchable to a defined audience.
  4. 4. 20% structured Enterprise Data Challenges Unmanaged Data is Pervasive & Increasing 80% unstructured 90% of unstructured data is unmanaged Volume of data is increasing ~36%/year Source: Doculabs 4
  5. 5. Information Management Pains Exponential growth of information… …is causing information management pain At least 50% of online searches are not successful 15% to 30% of information worker time spent looking for information ~$18k of lost productivity per information worker per year for a mid-sized company New information produced each year per Information Worker (MB) Source: IDC, Berkeley Megabytes 500 1,000 1,500 2,000 2,500 3,000 3,500 01 02 03 04 05 06 07 08 Source: IDC 5
  6. 6. 30 January, 2015 Title6 What’s new in 2010 Demo Refinements out-of-the-box Wildcard * Better relevancy Better stemming (House/ Houses) Phonetic search in people search (only English)?? Search Query suggestions
  7. 7. 30 January, 2015 Title7
  8. 8. 30 January, 2015 Title8 Search Service Application (Search Config) What do you manage here? Content sources: SharePoint Sites, File Shares, Websites (Using SharePoint index), Exchange Public Folders, Business Data (BCS) Federated locations: Google, Wiki, MSDN, (Using external index) Metadata properties: Properties of the content that need to be searchable (Result properties need to be metadata properties) File Types: What file types to index Logs, Crawl schedules, Authoritive pages (promotion of content)
  9. 9. 30 January, 2015 Title9 Search Scopes (Service Application and Site Collection) Scopes splits index into segments based on: Address Property •Example: ContentType = Contacts Content source •Example: File Share By separating the index you can be more specific and find better results
  10. 10. 30 January, 2015 Title10 Site (Collection) Search settings Standard result page used for search No customization /_layouts/OSSearchResults.aspx Creating a custom search center site Enterprise with tabs Basic without tabs
  11. 11. 30 January, 2015 Title11 Search center site config Tabs Search result page Search query page
  12. 12. 30 January, 2015 Title12 Refinement panel config Promote properties you want to use as refinement Some problems with multiple value lookup/choice columns Crawl Edit webpart refinement web part on results page !Don’t forget to uncheck localisation
  13. 13. 30 January, 2015 Title13 Search Result config Promote the properties you want to show Crawl Create devresults.aspx Fetch columns in core search result webpart Modify xslt: Rik, Bart, Viktor?
  14. 14. 30 January, 2015 Title14 Config federated locations A federated location makes it possible to get search results from an external source The search of the external source should comply with OpenSearch protocol. Most importantly you should be able to receive the results in XML Preconfigured locations  connector-examples/ 
  15. 15. 30 January, 2015 Title15 What about FAST Search  Costs Enterprise licenses Implementation/ running costs Seperate server  Features Preview docs, presentations Automatic keyword extraction Advanced linguistic engine  Possible future project Axel Vervoordt wants to index library with art/design books Requested Features: •Preview pdf docs on right page •Metadata extraction