Transforming data
2 posters
Page 1 of 1
Transforming data
Hi,
I have a question related to transformation is DW. In our system (Property Management) we buy, sell and let properties. In that we have a dimension called unit which is nothing but a subset of a property. For e.g. we have a property and that property has several floors, so a floor can be treated as unit. When the unit is deactivated the Area of that unit is automatically removed from the whole property but sometimes the unit is not actually deactivated but named as "deactivated" which will be actually deactivated at later point. But when we are reporting, users don't want to show the area and income of this particular unit. Generally data input users do zero out area and income when they name unit as "deactivated" but sometimes they forget. So is this something which I should be taking care when doing transformation in DW i.e changing area to 0 even if there is an area for the unit named as "deactivated"?
Please do let me know if the question is unclear.
Many Thanks,
Kanishka.
I have a question related to transformation is DW. In our system (Property Management) we buy, sell and let properties. In that we have a dimension called unit which is nothing but a subset of a property. For e.g. we have a property and that property has several floors, so a floor can be treated as unit. When the unit is deactivated the Area of that unit is automatically removed from the whole property but sometimes the unit is not actually deactivated but named as "deactivated" which will be actually deactivated at later point. But when we are reporting, users don't want to show the area and income of this particular unit. Generally data input users do zero out area and income when they name unit as "deactivated" but sometimes they forget. So is this something which I should be taking care when doing transformation in DW i.e changing area to 0 even if there is an area for the unit named as "deactivated"?
Please do let me know if the question is unclear.
Many Thanks,
Kanishka.
Kbheir- Posts : 2
Join date : 2011-09-09
Re: Transforming data
Generally it is best to correct any issues with the data in the source system, but that is not always possible. It is perfectly acceptable to correct this issue when loading the data warehouse.
cjrinpdx- Posts : 51
Join date : 2011-07-14
Location : Portland, OR
Many thanks for your reply cjrinpdx
cjrinpdx wrote:Generally it is best to correct any issues with the data in the source system, but that is not always possible. It is perfectly acceptable to correct this issue when loading the data warehouse.
Kbheir- Posts : 2
Join date : 2011-09-09

» Looking for a Data Architect/Data Modeler for NYC Big Data Startup
» difference between data mart and data warehouse at logical/physical level
» clickstream fact data coming in with different levels of dimensional geography data
» Data warehouse / data retention strategy - ERP upgrade and consolidation
» Reporting table data repository vs. Dimensional data store
» difference between data mart and data warehouse at logical/physical level
» clickstream fact data coming in with different levels of dimensional geography data
» Data warehouse / data retention strategy - ERP upgrade and consolidation
» Reporting table data repository vs. Dimensional data store
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum