===Flattening principles===__NOEDITSECTION__
{{Note | This section requires basic knowledge of the {{IMSMANG}} structure}}
The generation of {| class="wikitable" width="1000"|-| align="center" colspan="3" | '''Where to find which data in the staging area follows the following principles, for all the tables:'''|-| width="150pt" | '''Type of attribute''' | width="250pt" | '''Where?'''| width="600pt" | '''Example'''|-* | align="left" | '''Standard text, numeric, date and any time attributes''' | align="left" | Stored directly in the main object table, similar to {{IMSMANG}}| align="left" | The HAZARD (Land) attribute hazard_localid is stored in a column also called hazard_localid in the HAZARD table of the staging area.|-| align="left" | '''Standard single-select selects''' | align="left" | Stored directly in the main object table (whereas in {{IMSMANG}} the main object table only contains a GUID reference to the IMSMAENUM table)| align="left" | The HAZARD (Land) attribute status is stored in a column called status_enum in the HAZARD table of the staging area. It contains the '''translated value''' of the status base value, e.g. ''Open'' or ''Closed'' in English or the equivalent values (known as in another language that has been specified at staging area generation.|-| align="left" | '''imsmaenumStandard multi selects''') are stored | align="left" | Stored directly in the main object tableas '''comma-separated list of values''' '''AND''' in a normalized way in the <OBJECT>_STD_MULTISELECT table (in {{IMSMANG}} the values for a multi select have to be looked up in the <OBJECT>_HAS_IMSMAENUM and IMSMAENUM tables)| align="left" | some example|- ** Example:
* CDF text, numeric, and any single-select attribute values are stored directly in the main table.
** Example:
