| | 1 | = !BluePrint: Event Modules = |
| | 2 | [[TOC]] |
| | 3 | |
| | 4 | == Introduction == |
| | 5 | When Sahana Eden is used for Emergency Management an Event Module is important to be able to manage information by events. Events could either be real disasters, emergencies or trainings/simulations |
| | 6 | |
| | 7 | == Description == |
| | 8 | |
| | 9 | === Related !BluePrints === |
| | 10 | * BluePrintIncidentReporting - Within a single event there may be multiple incidents. |
| | 11 | * BluePrintScenario - Scenarios are used to specify what resources are required by specific types of events and incidents |
| | 12 | * BluePrintExerciseManagement - How events can be used for trainings and simulations |
| | 13 | * BluePrintRegionsAndIncidents |
| | 14 | |
| | 15 | == Requirements == |
| | 16 | * Assign resources ( Staff, Volunteers, Assets, Vechicles) to an Event/Incident |
| | 17 | * Set up projects, activities, tasks for an !Event/Incident |
| | 18 | * Record costs involved with an !Event/Incident |
| | 19 | * Distributed Inventory Items |
| | 20 | * !Volunteer/Staff/Asset Hours |
| | 21 | * Filter information by !Event/Incident |
| | 22 | * Navigate by Events - ability to have a top level menu of specific events |
| | 23 | * Event [BluePrint/UserInterface/Dashboard Dashboard] |
| | 24 | |
| | 25 | == Use-Cases == |
| | 26 | |
| | 27 | == Design == |
| | 28 | |
| | 29 | == Implementation == |
| | 30 | * modules/eden/event.py |
| | 31 | * modules/eden/irs.py (to be merged with modules/eden/event.py) |
| | 32 | |
| | 33 | == References == |
| | 34 | * Sahana Eden List [https://groups.google.com/forum/?fromgroups#!searchin/sahana-eden/event/sahana-eden/2msJ_wLu06k/hoHCPHG_PpAJ%5B1-25%5D IRS merging into Events module?] |
| | 35 | * Domain/EmergencyManagement/IncidentManagementSystems |
| | 36 | * Domain/EmergencyManagement/IncidentManagementSystems/IncidentCommandSystem(UnitedStates) |
| | 37 | |
| | 38 | ---- |
| | 39 | BluePrints |
