Metadata

Our experts develop ‘contextual metadata’.

Several metadata elements associated with the ETL process are valuable to the data warehouse or user application and must be provided to the end users.

• Data Lineage – a logical data mapping, illustrates transformations applied to a data element between its original data source and its ultimate data output. 
• Business Definitions – Every table created in the ETL process stems from a business definition. Although these definitions can be captured during the ETL process, they will be carried forward to the data warehouse or application for which the end user intends to use them.
• Technical Definitions – Technical definitions describe the physical attributes of data elements, including the structure, format, and location. Properly document technical metadata for all ETL tables to minimize ambiguity and ensure usability.
• Process Information – Processes that load ETL tables must record their statistics along with table loads. A measure of data freshness is useful both for ETL administrators and end users.

This service is delivered by an ETL specialist teams with assistance from IT and key business users who are well familiar with the data sources and the business rules. The ETL products and processes are configured to deliver the most appropriate data from sources to target DW/DM environments. ETL rules are stored in a single repository as per the best practices or following client practices for consistency of definition and ease of maintenance.

Compliance Requirements

The Data Services must plan for the compliance requirements placed on it by outside sources. Statutory rules and regulations, standards and guidelines must be taken in consideration during the planning stage, as how ETL will transfer data. The ETL process itself must account for the compliance requirements so that the data transferred is as usable as possible.