Entity Resolution Search System for CRM Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multiple users entering disparate data for the same entity across different customer relation management databases leads to duplicate records and inefficient data assimilation, wasting network resources and slowing down search results.
Innovation Solution
A system and method that allows users to search for existing records of an entity, with interactive drill-down menus to filter and merge data, and creates new records if none are found, ensuring consistent information across databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a master platform assimilates information from multiple records, then data consistency is improved, but network resources are wasted and search speed is reduced
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing entity resolution results, match scores, and merged data in the database before search queries are executed. This eliminates the need for real-time assimilation of information from multiple records during search operations, thereby reducing network resource consumption while maintaining data consistency through pre-established resolution mappings.
Solution Approach 2:
The patent introduces an intermediary entity resolution system that acts as a mediator between multiple customer relation management databases. This intermediary pre-resolves entity duplicates and stores the resolved data structure, allowing search queries to access consolidated information without requiring real-time assimilation across platforms, thus reducing network resource expenditure while ensuring data consistency.
2Reliability
If a master platform assimilates information from multiple records, then data consistency is improved, but search speed is reduced
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing entity resolution results, match scores, and merged data in the database before search queries are executed. This eliminates the need for real-time assimilation of information from multiple records during search operations, thereby reducing network resource consumption while maintaining data consistency through pre-established resolution mappings.
Solution Approach 2:
The patent segments the data assimilation process into distinct phases: offline entity resolution and data merging, and online search query execution. By separating these functions, the system pre-processes data consistency issues independently from search operations, allowing search queries to execute quickly against pre-resolved data without being hindered by real-time assimilation requirements.
3Quantity of substance
If users enter data for the same entity across different platforms, then data completeness is improved, but duplicate records are created
Solution Approach 1:
The system implements feedback mechanisms that detect when new data entries correspond to existing entities based on matching attributes (name, address, contact information). When duplicates are detected, the system provides feedback to users by displaying existing records alongside new entry forms, allowing users to see matching records and avoid creating duplicates while still capturing comprehensive data across multiple platforms.
Solution Approach 2:
The patent introduces an intermediary entity resolution system that acts as a mediator between multiple customer relation management databases. This intermediary pre-resolves entity duplicates and stores the resolved data structure, allowing search queries to access consolidated information without requiring real-time assimilation across platforms, thus reducing network resource expenditure while ensuring data consistency.
Data Source
AI summary
Examples are directed to systems and methods that cause a first user interface having an input field that receives a search query to be displayed. A search query having an attribute of a first entity is received at the input field. Data records are searched for a second entity using the attribute when the search query is received. A second user interface is displayed that has a data record for the second entity. The data record lists the attribute and an additional attribute of the second entity. The second user interface has a drill down user interface that lists the attribute and the additional attribute. The attribute and the additional attribute are selectable to reconfigure the second user interface. The second user interface has a selectable option to create a new data record where the option corresponds to an indication that the first entity is different from the second entity.


