Changes between Version 6 and Version 7 of BluePrintRegionsAndIncidents

Timestamp:

02/16/11 14:49:21 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintRegionsAndIncidents

@@ -32 +32 @@
 
 In order to support configuring and selecting regions:
+
  * Move any region-specific configuration into gis_config.  This currently means:
   * A location representing a region (see below).
@@ -46 +47 @@
   * Already present in gis_config, and needed for region selection:
    * Map center and zoom (so map can be positioned appropriately for the region).
+
  * Generate a regions menu from the gis_config table. Add site config options to enable
    the regions menu and specify a label for the menu head.
+
  * The selected region persists for the session only (or until the user selects another
    or clears the selection).
@@ -55 +58 @@
    * The user's personal gis_config.
    * The generic gis_config.
+
  * Filter entities that have locations by region.
   * Filter drop-down menus and other selectors.
@@ -65 +69 @@
 The "region location" associates specific locations to the region.
 There are four main ways a region location can specify this association:
+
  * The region location can be in the hierarchy, and specific locations can have
    the region location as an ancestor. (E.g. the region might be a city.)
@@ -84 +89 @@
 
 An incident involves:
+
  * Personnel
   * Teams