wiki:BluePrint/Event

Version 4 (modified by Fran Boon, 7 years ago) ( diff )

--

BluePrint: Event Modules

Introduction

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

Description

Related BluePrints

Requirements

  • Assign resources ( Staff, Volunteers, Assets, Vechicles) to an Event or Incident
  • Set up projects, activities, tasks for an Event/Incident
  • Record costs involved with an Event/Incident
    • Distributed Inventory Items
    • Volunteer/Staff/Asset Hours
  • Filter information by Event/Incident
  • Navigate by Events - ability to have a top level menu of specific events
  • Event Dashboard

Use-Cases

  • Deployments/DERA

Designs

SituationReport (SitRep) Aggregation

We currently have a very basic SitRep module in Eden where we can write a Rich Text report &/or add a file attachment.

There are cases where the SitReps for different Districts should be aggregated at the next higher level (e.g. Province or Division).

For the Rich-Text, I see this as creating a section for each District with a Section Header added and all the Heading levels taken down a notch: H1s -> H2s, etc

SitReps can also include hard numbers though, like #affected, #dead, #wounded, #missing, #displaced, # staff, #volunteers, # vehicles, #shelters, etc then obviously these should be totalled in the aggregated report, so, we need a way to store these in the SitRep.

Data Model

I would suggest a Key-Value system in a new table:

  • doc_sitrep_tag

This would be like the ones for gis_location (amongst others):

Note how these are added to the parent resource as a Component:

This model should be added to the SitRep class (I don't think we need a separate class here):

UI

For UI, this could be a Tab, as it is for gis_location, or could be an Inline form. I think the Inline form is better, generally better UX & works better for when the sitrep is itself on a tab (e.g. of the Event or Org)

Inline form:

Tabs:

I have provided an initial UI for the aggregation:

i.e. there is a hook for a new 'consolidate' method which is called with the selected sitreps.

The consolidate method needs writing. It would look something like this:

XSLT Import

XSLT should be provided to import the Tags:

Implementation

  • modules/s3db/event.py
  • modules/s3db/irs.py (to be merged with modules/s3db/event.py)

References


BluePrints

Note: See TracWiki for help on using the wiki.