Alias Mapping Table for Multi-Repository Attribute Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital information systems face inefficiencies in searching for data objects across multiple repositories due to the need for full-text searches that consume significant memory and time, while focused searches may be under-inclusive.
Innovation Solution
Implementing an alias mapping table that associates an alias name with multiple attribute names, allowing for efficient global attribute searches across distributed computing systems by providing user-selected attribute names and storing associations between alias names and attribute names in a relational database table or as metadata, enabling searches across multiple repositories.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full-text search is performed across all repositories, then search completeness is improved, but memory consumption and search time increase significantly
Solution Approach 1:
The system pre-generates and stores inverted indexes for each attribute across all repositories before search operations. These indexes organize attribute values and their corresponding data object locations in advance, allowing the search module to quickly retrieve relevant data without performing full-text scans during actual search operations, thus reducing search time while maintaining completeness
Solution Approach 2:
The patent introduces an alias mapping table as an intermediary component between the search interface and the actual attribute repositories. This mapping table stores relationships between user-friendly alias names and actual attribute names across multiple repositories, enabling the search system to translate user queries into efficient multi-repository searches without requiring users to understand the underlying complex attribute structures, thereby improving search completeness while managing time consumption through optimized query routing
2Reliability
If a full-text search is performed across all repositories, then search completeness is improved, but memory consumption increases significantly
Solution Approach 1:
The system divides the global search space into multiple independent attribute-specific inverted indexes, one for each attribute across different repositories. Instead of maintaining a single large full-text index that consumes excessive memory, the search is segmented into attribute-level searches using pre-built indexes, significantly reducing peak memory consumption while ensuring all relevant data is captured
Solution Approach 2:
The patent creates lightweight copies of attribute metadata and indexing structures in the alias mapping table rather than duplicating entire data objects. The inverted indexes store only essential indexing information (attribute values and data object location pointers) rather than full data copies, enabling efficient searches across multiple repositories with reduced memory overhead
3Productivity
If a focused search is performed to reduce time and memory usage, then search efficiency is improved, but search inclusivity deteriorates
Solution Approach 1:
The alias mapping table serves multiple functions simultaneously: it acts as a translation layer between user queries and repository attributes, a routing mechanism for directing searches to relevant repositories, and a configuration store for attribute relationships. This multi-functionality enables the system to perform focused attribute-specific searches efficiently while maintaining the ability to expand to comprehensive multi-attribute searches when needed, balancing efficiency and inclusivity
Data Source
AI summary
A computer-implemented method of configuring a database system for a global attribute search may include receiving a first user-actuated input in a distributed computing system that comprises multiple executable software applications. The software applications may process data objects in the system, and the data objects may have attributes and corresponding attribute values that are stored in two or more attribute repositories of an attribute system. The first user-actuated input may identify a user-selected attribute having an attribute name. The computer-implemented method may receive a second user-actuated input that identifies a user-determined alias name. The computer-implemented method may store in the attribute system an association between the user-determined alias name and the user-selected attribute name, such that during execution of a global search of attributes in the two or more attribute repositories, the attribute system may provide the user-selected attribute name in response to query input comprising the user-determined alias name.


