Abstract: A system for data comparison is disclosed. The system may receive a source configuration metadata. The system may configure a data extraction module to extract data from a data set in response to the source configuration metadata. The system may generate a pre-work data from the data set. The system may compare the pre-work data to generate a post-process data set. The system may generate a report corresponding to the post-process data set.

Abstract: A system for data comparison is disclosed. The system may receive a source configuration metadata. The system may configure a data extraction module to extract data from a data set in response to the source configuration metadata. The system may generate a pre-work data from the data set. The system may compare the pre-work data to generate a post-process data set. The system may generate a report corresponding to the post-process data set.

Abstract: The system may validate a data source having a structured format and a grammar that includes tags. The system may identify a tag in the grammar. The system may parse the data source to extract attributes and/or values associated with the tags in response to successful validation. The system may also write the attributes and/or values to an output file separated by a preselected delimiter. A configuration file may identify the grammar, the preselected delimiter, and/or the data source. The data source may be in an XML format or a JSON format. The system may generate execution ready code in response to the validating the data source and the grammar. The output file may be a load ready file for ingestion into a big data storage format. The tag may include a parent tag and a sub tag corresponding to a hierarchy in the data source.

Abstract: A system receives a source and a metadata layer that describes the source. The source may comprise source records with fields containing source data, and the metadata layer may include metadata comprising at least one of a field data type, a field data length, a field description, or a record length. The processor may further validate the metadata layer against the source and write results to a log. The processor may further be configured for transforming the source records into transformed records for a load ready file. The processor may further balance a number of records in the source against a number of transformed records in the load ready file to generate a transformation failure rate.

Abstract: The system may validate a data source having a structured format and a grammar that includes tags. The system may identify a tag in the grammar. The system may parse the data source to extract attributes and/or values associated with the tags in response to successful validation. The system may also write the attributes and/or values to an output file separated by a preselected delimiter. A configuration file may identify the grammar, the preselected delimiter, and/or the data source. The data source may be in an XML format or a JSON format. The system may generate execution ready code in response to the validating the data source and the grammar. The output file may be a load ready file for ingestion into a big data storage format. The tag may include a parent tag and a sub tag corresponding to a hierarchy in the data source.

Abstract: A system receives a source and a metadata layer that describes the source. The source may comprise source records with fields containing source data, and the metadata layer may include metadata comprising at least one of a field data type, a field data length, a field description, or a record length. The processor may further validate the metadata layer against the source and write results to a log. The processor may further be configured for transforming the source records into transformed records for a load ready file. The processor may further balance a number of records in the source against a number of transformed records in the load ready file to generate a transformation failure rate.