Notifications
Clear all

Redefining Satellite column definitions?


Posts: 3
Topic starter
(@bruce-kirk)
New Member
Joined: 2 months ago

How do you handle cases where a business definition changes in the future.

 

Example:

SAT_Stuff.ABC is defined as A + B on the source application as of today.

A month later the business redefines

SAT_Stuff.ABC is redefined as A + B + C on the source application or as part of the soft rules for the business vault layer.

 

If it is defined as part of the Data Vault Soft Rules then should this become a new / separate column on the Satellite or should the new definition be mapped to the existing definition?

If we remap the existing column, how do you manage the metadata changing for the present and future being different than the metadata definition for the previous data (Historic values).

Regards

Reply
1 Reply