Changes between Version 10 and Version 11 of BluePrintRegionsAndIncidents


Ignore:
Timestamp:
02/16/11 17:18:55 (11 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintRegionsAndIncidents

    v10 v11  
    2424The definition of a region or incident should be shared among (appropriate) users.  That is, a site admin should be able to configure a region or incident.
    2525
    26 And incident will probably need a region as part of its specification.
     26An incident will probably need a region as part of its specification.
    2727
    2828=== Region proposal ===
     
    104104  * Vehicles assigned
    105105  * Inventory allocated
    106  * Associated entities
     106 * Associated entities (Are these simply tagged as being part of this Incident & we filter by default to the already-tagged ones, but can also remove this filter if we want to find a resource from the wider pool)
    107107  * Hospitals
    108108  * Shelters
     
    112112
    113113==== Use an org ====
    114 Fran considered creating an org for each incident, as it has fields and components that would be appropriate, but says that may not be sufficient. Probably need at least a region in addition.
     114Fran considered creating an org for each incident, as it covers the command hierarchy for the staffing, but says that may not be sufficient. Probably need at least a region in addition.
    115115
    116116==== Use relationship tables ====
     
    118118
    119119(If a "paper trail" is needed, i.e. a record of what was used for each incident, there are several ways of providing that.  One is to add start and end dates to the relationship.  Since those could clutter the table, one could dump / pickle historical data, or move them to a parallel set of "expired" relationship tables.  Keeping it online would be more convenient for preparing reports.  Simplest is to leave them in the main incident relationship tables but set their end dates.)
     120
     121----
     122BluePrints