Changes between Version 21 and Version 22 of BluePrintIncidentReporting
- Timestamp:
- 09/26/10 00:45:27 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrintIncidentReporting
v21 v22 1 1 [[TOC]] 2 = Incident Reporting =3 Allow the p ublic to report Incidents, with associated locations on the map.2 = Blue Print - Incident Reporting = 3 Allow the people to report Incidents with structured data. 4 4 5 Optionally, provide the ability for admin to approve the Reports. 5 == Data Model == 6 6 7 == Usability Suggestions == 7 === Incident === 8 9 * Date 10 * Location 11 * Category 12 * Reporter 13 * Comments 14 15 Components: 16 * Status (Allocated depending on authorisation) 17 * Date 18 * Reporter 19 * Status (Verified, Resolved, False... ?) 20 * Impact 21 * Type (see below) 22 * Value 23 24 === Impact Type === 25 * Single field to allow customisable types of impacts to be defined: 26 * Number of People Affected 27 * Number of People Injured 28 * Number of People Deceased 29 * Number of Houses Destroyed 30 * Number of Houses Damaged 31 * Number of Cows Lost 32 * Restricted to Admin 33 * Defined in the Situation (Sit) Module 34 * Also used in [BluePrintAssessment Assessment] 35 36 == Workflows === 37 * Incident Reported 38 * This could use a hand crafted view whihc exposed a number of different impact types, and then separated these in a incident resouse with multiple impacts in the controller. 39 * Incident Status Update 40 * This could be done through custom buttons on the view using AJAX 41 * Review Incidents 42 * This could produce a list of incidents 43 * Multiple Incidents records refer to the same actual incident 44 * These incidents can all be linked to a single parent using BluePrintResourceLinking 45 * An incident can be used to initiate a assessment, request, task, etc 46 * A Status record is automatical created 47 * The new resource (assessment, request, task...) is linked (BluePrintResourceLinking) 48 * Incidents are displayed on maps with icons according to their category. 49 50 == Legacy Comments == 51 === Usability Suggestions === 8 52 [http://eden.sahanafoundation.org/attachment/wiki/BluePrintIncidentReporting/Usability%20Suggestion%20for%20IRS.2.doc Usability Suggestion for IRS.doc] 9 53 * All points for this document have been actioned, except: … … 12 56 [[Image(http://hsiaojan.pbworks.com/f/searchbutton.jpg)]] 13 57 14 == Replace irs_incident == 15 * With a 'parent' field so that ireports can be linked together but without needing an extra table. 16 * a 'Lead Incident' flag can be used to indicate the master record which is where most updates happen 17 (This is how Service Now manages Incidents) 18 19 == Simplified Categories == 58 === Simplified Categories === 20 59 * #508 21 60 22 === Status === 61 === Status ==== 23 62 * Complete as of r1143 24 63 … … 26 65 27 66 The back-end should NOT be easily customised as otherwise it is hard to share data between instances. 28 === Proposals===29 ==== Fran====67 ==== Proposals ==== 68 ===== Fran ===== 30 69 31 70 Change to something more like this (doesn't yet handle the mapping - needs work!): … … 46 85 A subclass of IS_IN_SET() is created to handle this data structure, providing access to full list to a role (default to 'Editor'), but the sub-set to normal users' dropdowns. 47 86 * Q: Should .represent also be modified for Display of records? 48 ==== nursix====87 ===== nursix ===== 49 88 50 89 a) keep the original dict, but change the values of the dict into tuples like: … … 74 113 }}} 75 114 76 ==== keith, marr====115 ===== keith, marr ===== 77 116 78 117 A config screen for admin/editor to map "simple category" to "canadian category". Assume that total number for simple category options is small and limited, say 6 for Taiwan's case. In IRS report adding screen, default menu using simple category, user can switch via radio-button to canadian category. … … 80 119 > Note that if the category code options differ from instance to instance then you cannot exchange the incident reports anymore - therefore I suggested to keep the original options dictionary keys, and just add a second "user-friendly" category title (nursix) 81 120 82 ==== keith====121 ===== keith ===== 83 122 84 123 To define "Incident Category" isn't an easy work.
