Book contents
- Frontmatter
- Dedication
- Contents
- Foreword
- Preface
- Acknowledgements
- Making search work – critical success factors
- 1 Search must work
- 2 How search works
- 3 The search business
- 4 Making a business case for search
- 5 Specifying and selecting a search engine
- 6 Optimizing search performance
- 7 Search usability
- 8 Desktop search
- 9 Implementing web search
- 10 Implementing search for an intranet
- 11 Enterprise search
- 12 Multilingual search
- 13 Future directions
- Appendix Search software vendors
- Further reading
- Glossary
- Subject index
- Company index
- Frontmatter
- Dedication
- Contents
- Foreword
- Preface
- Acknowledgements
- Making search work – critical success factors
- 1 Search must work
- 2 How search works
- 3 The search business
- 4 Making a business case for search
- 5 Specifying and selecting a search engine
- 6 Optimizing search performance
- 7 Search usability
- 8 Desktop search
- 9 Implementing web search
- 10 Implementing search for an intranet
- 11 Enterprise search
- 12 Multilingual search
- 13 Future directions
- Appendix Search software vendors
- Further reading
- Glossary
- Subject index
- Company index
Summary
In this chapter:
■ An introduction to enterprise search
■ Technology and implementation issues
■ A ten-step procedure that will ensure effective enterprise search implementation
Introduction
The term ‘enterprise’ tends to be widely used in the IT industry to signify a high-performance software application for use by Fortune 500-type companies. Over the last few years there has been much discussion about what the difference is between a web content management application and an enterprise content management (ECM) application. The same applies to the search business, although, in common with ECM applications, there is the sense that these solutions are designed primarily to work behind the corporate firewall.
The concept of enterprise search is to be able to locate information from any specified server/application, which may include not only internal servers but also external information services. This information might be held in:
■ unstructured text files (e.g. web and intranet sites, record and document management systems, e-mail servers)
■ structured relational databases (e.g. finance systems, enterprise resource planning, customer relationship management)
■ video and image collections (e.g. digital asset management, video conference recordings, video training)
■ specialized collections (e.g. project management applications, engineering and architectural drawings, maps, geospatial data, genomic databases).
This list is very incomplete, and of course the complexity is increased quite substantially by the extent of language diversity. In many enterpriselevel applications the two languages are UK English and American English, and although there are no issues of transliteration and translation, the problems of synonym management (e.g. gas rather than petrol) are very substantial. It does not help that few organizations would have an accurate list of all the database applications and servers that might contain information broadly relevant to the totality of the enterprise.
Another issue with the term ‘enterprise’ is that it has a connotation of a for-profit organization. The reality is that all organizations are an enterprise when it comes to specifying a search solution.
In many organizations the requirement for enterprise search starts with the need to provide an effective search solution for an intranet. It is often when implementing an intranet search solution that the organization realizes that employees would benefit from access to a wider range of information applications, and then finds that the intranet solution is not adequately scalable in power or extensible in functionality to provide an enterprise search solution.
- Type
- Chapter
- Information
- Making Search WorkImplementing web, intranet and enterprise search, pp. 113 - 126Publisher: FacetPrint publication year: 2007