Enterprise Search Best Practices Webinar 4.2013


Published on

Read through our latest webinar held in conjunction with Google Enterprise all about Enterprise Best Practices and creating successful search applications using the Google Search Appliance 7.0. Search Technologies provides implementation and consulting services to Google search Appliance Customers. For further information, see http://www.searchtechnologies.com/google-search-appliance-services.html


Published in: Technology, News & Politics
  • 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
  • We’re an IT services company dedicated to search engines Search is all we do We believe that we are the largest company of our kindWe provide strategic consulting, implementation work, and a range of managed servicesWe are technology independent and work with all of the leading search engine vendors.Established in 2005, we now have about 110 staff and more than 400 customers. A growing proportion of our customers now use the Google Search Appliance.
  • We have worked with more than 130 customers who have chosen to use the GSA, here are a few of them
  • Why not stick with the embedded search functionality that most repositories provide?READ SLIDEIn the case of the GSA, it will look familiar too…
  • Scale within the enterprise also implies a wide variety of document types, formats and lengths, which further complications relevancy calculation.I’ll leave it to Google to mention the technical aspects of achieving relevance at scale during their presentation.
  • The number 1 reason for not finding something through using search is simple – because it has not been indexed.To index content, of course you need data connectors.In the GSA environment, there’s a growing range of connectors available, both from Google and from third parties. There’s also an API for developing new connectorsEvery company has its own combination of repositories to connect to
  • Connectors almost always need configuration. Even where they will literally plug-and-play, and with the with GSA this is often the case, it is still worth taking the time to understand the full range of configuration possibilities. Connectors frequently have issues.We’ve seen many companies over the years who have approached enterprise search with strong expectations of plug-and-play when it comes to connectors, only to be discouraged when things don’t run entirely smoothly.When issues occur, it is usually not because of the connector software. Most issues are caused by the characteristics of the repository, or by the IT environment more generally.The enterprise search implementation team typically has no control over the configuration of document repositories, so you have to “go with the flow” and work with what is available. Security causes the most connector issues, I’ll come back to that shortly.But the good news is that with planning, and with a willingness to configure or customize, pretty much any repository can be successfully connected to, and this gets us to base camp, getting the content indexed and made searchable
  • The point is, you need metadata to do this.The GSA provides a RESTful / xml results delivery services that can be used to create user interfaces such as these
  • Thanks for your attention.If you have any questions that you’d prefer weren’t discussed in public, please feel free to drop me an email.
  • Enterprise Search Best Practices Webinar 4.2013

    1. 1. ENTERPRISE SEARCH BEST PRACTICESIain Fletcherifletcher@searchtechnologies.comBill Fowlerbfowler@searchtechnologies.comGreg Gomezggomez@google.comMaria Lundahlmlundahl@google.com
    2. 2. Agenda• Search Technologies Overview• Enterprise Search Best Practices• Three pillars of enterprise search success• Google Demo Presentation• Q&A2
    3. 3. Search Technologies Overview• The largest IT services company focused on searchengines• Consulting• Implementation• Managed services• Technology independent, working with most of the leadingsearch engine vendors• An increasing proportion of customers using the GSA3
    4. 4. Search Technologies Overview4San Diego, CASan Jose, CRHerndon, VAAscot, UKCincinnati, OH
    5. 5. Some of our GSA customers5
    6. 6. Introduction• The GSA is used for a wide range of search solutions• Many initial GSA implementations address “plug-in-and-go”• We are working with an increasing number of GSAcustomers to extend to enterprise-scale6
    7. 7. Enterprise Search ApplicationsBetter search improves awide range of business processes7• Compliance & Risk• Customer Service Support• Research & Development• Legal & Contracts• Competitive Intelligence• People/Expert Search• General Intranet…Internal• Partner Extranet• Online Publishing• Ecommerce• Customer Self-service• Field Maintenance• Website Search• Tech Sales Support…External
    8. 8. The Platform ApproachKey Advantages• Cost sharing provides lower TCO• Agility is improved, as it is much easier to create newapplications or repurpose content via search, to meetemerging needs• Improved user productivity• Users benefit from a consistent and instantly available, repositoryindependent search experience8
    9. 9. Relevancy &ScalabilityConnectivity &SecurityMetadataCapture & CreationThree pillars of Enterprise Search successEnterprise Search Foundations9
    10. 10. Relevancy & Scalability• Relevancy is easy over small data sets• Most modern search engines scale well in terms ofdocument count and query load• Maintaining relevancy at scale is the challenge• Poor relevancy is a common complaint with existing enterprisesearch systems• This is a sweet spot for the GSA10
    11. 11. Connectivity & Security• What is the #1 reason to not find information?• Because it hasn’t been indexed• Data connectors enable the search engine to accesscontent sources• A growing range of connectors are available for the GSA• There is also a connector framework for custom developments• Every company has its own combination of repositories11
    12. 12. Connectivity & Security• Connectivity occasionally creates “issues”• These are mostly caused by the characteristics of the repository orthe general IT environment, rather than by faults with the connectorsoftware• Security causes the most issues• In larger organizations, security can be complex• Multiple LDAP/AD servers• Nested permissions, etc.12
    13. 13. Connectivity & SecurityBest Practices:• Don’t expect connectors to always “plug-and-go”• Usually they will, but sometimes it will take a little effort• Secure connectivity can almost always be achieved• Take security seriously• Make friends not enemies of repository owners byshowing them that you take security seriously – youwill need their cooperation!13
    14. 14. Metadata Capture & CreationMetadata is the foundation of important search functions.For example:• It supports relevancy• It drives dynamic navigation• It enables infographical results display14
    15. 15. Dynamic Navigation15
    16. 16. Infographical Results• Via RESTful/xml results delivery• Holistic results display, graphical navigation….16
    17. 17. Creating & Capturing MetadataCapture• Be diligent about taking what is available from the source• This includes metadata encoded into file paths, oravailable from complimentary sourcesCreation• Automate the creation of metadata based onextraction techniques• The GSA 7 provides new capabilities for this“Entity Recognition”17
    18. 18. New with GSA 7: Entity Recognition• Provides both “regex” and dictionary-based approaches toautomated metadata creation• Regex – identifies patterns in the content to match names, emails,phone numbers, etc.• List-based, enables a focus on industry or company specificterminology• Open & Customizable18
    19. 19. Summary• The GSA 7 has a full set of capabilities to deliver enterprisesearch excellence• Key issues are:• Relevancy at scale• Security-compliant connectivity capabilities• Metadata capture and auto-generation capabilities• Plus the administrative simplicity you’d expect from aGoogle application19
    20. 20. The Google Approach• Google receives >1B queries perday• Algorithm is made up of >200signals• >500 changes to the algorithmeach year• Each change is analyzed through1% testing of actual Google traffic• Over 10,000 such experimentseach yearSignalsSignals
    21. 21. Evolution of the Google Search Appliance2002 2009 20126.14Apr Oct Dec20117.0Sep20046.10 6.122006 201350X Increase in Capacity between 2002 and 20132M to 100M documents
    22. 22. Demo – GSA 7.0• Cross-Platform Search Results• Security Trimming• Dynamic Navigation• Entity Recognition• Document Preview• Language Translation• Expert Search22
    23. 23. Thank You!