Skip to main content

Enterprise Search: Factors to be considered

Social and Enterprise Search capabilities are becoming very important for the Enterprises.

While Enterprise Social capability enables employees across different groups to collaborate and share knowledge, Enterprise Search capability enables employees to search digital content & data spread across different isolated systems and applications

Success of an Enterprise Search capability not only depend on the technology /platform that is leveraged but also on other key factors such as:

  1. Content Sources

Analysis of the sources from which content will be searched and made available for the end user consumption. If the source systems are not analyzed properly in terms of content volume, Meta data of the content, then there will be miss match between what is expected by the end user and what the Enterprise Search capability shows as search results. If the content in the source systems are not marked with proper metadata or if the metadata in the source systems are not understood properly leading to wrong mapping, then it will result in irrelevant search results.


  1. Security

Access restrictions on the content in the various sources; every source will have its own access restrictions on its content / data like which group of users will have access to view , update & delete. It is important that when these content / data is made available as part of search results, same access (view) restrictions are to be carried out ; Mechanisms employed for achieving access restriction will vary from one content source to another and they have to be understood and accordingly search capability is to be planned


  1. Scheduling of Search Crawls


Content in different content sources will get updated in different time intervals and there will be also variations in update frequency. This has to be taken into consideration when finalizing schedules when various content sources will be crawled by the search capability. Improper scheduling of crawls will result in old / irrelevant data surfacing in the search result.


  1. Personas

It is important to understand the different personas of an enterprise who will use the search capability and their intent of search. For example, search results that is expected by an executive from the finance department of an enterprise, for a given query word will differ from that is expected by an executive from the sales department.

  1. End user awareness


Success of an Enterprise Search capability also depends on how end user’s expectation are met. Every user is already exposed to the internet search capabilities such as Bing, Google etc. and their expectation on Enterprise Search capability will be on similar lines. But dynamics of Enterprise Search capability differs from internet search capabilities in terms security, content relevancy based on user persona, freshness etc. and enterprise end users are to be educated accordingly.
Labels:

Comments

Post a Comment

Popular posts from this blog

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive. At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists. With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time    More  
14 comments
Read more

Heterogeneous Cloud Integration

Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.   These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.   With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters   Within datacenters / on premise, integration product
10 comments
Read more

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...
7 comments
Read more