| | 195 | |
| | 196 | == Proposal (keith) == |
| | 197 | |
| | 198 | To define "Incident Category" isn't an easy work. |
| | 199 | The Candian ems.incident seems too detail for a large disaster management system. |
| | 200 | e.g. It should be "Transport/Railway" instead of "Railway/Hijacking" |
| | 201 | We might start from small to define our own incident categories to increasing |
| | 202 | user experience without missing the flexibility and accuracy. |
| | 203 | |
| | 204 | The way to category is using preemptive way "number range": |
| | 205 | {{{ |
| | 206 | irs_incident_type_opts = { |
| | 207 | 1:T("Natural Disaster"), |
| | 208 | 2:T("Transport"), |
| | 209 | 3:T("Collapse, Illness, Injury, Trapped"), |
| | 210 | 4:T("Industrial"), |
| | 211 | } |
| | 212 | |
| | 213 | irs_incident_subtype_opts = { |
| | 214 | 100:(1, T("Flood")), |
| | 215 | 101:(1, T("Landslide")), |
| | 216 | 200:(2, T("Roads Brodken")), |
| | 217 | 201:(2, T("Bridges Broken ")), |
| | 218 | 300:(3, T("Buildings Collapsed")), |
| | 219 | 301:(3, T("People Trapped")), |
| | 220 | 400:(4, T("Power Failures")), |
| | 221 | } |
| | 222 | }}} |
| | 223 | So ID 1~99 are major categories. ID 100~199 are under 1st Category "Nature Disaster". |
| | 224 | 200~299 are under "Transport". |
| | 225 | |
| | 226 | If someone gonna create a new category, he *should* have a look at |
| | 227 | "THE NATIONAL STANDARD FOR INCIDENT RECORDING" |
| | 228 | http://rds.homeoffice.gov.uk/rds/pdfs08/countnsir08.pdf |
| | 229 | |
| | 230 | TODO: |
| | 231 | There should be "Please refer to the link of 'Make a request' for the need of helps" |
| | 232 | in the page before creating a incident report. |
| | 233 | |
| | 234 | It is what I can think of now to get most benefit for current usage and fine for future development. |
| | 235 | |
| | 236 | For now the code will only show the sub categories. |
| | 237 | |
| | 238 | [[Image(Screen shot 2010-08-25 at 1.42.50 AM.png)]] |
| | 239 | |
| | 240 | If it's ok, the diff code is on http://bazaar.launchpad.net/~keitheis/sahana-eden/edentrunk/revision/1073 |
| | 241 | |
| | 242 | If we had much more time and the amount of categories went out of control, we can try the top-down way of selecting gis location. |
| | 243 | (I've tried and find it needs much more effort to make it work.) |
| | 244 | |
| | 245 | |