TRANSFORMING DATA METRICS TO MAINTAIN COMPATIBILITY IN AN ENTERPRISE DATA WAREHOUSE
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.
1 . A computer-implemented method comprising:
associating a first data access level with a first production schema specific to a first data domain;
associating a second data access level with a second production schema specific to a second data domain, wherein the first data access level is different from the second data access level;
transforming a first metric having a first initial schema to conform to the first production schema specific to the first data domain based on determining that the first initial schema is inconsistent with the first production schema;
storing, in a database, the first metric having the first production schema;
receiving a first access request for the first metric; and
responding to the first access request for the first metric based on the first data access level associated with the first production schema.
2 . The computer-implemented method of claim 1 , further comprising determining to approve the first access request based on a role of a user account corresponding to the first access request being granted access within the first data access level associated with the first production schema.
3 . The computer-implemented method of claim 1 , further comprising determining to approve the first access request based on an access type of the first access request being permitted within the first data access level associated with the first production schema.
4 . The computer-implemented method of claim 1 , further comprising determining to approve the first access request based on both an access type of the first access request being permitted, and a role of a user account corresponding to the first access request being granted, within the first data access level associated with the first production schema.
5 . The computer-implemented method of claim 1 , further comprising:
receiving a second access request for a second metric that conforms to the second production schema; and
responding to the second access request for the second metric based on the second data access level associated with the second production schema.
6 . The computer-implemented method of claim 1 , further comprising determining to approve the first access request based on a data domain associated with the first access request being included in the first data access level associated with the first production schema.
7 . The computer-implemented method of claim 6 , further comprising determining to approve the first access request based on a user account belonging to a team of user accounts included in the first data access level associated with the first production schema.
8 . 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:
associate a first data access level with a first production schema specific to a first data domain;
associate a second data access level with a second production schema specific to a second data domain, wherein the first data access level is different from the second data access level;
transform a first metric having a first initial schema to conform to the first production schema specific to the first data domain based on determining that the first initial schema is inconsistent with the first production schema;
store, in a database, the first metric having the first production schema;
receive a first access request for the first metric; and
respond to the first access request for the first metric based on the first data access level associated with the first production schema.
9 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine to deny the first access request based on a role of a user account corresponding to the first access request not being defined within the first data access level associated with the first production schema.
10 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine to deny the first access request based on an access type of the first access request being restricted within the first data access level associated with the first production schema.
11 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine to deny the first access request based on one of an access type of the first access request being restricted, or a role of a user account corresponding to the first access request not being defined, within the first data access level associated with the first production schema.
12 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to
receive a second access request for a second metric that conforms to the second production schema; and
respond to the second access request for the second metric based on the second data access level associated with the second production schema.
13 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine to deny the first access request based on a data domain associated with the first access request not being included in the first data access level associated with the first production schema.
14 . The system of claim 8 , further comprising instructions that, when executed by the at least one processor, cause the system to determine to approve the first access request based on a user account belonging to a team of user accounts included in the first data access level associated with the first production schema.
15 . A non-transitory computer readable medium comprising instructions that, when executed by at least one processor, cause a computing device to:
associate a first data access level with a first production schema specific to a first data domain;
associate a second data access level with a second production schema specific to a second data domain, wherein the first data access level is different from the second data access level;
transform a first metric having a first initial schema to conform to the first production schema specific to the first data domain based on determining that the first initial schema is inconsistent with the first production schema;
store, in a database, the first metric having the first production schema;
receive a first access request for the first metric; and
respond to the first access request for the first metric based on the first data access level associated with the first production schema.
16 . The non-transitory computer readable medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine to deny the first access request based on a role of a user account corresponding to the first access request not being defined within the first data access level associated with the first production schema.
17 . The non-transitory computer readable medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine to deny the first access request based on an access type of the first access request being restricted within the first data access level associated with the first production schema.
18 . The non-transitory computer readable medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to approve the first access request based an access type of the first access request being permitted, and a role of a user account corresponding to the first access request being defined, within the first data access level associated with the first production schema.
19 . The non-transitory computer readable medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
receive a second access request for a second metric that conforms to the second production schema; and
respond to the second access request for the second metric based on the second data access level associated with the second production schema.
20 . The non-transitory computer readable medium of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computing device to determine to approve the first access request based on a user account belonging to a team and the team being included in the first data access level associated with the first production schema.