Entity id lineage persistence and cross-tenant durability

Abstract

Among other techniques, techniques for dynamic survivorship, cross-tenant matching, and lineage entity identifier (EID) promotion are described. A system utilizing these techniques can include an industry-agnostic datastore, an industry-focused datastore, a tenant datastore, a new dataset datastore, a new dataset onboarding engine, an EID assignment engine, an object registration engine, a primary EID selection engine, a matching engine, a merging engine, a survivorship engine, a cross-tenant matching engine, and a lineage EID promotion engine. A method utilizing these techniques can include new dataset onboarding, EID assignment, object registration, primary EID selection, matching, merging, survivorship, cross-tenant matching, and lineage EID promotion.

What is claimed is: 
     
       1. A system comprising:
 an entity identifier (EID) assignment engine; 
 a primary EID selection engine coupled to the EID assignment engine; 
 a survivorship engine coupled to the primary EID selection engine; 
 a lineage EID promotion engine coupled to the survivorship engine; 
 wherein, in operation:
 the EID assignment engine assigns an EID to a first object stored in a datastore of a multitenant EID lineage-persistent relational database management system (RDBMS), wherein the datastore has an n-tier architecture, wherein the datastore includes an industry-agnostic datastore in a Layer  1  (L 1 ) datastore of the n-tier architecture, wherein the datastore includes an industry-focused datastore in a Layer  2  (L 2 ) datastore of the n-tier architecture, wherein the datastore includes a tenant datastore in Layer (L 3 ) datastores of the n-tier architecture, and wherein L 3  inherits objects from L 2 ; 
 the primary EID selection engine, for a first set of EIDs that reference a common real world entity with which the first object is associated, selects a primary EID from a first set of EIDs of the first object; 
 the survivorship engine, when the first object is merged with a second object to produce a third object, maintains the first set of EIDs as a first set of persistent lineage EIDs in association with first attributes of the first object, maintains a second set of EIDs as a second set of persistent lineage EIDs in association with second attributes of the second object, and maintains the first set of persistent lineage EIDs and the second set of persistent lineage EIDs in association with the third object; 
 the lineage EID promotion engine, when the first object is unmerged from the second object, the third object, or a fourth object that is a child or grandchild of the third object, selects a lineage EID of the first set of persistent lineage EIDs to serve as a primary EID of the now-unmerged first object; 
 wherein a first tenant object is stored in a first tenant datastore of the L 3  datastores and a second tenant object is stored in a second tenant datastore of the L 3  datastores, comprising a cross-tenant matching engine that matches the first tenant object with the second tenant object. 
 
 
     
     
       2. The system of  claim 1 , comprising a new dataset onboarding engine that receives a new dataset including an object that is assigned an EID by the EID assignment engine. 
     
     
       3. The system of  claim 1 , comprising an object registration engine that registers an object in association with a source of the object. 
     
     
       4. The system of  claim 1 , comprising a matching engine that identifies within a tenant a first profile of the first object and a second profile of the second object that are semantically the same or similar. 
     
     
       5. The system of  claim 1 , comprising a merging engine that merges the first object and the second object while aggregating crosswalks, attribute values, relationships, and interactions from contributing profiles of the first object and the second object into a winning profile. 
     
     
       6. A method comprising:
 assigning an entity identifier (EID) to a first object stored in a datastore of a multitenant EID lineage-persistent relational database management system (RDBMS), wherein the datastore has an n-tier architecture, wherein the datastore includes an industry-agnostic datastore in a Layer  1  (L 1 ) datastore of the n-tier architecture, wherein the datastore includes an industry-focused datastore in a Layer  2  (L 2 ) datastore of the n-tier architecture, wherein the datastore includes tenant datastore in Layer (L 3 ) datastores of the n-tier architecture, and wherein L 3  inherits objects from L 2 ; 
 for a first set of EIDs that reference a common real world entity with which the first object is associated, selecting a primary EID from a first set of EIDs of the first object; 
 when the first object is merged with a second object to produce a third object, maintaining the first set of EIDs as a first set of persistent lineage EIDs in association with first attributes of the first object, maintaining a second set of EIDs as a second set of persistent lineage EIDs in association with second attributes of the second object, and maintaining the first set of persistent lineage EIDs and the second set of persistent lineage EIDs in association with the third object; 
 when the first object is unmerged from the second object, the third object, or a fourth object that is a child or grandchild of the third object, selecting a lineage EID of the first set of persistent lineage EIDs to serve as a primary EID of the now-unmerged first object, wherein a first tenant object is stored in a first tenant datastore of the L 3  datastores and a second tenant object is stored in a second tenant datastore of the L 3  datastores, comprising a cross-tenant matching engine that matches the first tenant object with the second tenant object. 
 
     
     
       7. The method of  claim 6 , comprising receiving a new dataset including an object that is assigned an EID. 
     
     
       8. The method of  claim 6 , comprising registering an object in association with a source of the object. 
     
     
       9. The method of  claim 6 , comprising identifying within a tenant a first profile of the first object and a second profile of the second object that are semantically the same or similar. 
     
     
       10. The method of  claim 6 , comprising merging the first object and the second object while aggregating crosswalks, attribute values, relationships, and interactions from contributing profiles of the first object and the second object into a winning profile.