The ETL
tool is integrated into the application suite where metadata can be used and reused within the
environment. In the process of mapping, the application will identify, define, and store the
metadata information for each field that is being mapped. The application will also capture
the transformation rules that must be applied as data moves from one application to another.
For example, the gender code of system A may utilize numeric representations which need
to be converted to alphanumeric codes of ???M??? and ???F???. The transformation rule would be
something along the lines:
Figure 2. Structured and unstructured information
0 Stephens
Copyright ?© 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission
of Idea Group Inc. is prohibited.
???If Source-Gendor = 1 then Move ???M??? to the Target-Gendor Else Move ???F???.
This type of information has an enormous amount of reuse since once a system or database
is integrated; you do not need to repeat the work the next time. Once the source and target
definitions are captured, the definitions can be reused until the system owners modify the
underlying structures. The benefits of using this approach include the following:
??? Reduces build, support, maintenance, and troubleshooting overhead
??? Data Warehouse projects take less time to develop, and allows for an iterative development
style, reducing the risk of failure
??? Documentation and metadata is simplified as only one area needs to be documented
and managed
??? One processing environment reduces cost, leverages skills, and simplifies management
??? Integration occurs external to the operational applications
Organizations that have any size to them are going to have an enormous amount of data
within the legacy applications, operational data stores, CRM systems, and enterprise resource
planning (ERP) systems.
Pages:
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149