Enterprise data re-matching

Abstract

A system and method for managing media advertising enterprise data including a process for learning enterprise data matching. An EDM (Enterprise Data Management) application module can be configured to include a set of rules at an enterprise level to manage disparate and disconnected records associated with an entity. A number of unmatched and enterprise entities that matches with respect to an active entity can be returned based on a fuzzy logic associated with various matching options stored in an EDM database. A matching process can then be performed to accurately match similar records regardless of manual input, location, and format of the records in a distributed system. Each unmatched record can then be assigned with a parent enterprise entity. Such an optimization mechanism can interactively manage and report records at the enterprise level in a simple and efficient manner.

What is claimed is: 
     
         1 . A method of managing distributed and disconnected entity records, the method comprising:
 transmitting requests for entity records, from a first processing device implementing an enterprise data management module, to a second processing device implementing an enterprise management system and to a third processing device implementing an advertising services module;   receiving, at the enterprise data management module, response messages from the enterprise management system and the advertising services module, the response message from the enterprise management system including first entity records, and the response message from the advertising services module including second entity records, wherein:
 the first entity records include enterprise-level market entity records associated with unique enterprise identifiers; 
 the second entity records include a local entity record associated with an advertiser identifier different from the unique enterprise identifiers; 
   matching, at the enterprise data management module, the advertiser identifier to one of the unique enterprise identifiers to generate a matched market entity record, wherein the matching is based, at least in part, on a fuzzy logic match between contents of the local entity record and the enterprise-level market entity records;   receiving, at the enterprise data management module, manual changes including at least one change to entity information associated with the matched market entity record; and   in response to the manual changes, automatically re-matching the matched market entity record including the manual changes to one of the unique enterprise identifiers.   
     
     
         2 . The method of  claim 1 , wherein some market entity records are associated with advertisers, and other market entity records are associated with agents, the method further comprising:
 storing the market entity records associated with advertisers and the market entity records associated with agents in separate tables of a media database.   
     
     
         3 . The method of  claim 1 , wherein re-matching includes:
 receiving, at the enterprise data management module, an old unique enterprise identifier previously assigned to the matched market entity record.   
     
     
         4 . The method of  claim 1 , wherein the manual changes include at least one of:
 a changed name, a changed revenue type, or a changed industry code.   
     
     
         5 . The method of  claim 1 , wherein:
 the unique enterprise identifiers include identifiers assigned by the enterprise management system; and   the advertiser identifier includes an identifier assigned by an advertiser.   
     
     
         6 . The method of  claim 5 , further comprising:
 updating the matched market entity record in a hub database based, at least in part, on one of the unique enterprise identifiers or the advertiser identifier.   
     
     
         7 . The method of  claim 1 , further comprising:
 periodically pulling the first and second entity records into the enterprise data management module.   
     
     
         8 . A system for managing distributed and disconnected entity records, the system comprising:
 an enterprise and media management system including a processor and memory;   a communication module including a processor and memory configured to implement an advertising services module; and   a data-processing system including a processor and memory, the data-processing system including an enterprise data management module configured to:
 transmit requests for entity records to the enterprise and media management system and to the advertising services module; 
 receive response messages from the enterprise and media management system and the advertising services module, the response message from the enterprise and media management system including first entity records, and the response message from the advertising services module including second entity records, wherein:
 the first entity records include enterprise-level market entity records associated with unique enterprise identifiers; 
 the second entity records include a local entity record associated with an advertiser identifier different from the unique enterprise identifiers; 
 
 match the advertiser identifier to one of the unique enterprise identifiers to generate a matched market entity record, wherein the match is based, at least in part, on a fuzzy logic match between contents of the local entity record and the enterprise-level market entity records; 
 receive manual changes including at least one change to entity information associated with the matched market entity record; and 
 in response to the manual changes, automatically re-match the matched market entity record including the manual changes to one of the unique enterprise identifiers. 
   
     
     
         9 . The system of  claim 8 , wherein some market entity records are associated with advertisers, and other market entity records are associated with agents, the enterprise and media management system further configured to:
 store the market entity records associated with advertisers and the market entity records associated with agents in separate tables of a media database.   
     
     
         10 . The system of  claim 8 , the enterprise data management module further configured to:
 receive an old unique enterprise identifier previously assigned to the matched market entity record as part of a re-matching process.   
     
     
         11 . The system of  claim 8 , wherein:
 the manual changes include at least one of a changed name, a changed revenue type, or a changed industry code.   
     
     
         12 . The system of  claim 8 , wherein:
 the unique enterprise identifiers include identifiers assigned by the enterprise and media management system; and   the advertiser identifier includes an identifier assigned by an advertiser.   
     
     
         13 . The system of  claim 12 , the communications module including:
 a hub database; and   the communications module is further configured to update the matched market entity record in the hub database based, at least in part, on one of the unique enterprise identifiers or the advertiser identifier.   
     
     
         14 . The system of  claim 8 , wherein the enterprise data management module is further configured to:
 periodically pull the first and second entity records from the enterprise and media management system and the advertising services module.   
     
     
         15 . A non-transitory computer-readable storage medium storing computer code, the computer code comprising instructions executable by a processor, the instructions comprising:
 at least one instruction to transmit requests for entity records, from a first processing device implementing an enterprise data management module, to a second processing device implementing an enterprise management system and to a third processing device implementing an advertising services module;   at least one instruction to receive, at the enterprise data management module, response messages from the enterprise management system and the advertising services module, the response message from the enterprise management system including first entity records, and the response message from the advertising services module including second entity records, wherein:
 the first entity records include enterprise-level market entity records associated with unique enterprise identifiers; 
 the second entity records include a local entity record associated with an advertiser identifier different from the unique enterprise identifiers; 
   at least one instruction to match, at the enterprise data management module, the advertiser identifier to one of the unique enterprise identifiers to generate a matched market entity record, wherein the matching is based, at least in part, on a fuzzy logic match between contents of the local entity record and the enterprise-level market entity records;   at least one instruction to receive, at the enterprise data management module, manual changes including at least one change to entity information associated with the matched market entity record; and   at least one instruction to automatically re-match the matched market entity record including the manual changes to one of the unique enterprise identifiers.   
     
     
         16 . The non-transitory computer-readable storage medium of  claim 15 , wherein some market entity records are associated with advertisers, and other market entity records are associated with agents, the instructions further comprising:
 at least one instruction to store the market entity records associated with advertisers and the market entity records associated with agents in separate tables of a media database.   
     
     
         17 . The non-transitory computer-readable storage medium of  claim 15 , wherein the instructions further comprise:
 at least one instruction to receive, at the enterprise data management module, an old unique enterprise identifier previously assigned to the matched market entity record.   
     
     
         18 . The non-transitory computer-readable storage medium of  claim 15 , wherein:
 the unique enterprise identifiers include identifiers assigned by the enterprise management system; and   the advertiser identifier includes an identifier assigned by an advertiser.   
     
     
         19 . The non-transitory computer-readable storage medium of  claim 15 , wherein the instructions further comprise:
 at least one instruction to update the matched market entity record in a hub database based, at least in part, on one of the unique enterprise identifiers or the advertiser identifier.   
     
     
         20 . The non-transitory computer-readable storage medium of  claim 15 , wherein the instructions further comprise:
 at least one instruction to periodically pull the first and second entity records into the enterprise data management module.