Changes

{{TOC right}}{{Under construction | This page is under construction}}==What is the IMSMA Staging Area?==__NOEDITSECTION__The IMSMA staging area is a '''flattened''' and '''read-only''' version of the IMSMA {{IMSMANG}} operational database. In terms of content, the data is an exact copy of the IMSMA '''approved''' information in the {{IMSMANG}} database, but the structure is much less complex and therefore easier to query. While in the operational IMSMA database the core object data (e.g. the ID and name of a Land) is stored in one table (e.g. in the HAZARD table) and descriptive attributes (such as single- and multi-select standard and custom defined fields) are stored in separate tables, in the staging area all this information is available in one single table. Therefore, there is no need to write complex queries to get to all the attributes of an object. Ultimately, reporting and data analysis tools can easily be connected to the staging area.<br />A staging area can be created out of an {{IMSMANG}} v 6.0 (and higher) database. It is typically used as a '''reporting database''', via [[lightMINT]], [[MINT]] or any other [[External Reporting Tools|reporting/analysis tool]].

==Structure of the IMSMA Staging Area==__NOEDITSECTION__===Flattening principles===__NOEDITSECTION__{{Note | This section requires basic knowledge of the {{IMSMANG}} structure}} {| class="wikitable" width="1000"|-| align="center" colspan="3" | '''Where to find which data in the staging area'''|-| width="150pt" | '''Type of attribute''' | width="250pt" | '''Where?'''| width="600pt" | '''Example'''|-| align="left" | '''Standard text, numeric, date and time attributes''' | align="left" | Stored directly While in the main object table, similar to operational {{IMSMANG}}| align="left" | The HAZARD (Land) attribute hazard_localid is stored in a column also called hazard_localid in database the HAZARD table of the staging area.|-| align="left" | '''Standard single-selects''' | align="left" | Stored directly in the main object table item data (whereas in {{IMSMANG}} the main object table only contains a GUID reference to the IMSMAENUM table)| align="left" | The 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 in another language that has been specified at staging area generation.|-| align="left" | '''Standard multi-selects''' | align="left" | Stored directly in the main object table as '''comma-separated list ID, status and name 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" | The Land object has a multi-select attribute called ''Marking'' (Marking Method). In the staging area, the HAZARD table has an attribute marking_method with a comma-separated list of values, for example 'Official Signs, Local Signs'. Additionally, the table HAZARD_STD_MULTISELECT can be joined with the HAZARD table is stored in order to get to the same values as rows. Reusing the above example, there will be two rows, one with 'Official Signs' and one with 'Local Signs' as values (or the translated values if any translations are available).|-| align="left" | '''CDF text, numeric, date and time attributes and CDF single-selects''' | align="left" | Stored directly in the main object table (as opposed to {{IMSMANG}} where a lookup has to be made through the <OBJECT>_HAS_CDFVALUE, CDFVALUE and CUSTOMDEFINEDFIELD tables)| align="left" | Each CDF will be turned into a column in other information about the staging area. For example, a CDF called ''My Hazard CDF'' defined on Land will result in a column named my_hazard_cdf in the HAZARD table of the staging area. {{Note | Note that non-standard characters in CDF names, (such as blanks, are replaced by underscores in the column names}}|-| align="left" | '''CDF multi-selects''' | align="left" | Stored directly select and custom defined fields) are stored in the main object table as '''comma-separated list of values''' '''AND''' in a normalized way separate tables. Furthermore in the <OBJECT>_CDF_MULTISELECT table (in {{IMSMANG}} the information are also stored with enumeration values for a multi select have to be looked up in the <OBJECT>_HAS_CDFVALUE, CDFVALUE and CUSTOMDEFINEDFIELD tables)| align="left" | Let's assume that the Land object has a multi-select CDF attribute called ''My Land Multi-Select''as links between objects. In the staging area, all this will result information is flattened in a column in the HAZARD one single table called my_land_multi_select with a comma-separated list of values, for example 'Value1, Value2'each item. Additionally, the table HAZARD_CDF_MULTISELECT can be joined with the HAZARD table in order to get to the same values as rows. Reusing the above exampleTherefore, there will be two rows, one with 'Value1' and one with 'Value2' as values.|-| align="left" | '''Location data''' | align="left" | The guid, localid and name of the location an object is assigned to are directly stored in the main object table.| align="left" | The HAZARD table in the staging area has the columns location_guid, location_localid and location_name with the values of the location that each object is assigned lesser need to.|-| align="left" | '''Organisation data''' | align="left" | The guid, localid and name of the organisation linked write complex queries to an object are directly stored in the main object table.| align="left" | TODO|-| align="left" | '''Places data''' | align="left" | The guid, localid and name retrieve attributes of the place linked to an object are directly stored in the main object table.| align="left" | TODO|-| align="left" | '''Classification data (Country structure, Assistance Classification, Cause Classification and Needs Assessment Classification)''' | align="left" | The guid, localid and name of classifications (country structure (gazetteer), assistance classification, cause classification and needs assessment classification) associated to an object are directly stored in the main object table. Since a classification can have several levels, there is a placeholder for each level, up to the maximum number of levels.| align="left" | In the HAZARD table in the staging area, there are the following columns regarding the country structure classification (gazetteer): gazetteer_guid, gazetteer_level1_localid, gazetteer_level1_name, gazetteer_level2_localid, gazetteer_level2_name, ..., gazetteer_level7_localid, gazetteer_level7_name. There are seven placeholders because the country structure in {{IMSMANG}} can have up to seven levels.|-|} ===Database model===__NOEDITSECTION__A simplified staging area database model for the Land (Hazard) object is depicted below. For all the other main objects, the model looks very similar.[[Image:Staging_Area_Model_Hazard.png|center|800px]] ===Main object tables===__NOEDITSECTION__ ===Other tables===__NOEDITSECTION__{| class="wikitable" width="1000'"|-| width="150pt" | '''Table name''' | width="850pt" | '''Description'''|-|}===Views===__NOEDITSECTION__ ==Geographical data in the staging area==__NOEDITSECTION__

[[Category:VIENAA]]