Data Warehousing Community Forum
March 21, 2019, 08:01:58 am

Pages: [1]   Go Down
Author Topic: DW Conceptual/Logical Modeling Dilemma  (Read 495 times)
DW Fresher

Reputation: +0/-0
Offline Offline

Posts: 1

View Profile
« on: September 21, 2018, 11:12:48 pm »

I have been struggling to develop a logical data warehousing model for a government agency tasked with integrating and making discoverable hundreds of years worth of disparate records both in electronic and to-be digitized paper records in substantially disparate formats.

My dilemma is thus:

Should i design the logical datawarehouse entity model based on the:

1. legally-mandated perspective of these records, which essentially buckets these record data according to the agency's departments that are responsible for managing their records? For example, accounting department records would belong to its own distinct entity groups apart from human resources department records--so i would define an entity called "Accounting" and all accounting dept records fit in there.  Pretty typical....

2. or, model these entities according to a "product-centric" model? By that i mean that entities in the model each represent a specific tangible "product" that the agency provides to the general public or some other customer. The caveat is: each "product" is composed of bits & pieces of attributes queried from other department's data. To take our previous example, a product (such as a 1000-page research report) from the accounting department could be composed of  50% accounting data attributes and 50% queried from human resources data attributes.

The reason I would really prefer, if feasible, to consider modeling option #2 is built on the notion that the agency could better measure the value of its existence based on how well it provides its "products" to the public--and not on how well it is remaining compliant to how a law dictates how it stores its records (modeling option #1).

I would really love to hear your opinions on this.
Pages: [1]   Go Up
Jump to: