Changes between Version 2 and Version 3 of BluePrint/Event

11/06/14 03:33:24 (7 years ago)
Michael Howden



  • BluePrint/Event

    v2 v3  
    2525== Use-Cases ==
     26* Deployments/DERA
    27 == Design ==
     28== Designs ==
     30=== !SituationReport (!SitRep) Aggregation ===
     32We currently have a very basic !SitRep module in Eden where we can write a Rich Text report &/or add a file attachment.
     34There are cases where the !SitReps for different Districts should be aggregated at the next higher level (e.g. Province or Division).
     36For 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
     38!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.
     40==== Data Model ====
     41I would suggest a Key-Value system in a new table:
     42* {{{doc_sitrep_tag}}}
     44This would be like the ones for {{{gis_location}}} (amongst others):
     46Note how these are added to the parent resource as a [wiki:S3/S3Model/ComponentResources Component]:
     49This model should be added to the !SitRep class (I don't think we need a separate class here):
     52==== UI ====
     53For 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)
     55Inline form:
     56* (Can add KV like Files)
     59* (Need to add an rheader like this to !SitReps)
     62I have provided an initial UI for the aggregation:
     64i.e. there is a hook for a new 'consolidate' method which is called with the selected sitreps.
     66The {{{consolidate}}} method needs writing. It would look something like this:
     69==== XSLT Import ====
     70XSLT should be provided to import the Tags:
     71* [Example of a KV in an XSLT file]
     72* [File which needs modifying]
    2974== Implementation ==