Enterprise Search Paneling by Query Type
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise search systems face challenges in providing relevant results due to the complexity of multiple repositories and static ordering of search results, which hinders users in finding specific data within large organizations, especially when searching across different job roles or data types.
Innovation Solution
A system that determines the search type from a user's query and orders repositories accordingly, displaying search results in separate panels based on each repository's relevancy, allowing for customization and prioritization of search results through a plug-in architecture and user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If search results are blended into a single list with static tab ordering, then the search system is simple to implement, but it becomes difficult for users to maintain mental continuity and isolate desired results from specific repositories
Solution Approach 1:
The patent divides the search results into separate panels for each repository type (e.g., documents, images, videos, web pages) rather than blending them into a single list. Each panel displays results from its specific repository, allowing users to easily isolate and focus on desired result types while maintaining a organized, multi-panel presentation structure.
2Measurement precision
If role-based search algorithms are implemented for each job title, then search relevancy improves for role-specific queries, but the system complexity increases burdenously for large companies with many job titles
Solution Approach 1:
The patent implements a universal search system that searches all repositories for all users regardless of role or job title. The same search algorithm and interface are used by everyone, eliminating the need for separate role-based algorithms while maintaining search functionality across diverse user needs and repository types.
3Adaptability or versatility
If the same search criteria are applied to all repository types with static ordering, then the search algorithm is simple to implement, but the results do not reflect user-specific relevancy or intent
Solution Approach 1:
The patent applies different search criteria and ordering rules to different repository types based on their specific characteristics. Each repository panel uses criteria appropriate to its data type (e.g., different weighting for documents versus images), allowing the search system to adapt to user intent and repository-specific qualities without requiring a completely different algorithm for each type.
Data Source
AI summary
In one embodiment, a search string is received from a user and the search type of the search is determined from the search string. Based on the search type, an order of repositories to search is determined and each repository is searched. The search results from each repository are displayed for the user in separate panels for each repository and the panels are ordered based on search type and the search results within each panel are ordered using that respective repository's relevancy.