Difference between revisions of "Other tables"
From IMSMA Wiki
| Line 30: | Line 30: | ||
::* tbltask | ::* tbltask | ||
::* tbltaskconnection | ::* tbltaskconnection | ||
| − | <li> system tables. | + | <li> system tables |
| + | <li> inactive tables | ||
| + | ::* hazreducversion_involvedorg | ||
| + | ::* mrecontactversion. | ||
</ol> | </ol> | ||
Latest revision as of 07:00, 14 January 2019
Other tables may be divided in groups of:
- 1:M tables for cdfvalues e.g. hazard_has_cdfvalue
- 1:M tables for geospatial data e.g. hazard_has_geospatialinfo
- 1:M tables for multi-select data e.g. hazard_has_imsmaenum
- 1:M tables for creating Summary window data e.g. hazardinfoversion which has their own 1:M for cdfvalues, geospatial data and multi-selct data
- tables used for Impact scoring
- template
- templatefactor
- templatefactorweight
- templatescenario
- templatescoringrange
- link table
- Data Inventory Manager tables
- migration tables that were used as temporary storage when data is migrated from Legacy
- contact
- imsma3x_fieldreport_xref
- imsma3x_location_xref
- map
- mrecontactversion
- socioeconomicinfo
- tblapplicationmac
- tbldailyrecord
- tbllessonlearned
- tblmineriskeducationactivitycontact
- tblorganisationcontact
- tblpersonnelmac
- tblplacecontact
- tblsketch
- tbltask
- tbltaskconnection
- system tables
- inactive tables
- hazreducversion_involvedorg
- mrecontactversion.
These tables are not described in the Data Dictionary because some are general and other for data security reasons. Contact your GICHD IM advisor if you have questions about these tables.
