26. A method for optimizing data queries for related records in a reliable fashion, to be used with a system having a first computing device communicatively coupled with a second and a third computing device, and communicatively coupled to a first database that stores real-world entity data, having said second computing device communicatively coupled with said first and said third computing device, and communicatively coupled to a second database that stores real-world entity data, having said third computing device communicatively coupled with said first and said second computing device, and communicatively coupled to a third database that stores real-world entity data, a first end-user interface communicatively coupled to said first database, a second end-user interface communicatively coupled to said second database, and a third end-user interface communicatively coupled to said third database, comprising: providing a hierarchical system of Consolidation Strings for said first database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said first database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said first database, acting as a first data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing a hierarchical system of Consolidation Strings for said second database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said second database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said second database, acting as a second data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing a hierarchical system of Consolidation Strings for said third database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said third database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said third database, acting as a third data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing the capability of said first end-user interface to allow a first end-user to query said first data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said second and third data-source nodes, wherein said first data-source node communicates consolidation information to said second and third data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said second and third data-source nodes, and wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view; providing the capability of said second end-user interface to allow a second end-user to query said second data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said first and third data-source nodes, wherein said second data-source node communicates consolidation information to said first and third data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said first and third data-source nodes, and wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view; and providing the capability of said third end-user interface to allow a third end-user to query said third data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said first and second data-source nodes, wherein said third data-source node communicates consolidation information to said first and second data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said first and second data-source nodes, wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view.
26. A method for optimizing data queries for related records in a reliable fashion, to be used with a system having a first computing device communicatively coupled with a second and a third computing device, and communicatively coupled to a first database that stores real-world entity data, having said second computing device communicatively coupled with said first and said third computing device, and communicatively coupled to a second database that stores real-world entity data, having said third computing device communicatively coupled with said first and said second computing device, and communicatively coupled to a third database that stores real-world entity data, a first end-user interface communicatively coupled to said first database, a second end-user interface communicatively coupled to said second database, and a third end-user interface communicatively coupled to said third database, comprising: providing a hierarchical system of Consolidation Strings for said first database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said first database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said first database, acting as a first data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing a hierarchical system of Consolidation Strings for said second database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said second database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said second database, acting as a second data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing a hierarchical system of Consolidation Strings for said third database, wherein each Consolidation String in said hierarchical system represents one or more key pieces of information relating to a real-world entity stored in said third database, wherein the information represented in each Consolidation String is in a character format, wherein the hierarchical ranking of Consolidation String priorities are used to optimize database queries to find matching records for at least one entity of interest with substantial certainty, and wherein Inter-Node Consolidation is set up for said third database, acting as a third data-source node in the overall system, by periodically communicating its Consolidation Strings to other data-source nodes; providing the capability of said first end-user interface to allow a first end-user to query said first data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said second and third data-source nodes, wherein said first data-source node communicates consolidation information to said second and third data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said second and third data-source nodes, and wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view; providing the capability of said second end-user interface to allow a second end-user to query said second data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said first and third data-source nodes, wherein said second data-source node communicates consolidation information to said first and third data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said first and third data-source nodes, and wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view; and providing the capability of said third end-user interface to allow a third end-user to query said third data-source node, which in turn queries any associated Consolidated Strings associated with the query for the entity to identify related records contained in said first and second data-source nodes, wherein said third data-source node communicates consolidation information to said first and second data-source nodes, wherein said consolidation information is applied against a consolidation algorithm in each said first and second data-source nodes, wherein said consolidation algorithm looks for a pair of entity records with Consolidation Strings on the same priority level that are character-wise identical, and when such an entity match is found, said matching entity records are consolidated from an end-user's point of view. 31. The method in claim 26 , wherein said periodic communication of Consolidated Strings to other data-source nodes consists of all of the communication-originating data-source node's Consolidated Strings and source-record identifiers, wherein a data-source node is allowed to deconsolidate if there are changes in the communication-originating data-source node, and a data-source node can query back to querying data-source nodes to get more information.