Changes between Version 76 and Version 77 of Event/GHC2014


Ignore:
Timestamp:
10/07/14 10:10:24 (7 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/GHC2014

    v76 v77  
    8888=== !SituationReport (!SitRep) Aggregation ===
    8989
    90 We currently have a very basic !SitRep module in Eden where we can write a RichText 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).
     90We 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).
    9191
    9292For 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
     
    9494SitReps 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.
    9595
    96 So, we need a way to store these in the SitRep: I would suggest a KeyValue system: doc_sitrep_tag.
     96So, we need a way to store these in the !SitRep: I would suggest a Key-Value system: doc_sitrep_tag.
    9797
    9898This would be like the ones for gis_location (amongst others): https://github.com/flavour/eden/blob/master/modules/s3db/gis.py#L1254
    9999Note how these are added to the parent resource as a 'Component': https://github.com/flavour/eden/blob/master/modules/s3db/gis.py#L386
    100100
    101 This model should be added to the SitRep class (I don't think we need a separate class here): https://github.com/flavour/eden/blob/master/modules/s3db/doc.py#L664
     101This model should be added to the !SitRep class (I don't think we need a separate class here): https://github.com/flavour/eden/blob/master/modules/s3db/doc.py#L664
    102102
    103103For 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)
    104104Inline form: https://github.com/flavour/eden/blob/master/modules/s3db/doc.py#L715 (Can add KV like Files)
    105105
    106 Tabs: https://github.com/flavour/eden/blob/master/modules/s3db/gis.py#L5427 (Need to add an rheader like this to SitReps)
     106Tabs: https://github.com/flavour/eden/blob/master/modules/s3db/gis.py#L5427 (Need to add an rheader like this to !SitReps)
    107107
    108108Ideally XSLT would be provided to import the Tags: https://github.com/flavour/eden/blob/master/static/formats/s3csv/event/event.xsl