US 12,493,583 B1
Systems and methods for improved database functionality and data translation
Chris Edward Furlong, Charlotte, NC (US); Justin Arthur Adams, Charlotte, NC (US); Ellen Choi, Charlotte, NC (US); Tanner John Fritz, Charlotte, NC (US); and Patrick James Morrell, Charlotte, NC (US)
Assigned to AIWYN, Inc., Charlotte, NC (US)
Filed by Aiwyn, Inc., Charlotte, NC (US)
Filed on Feb. 28, 2023, as Appl. No. 18/175,842.
Claims priority of provisional application 63/315,264, filed on Mar. 1, 2022.
Int. Cl. G06F 7/00 (2006.01); G06F 16/13 (2019.01); G06F 16/17 (2019.01)
CPC G06F 16/1727 (2019.01) [G06F 16/134 (2019.01)] 16 Claims
OG exemplary drawing
 
1. A method for formatting a unified database, comprising:
receiving, via at least one computing device, one or more data files, wherein the one or more data files comprise different formats;
determining, via the at least one computing device, a configuration for a data file from the one or more data files, wherein the data file comprises a particular format of the different formats;
parsing, via the at least one computing device, the data file into one or more cells;
associating, via the at least one computing device, each of the one or more cells, which are associated with a first primary key, with a first entity of a plurality of entities, wherein one or more entities of the plurality of entities is linked via one or more respective foreign keys;
configuring the one or more cells from the particular format into a unified format, via the at least one computing device, based on the configuration;
extracting, via the at least one computing device, a first key from the one or more cells, wherein the configuration defines a location of the first key in the one or more cells;
identifying, via the at least one computing device, a dependent entity associated with the data file based on the first key;
storing, via the at least one computing device, the one or more cells in a cache based on a determination that the dependent entity is not present in a destination data store;
aggregating the one or more cells into a message, via the at least one computing device, based at least on the dependent entity;
retrieving from the destination data store, via the at least one computing device, a second primary key associated with the dependent entity;
storing, via the at least one computing device, the second primary key in the one or more cells;
associating, via the at least one computing device, the first key with the dependent entity;
excluding, via the at least one computing device, the first entity from the message; and
upon determining that the dependent entity has been added to the destination data store, transmitting, via the at least one computing device, the message from the cache to the destination data store, wherein the destination data store comprises the unified database.