# US 10,769,169 B2 · System for automatically creating and associating data conversion programs with source and target data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,769,169 B2 - Document ID: US10769169B2 - Status: Granted - Kind: B2 - Application number: 16/175,599 - Filed: 2018-10-30 - Published: 2019-02-28 - Granted: 2020-09-08 - Earliest claimed: 2015-04-25 - Applicants: Phillip Hiroshige - Inventors: Phillip Hiroshige - Web page: https://patentgrep.com/patent/US10769169B2 ## CPC - G06F 16/258: {Data format conversion from or to a database} - G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A networked computing system where data from multiple sources is automatically tracked through a plurality of conversion steps at the data row and element level. The system allows input of data conversion metadata. The system automatically applies a version number to the conversion metadata. The system includes a data conversion engine. The data conversion engine ensures that processing metadata versions are in sync with versions of converted data. The conversion engine creates version synchronization at the data row and element level thus allowing data tracking at the data row and element level. The system includes a database that stores conversion metadata and execution attributes and a graphical user interface that allows the user access to the conversion metadata. ## Claims ### Claim 1 A system of data tracking a source dataset comprising: a data tracking computer comprising a memory, a processor, and a plurality of software instructions, the software instructions when executed by the processor cause the processor to: receive, from a client device, data conversion instructions for one or more data elements of the plurality of data elements; store the data conversion instructions as conversion metadata; associate the conversion metadata with the source dataset in the memory; create a unique version number based on the conversion metadata; create a conversion program from the conversion instructions of the conversion metadata; execute the conversion program to perform a data conversion on the one or more data elements to form a target dataset comprising one or more converted data elements; and associate and store the unique version number with the conversion metadata, with the conversion program, and with the target dataset in the memory. ### Claim 2 (depends on 1) The system of claim 1, wherein another unique version number is created when the conversion metadata is modified. ### Claim 3 (depends on 2) The system of claim 2, wherein the another unique version number is associated and stored with the conversion metadata, with the conversion program, and with the target dataset. ### Claim 4 (depends on 3) The system of claim 3, wherein the execution attributes are stored in the data build. ### Claim 5 (depends on 1) The system of claim 1, wherein the software instructions when executed by the processor further cause the processor to: store the source dataset, conversion metadata with the associated unique version number, and the target dataset with the associated unique version number as a data build, in the memory. ### Claim 6 (depends on 5) The system of claim 5, wherein the target dataset of a first data build is used as a second source dataset to create a second data build comprising the second source dataset, a second conversion metadata with a second associated unique version number, and a second target dataset with the second associated unique version number. ### Claim 7 (depends on 5) The system of claim 5, wherein multiple data builds are grouped, sequenced and stored as a data flow in a data build database. ### Claim 8 (depends on 7) The system of claim 7, wherein the data flow comprises lineage data describing the relationship between the first and second data build. ### Claim 9 (depends on 8) The system of claim 8, wherein the data build database is used to automatically create one or more data builds. ### Claim 10 (depends on 8) The system of claim 8, wherein multiple data tracking systems are networked to track data movement through data flows across multiple data tracking systems. ### Claim 11 (depends on 1) The system of claim 1, wherein the conversion program creates execution attributes. ### Claim 12 A system of data tracking a source dataset comprising: a data tracking computer comprising a memory, a processor, and a plurality of software instructions, the software instructions when executed by the processor cause the processor to: receive, from a client device, data conversion instructions for one or more data elements of the plurality of data elements; store the data conversion instructions as conversion metadata; associate the conversion metadata with the source dataset in the memory; create a unique version number based on the conversion metadata; create a conversion program from the conversion instructions of the conversion metadata; execute the conversion program to perform a data conversion on the one or more data elements to form a target dataset comprising one or more converted data elements; and associate and store the unique version number with the conversion metadata, with the conversion program, and with each converted data element in the memory. ### Claim 13 (depends on 12) The system of claim 12, wherein another unique version number is created when the conversion metadata is modified, by the data build manager, and, wherein the another unique version number created when the conversion metadata is modified is associated and stored with the conversion metadata, with the conversion program, and with each converted data element with the processor in the memory. ### Claim 14 (depends on 13) The system of claim 13, wherein the software instructions when executed by the processor further cause the processor to: associate and store the another unique version number with the target dataset. ### Claim 15 (depends on 14) The system of claim 14, wherein the software instructions when executed by the processor further cause the processor to: store the source dataset, conversion metadata with the associated unique version number, and the target dataset with the associated another unique version number as a data build. ### Claim 16 (depends on 14) The system of claim 14, wherein the conversion program creates execution attributes. ### Claim 17 (depends on 16) The system of claim 16, wherein the execution attributes are stored in the data build. ### Claim 18 (depends on 17) The system of claim 17, wherein the target dataset of a first data build is used as a second source dataset to create a second data build comprising the second source dataset, a second conversion metadata with a second associated unique version number, and a second converted dataset with the second associated unique version number. ### Claim 19 (depends on 18) The system of claim 18, wherein the first data build and second data build are stored as a data flow in the memory. ### Claim 20 (depends on 19) The system of claim 19, wherein the data flow comprises lineage data describing the relationship between the first data build and the second data build. ### Claim 21 (depends on 20) The system of claim 20, wherein a graphic user interface is configured to present summary information of the data builds in a data flow, and wherein the graphic user interface may be used to select an item of summary information regarding a data build, and the conversion metadata associated with the summary information of that data build may then be presented to the user by the graphic user interface.