Merge pull request #8 from RJNashleanas/master

Cleanup of image links

Author: RoelantVos

Data Integration Framework - Reference Solution Architecture - 1 - Overview.md

@@ -133,7 +133,7 @@ The Solution Pattern finally creates the actual code or ETL mapping and is there
 
 The following high level reference architecture depicts the three main layers:
 
-![1547521419126](.\Images\HighLevelSolutionOverview.png)
+![1547521419126](./Images/HighLevelSolutionOverview.png)
 
 The basic flow of data as specified in the reference architecture is:
 
@@ -170,7 +170,7 @@ For tables that store history the metadata includes the regular start and end da
 
 The reference architecture itself exists in a larger system of components and functionality. While these are considered out of scope for the data integration framework, it can be useful to mention this wider context.
 
-![1547521593410](.\Images\93410.png)
+![1547521593410](./Images/93410.png)
 
 This diagram shows the some of the key concepts that relate to the reference architecture.
 

Data Integration Framework - Reference Solution Architecture - 2 - Staging Layer.md

@@ -12,7 +12,7 @@ Every project or delivery has different constraints and opportunities, which is
 
 The position of the Staging Layer in the overall architecture is outlined in the following diagram.
 
- ![1547519184139](.\Images\Staging_Layer_1_Overview.png)                                               
+ ![1547519184139](./Images/Staging_Layer_1_Overview.png)
 
 Core requirements and principles
 
@@ -72,7 +72,7 @@ The reference architecture specifies that data from the source systems is loaded
 
 This approach is presented in the following diagram:
 
-![1547519184139](.\Images\Staging_Layer_2_Functionality.png)   
+![1547519184139](./Images/Staging_Layer_2_Functionality.png)
 
 In typical solution designs, the Staging Area ETL is contains the steps where the source data is actually copied into the Data Warehouse environment. Concepts such as Change Data Capture (CDC) are implemented for this purpose.  
 

Data Integration Framework - Reference Solution Architecture - 3 - Integration Layer.md

@@ -52,7 +52,7 @@ The Integration Layer (Integration Area and Interpretation Area) will be created
 
 As an example, this approach allows information related to the same customer or prospect to be delivered and integrated independently. It also supports ongoing linking of customer information to tie in various elements of information to the unique prospect or customer over time without losing flexibility; the logic for de-duplication can be changed and/or recalculated across historical information if required.
 
-![1547521558900](D:/Git_Repositories/Data_Integration_Framework/Images/558900.png)
+![1547521558900](./Images/558900.png)
 
 Objects in the Integration Layer are not accessible for end-users or Business Intelligence and analytics software. This is because for most scenarios information has not yet been prepared for consumption; only Data Warehouse logic is implemented.  There is an exception to this rule; for specific data mining or statistical analysis it is often preferable for analysts to access the raw / unprocessed data. This means this access can be granted for the Integration Layer which contains essentially raw, but indexed and time variant data in the right context (e.g. related to the correct business keys). This is an ideal structure for statistical analysis.