Changes

The IMSMA staging area is a '''flattened''' and '''read-only''' version of the {{TOC rightIMSMANG}}operational database. In terms of content, the data is an exact copy of the '''approved''' information in the {{IMSMANG}} database, but the structure is less complex and therefore easier to query.

==What's the IMSMA Staging Area?==The IMSMA staging area is a ''flattened'' version of the IMSMA operational database. In terms of content, the data is an exact copy of the IMSMA database, but the structure is much less complex and therefore easier to query. While in the operational IMSMA {{IMSMANG}} database the core object item data (e.g. the ID , status and name of a Land) is stored in one table (e.g. in and other information about the HAZARD table) and descriptive attributes Land (such as single- and multi-select standard and custom defined fields) are stored in separate tables, . Furthermore in the {{IMSMANG}} information are also stored with enumeration values and as links between objects. In the staging area all this information is available flattened in one single tablefor each item. Therefore, there is no lesser need to write complex queries to get to the core information. Ultimately, reporting and data analysis tools can easily be connected to the staging arearetrieve attributes of an object.

==Structure of the IMSMA Staging Area=====Flattening principles===The generation of the A staging area follows the following principles, for all the tables:* Standard text, numeric, can be created out of an {{IMSMANG}} v 6.0 (and any single-select attribute values (known as '''imsmaenum'''higher) are stored directly in the main table** Example:* CDF text, numeric, and any single-select attribute values are stored directly in the main tabledatabase.** Example:* Standard multi-select attribute values are directly stored in the main table It is typically used as a comma-separated list '''andreporting database''' in a normalised way in the standard multi-select table associated to the object.** Example:* CDF multi-select attribute values are directly stored in the main table , via [[MINT]] or any other [[Other Reporting Tools|reporting/analysis tool]] such as a comma-separated list '''and''' in a normalised way in the CDF multi-select table associated to the object.** Example:* The guid, localid and name of the location an object is linked to are directly stored in the main object table.** Example:* The guid, localid and name of an organization linked to an object are directly stored in the main object table.** Example:* 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. For example, the country structure can have up to seven levelsExcel or ArcGIS. Therefore, in a main object table like HAZARD, there will the following columns: gazetteer_level1_localid, gazetteer_level1_name, gazetteer_level2_localid, gazetteer_level2_name, ..., gazetteer_level7_localid, gazetteer_level7_name. If in IMSMA only four levels are defined, then the columns for levels five to seven will always be empty.** Example: ===Main object tables=== ===Other tables=== ===Geographical data=== ===Database diagrams=== ==The IMSMA Staging Area Generator==