Skip to content

Commit 4b29292

Browse files
committed
Revert "Updating template"
This reverts commit d591b35.
1 parent e5cb05a commit 4b29292

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

2000_Solution_Patterns/Solution Pattern - Data Modelling - Presentation Layer.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@
33
## Purpose
44
<<<<<<< HEAD
55
This Implementation Pattern describes the data modelling conventions and architecture for the Presentation Layer.
6-
7-
##Structure
6+
Structure
87
In principle, there are two mechanisms towards preparing information for consumption in the Presentation Layer (created in the Presentation Layer database):
8+
<<<<<<< HEAD
99
* Direct view on top of the Integration Layer (virtual information mart). In by far the most scenarios the first option (direct view / virtual) option is preferred as the subsequent layers in the (BI) architecture are typically MOLAP or in-memory.
1010
=======
1111
This Solution Pattern describes the data modelling conventions and objects used to expose and/or load dimensions in the Presentation Layer.
@@ -28,6 +28,10 @@ In principle, there are two technical approaches / mechanisms to prepare informa
2828
>>>>>>> 83665a0b59440a7c43985df8305b15a4bf404985
2929
* Table / persistence / physical storage using a view to join and prepare the data in the format that matches the table (logic) and can be used to incrementally load the table.
3030

31+
=======
32+
Direct view on top of the Integration Layer (virtual information mart). In by far the most scenarios the first option (direct view / virtual) option is preferred as the subsequent layers in the (BI) architecture are typically MOLAP or in-memory.
33+
Table / persistence / physical storage using a view to join and prepare the data in the format that matches the table (logic) and can be used to incrementally load the table.
34+
>>>>>>> parent of d591b35... Updating template
3135
In both cases these Presentation Layer objects will require one or more views to decouple the Business Intelligence (BI) and Data Warehouse (DWH) environments. These decoupling views are also intended to apply the history perspective at attribute level; e.g. how every attribute is displayed in time (e.g. Type1, Type2, Type 6).
3236

3337
The following general guidelines have been defined for Presentation Layer development:

0 commit comments

Comments
 (0)