title: Datavault - hard rules (rawvault) vs soft rules (businessvault)
body: <p>I have a question on hard rules (rawvault) and soft rules (businessrules).</p>
  
  <p>The example I have is a source system has a denormalized table called Pets where Pets contain Cats, Dogs, and Birds where they are distinguished by a Type Code (1 – cat, 2 – dog, 3 – birds). </p>
  
  <p>My question is regarding hard rules vs soft rules when loading the data into the Rawvault vs business vault.  When loading the Pets table, can you create a h_cat, h_dog, and h_bird hub in the rawvault and filter the source table pets base on the Type Code of 1 into h_cat, type code 2 into h_dog and type code 3 into h_bird?   Is this a hard rule or a soft rule? </p>
  
  <p>Or</p>
  
  <p>Should we be creating a h_pet hub in the rawvault keeping the data as close to the source as possible creating the h_cat, h_dog, and h_bird in the businessvault when filter the data based on type code because this would be classified as a soft rule?</p>