Changes between Version 2 and Version 3 of BluePrintRegionsAndIncidents


Ignore:
Timestamp:
02/16/11 13:51:07 (11 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintRegionsAndIncidents

    v2 v3  
    3232This is open for ideas -- please add suggestions here.
    3333
     34An incident involves:
     35 * Personnel
     36  * Teams
     37  * Projects / work assignments
     38 * Material resources
     39  * Vehicles assigned
     40  * Inventory allocated
     41 * Associated entities
     42  * Hospitals
     43  * Shelters
     44  * Other orgs involved
     45  * Assessments
     46 * Information (e.g. work logs, instructions)
     47
    3448Fran considered creating an org for each incident, as it has fields and components that would be appropriate, but says that may not be sufficient.
     49
     50Many types of things are associated with an incident.  The "relational" way to do this, without adding fields to entities, is to add relationship tables that associate an incident with each of the types.  That is, there would be an "incident assessments" table that says which assessments go with which incident, and so-on for the other associated types.  This allows overlap.  When an entity is no longer needed for an incident, it's relationship can be deleted or "expired" by setting an end date.  (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.)