IP Library Granted Patent US 12,099,514
Granted Patent B2
US 12,099,514 · App. 18/172,093 · Granted Sep 24, 2024

Transforming data metrics to maintain compatibility in an enterprise data warehouse

Inventors: Karishma Dambe (Fremont, CA); Dmytro Manannykov (Pleasanton, CA); Saiyad Shah (Pleasanton, CA)
Assignee: Chime Financial, Inc.
G06F16/254G06F16/2365
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,099,514
App. No.
18/172,093
Granted
Sep 24, 2024
Kind
B2
Abstract

The present disclosure relates to systems, non-transitory computer-readable media, and methods for transforming data metrics to conform to a production schema for cross-domain uniformity. In particular, in one or more embodiments, the disclosed systems receive a metric having an initial schema, determine that the initial schema is inconsistent with a production schema, transform the metric to conform with the production schema, and store the metric in a standardized-schema database.

Claims (45)

1. A method comprising:

receiving a first metric having a first initial schema and corresponding to a first data domain;

receiving a second metric having a second initial schema and corresponding to a second data domain;

determining that the first initial schema is inconsistent with a first production schema specific to the first data domain;

determining that the second initial schema is inconsistent with a second production schema specific to the second data domain, wherein the second production schema is different from the first production schema;

transforming the first metric to conform to the first production schema specific to the first data domain;

transforming the second metric to conform to the second production schema specific to the second data domain; and

storing, in a standardized-schema database, the first metric having the first production schema and the second metric having the second production schema.

2. The method of claim 1 , wherein receiving the first metric comprises retrieving the first metric from an ingestion database, a staging database, or a data-domain-specific database.

3. The method of claim 1 , further comprising utilizing executable instructions in a test schema to generate the first metric.

4. The method of claim 1 , further comprising verifying that the first metric follows the first production schema before storing the first metric in the standardized-schema database.

5. The method of claim 1 , further comprising receiving an additional metric having an additional initial schema differing from the first initial schema and corresponding to the first data domain.

6. The method of claim 5 , further comprising determining that the additional initial schema is inconsistent with the first production schema specific to the first data domain.

7. The method of claim 6 , further comprising transforming the additional metric to conform to the first production schema specific to the first data domain.

8. The method of claim 1 , wherein the standardized-schema database stores data having the first production schema specific to the first data domain and stores additional data having an additional production schema specific to an additional data domain.

9. The method of claim 1 , further comprising:

storing, in a data-domain-specific database, the first metric having the first production schema specific to the first data domain; and

storing, in an additional data-domain-specific database, an additional metric having an additional production schema specific to an additional data domain.

10. The method of claim 1 , further comprising generating an owner role, a writer role, and a reader role for the first initial schema.

11. A system comprising:

at least one processor; and

a non-transitory computer readable medium comprising instructions that, when executed by the at least one processor, cause the system to:

receive a first metric having a first initial schema and corresponding to a first data domain;

receive a second metric having a second initial schema and corresponding to a second data domain;

determine that the first initial schema is inconsistent with a first production schema specific to the first data domain;

determine that the second initial schema is inconsistent with a second production schema specific to the second data domain, wherein the second production schema is different from the first production schema;

transform the first metric to conform to the first production schema specific to the first data domain;

transform the second metric to conform to the second production schema specific to the second data domain; and

store, in a standardized-schema database, the first metric having the first production schema and the second metric having the second production schema.

12. The system of claim 11 , further comprising instructions that, when executed by the at least one processor, cause the system to receive an additional metric having an additional initial schema differing from the first initial schema and corresponding to the first data domain.

13. The system of claim 12 , further comprising instructions that, when executed by the at least one processor, cause the system to determine that the additional initial schema is inconsistent with the first production schema specific to the first data domain.

14. The system of claim 13 , further comprising instructions that, when executed by the at least one processor, cause the system to transform the additional metric to conform to the first production schema specific to the first data domain.

15. The system of claim 11 , further comprising instructions that, when executed by the at least one processor, cause the system to generate an owner role, a writer role, and a reader role for the first initial schema.

16. A non-transitory computer readable medium comprising instructions that, when executed by at least one processor, cause a computing device to:

receive a first metric having a first initial schema and corresponding to a first data domain;

receive a second metric having a second initial schema and corresponding to a second data domain;

determine that the first initial schema is inconsistent with a first production schema specific to the first data domain;

determine that the second initial schema is inconsistent with a second production schema specific to the second data domain, wherein the second production schema is different from the first production schema;

transform the first metric to conform to the first production schema specific to the first data domain;

transform the second metric to conform to the second production schema specific to the second data domain; and

store, in a standardized-schema database, the first metric having the first production schema and the second metric having the second production schema.

17. The non-transitory computer readable medium of claim 16 , further comprising instructions that, when executed by the at least one processor, cause the computing device to receive the first metric by retrieving the first metric from an ingestion database, a staging database, or a data-domain-specific database.

18. The non-transitory computer readable medium of claim 16 , further comprising instructions that, when executed by the at least one processor, cause the computing device to utilize executable instructions in a test schema to generate the first metric.

19. The non-transitory computer readable medium of claim 16 , further comprising instructions that, when executed by the at least one processor, cause the computing device to verify that the first metric follows the first production schema before storing the first metric in the standardized-schema database.

20. The non-transitory computer readable medium of claim 16 , further comprising instructions that, when executed by the at least one processor, cause the computing device to store, in the standardized-schema database, an additional metric having an additional production schema specific to an additional data domain.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded Apr 1, 2025
From: FIRST-CITIZENS BANK & TRUST COMPANY, AS ADMINISTRATIVE AGENT
To: CHIME FINANCIAL, INC.
Reel/Frame 070695/0013 →
SECURITY AGREEMENT Recorded Mar 31, 2025
From: CHIME FINANCIAL, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 070689/0813 →
SECURITY INTEREST Recorded Jun 6, 2023
From: CHIME FINANCIAL, INC.
To: FIRST-CITIZENS BANK & TRUST COMPANY, AS ADMINISTRATIVE AGENT
Reel/Frame 063877/0204 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2023
From: DAMBE, KARISHMA; MANANNYKOV, DMYTRO; SHAH, SAIYAD
To: CHIME FINANCIAL, INC.
Reel/Frame 062757/0729 →
Continuity (1)
Related Publication 20240281451A1 · Aug 22, 2024