Changes between Version 81 and Version 82 of Event/GHC2014

Timestamp:

10/07/14 10:17:42 (10 years ago)

Author:

Fran Boon

Comment:

--

Event/GHC2014

@@ -94 +94 @@
 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.
+!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.
 
-So, we need a way to store these in the !SitRep. I would suggest a Key-Value system in a new table:
+==== Data Model ====
+I would suggest a Key-Value system in a new table:
 * {{{doc_sitrep_tag}}}
 
@@ -107 +108 @@
 * https://github.com/flavour/eden/blob/master/modules/s3db/doc.py#L664
 
-
+==== 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)
 
@@ -124 +125 @@
 * https://github.com/flavour/eden/blob/master/modules/s3db/hrm.py#L3995
 
-
-Ideally XSLT would be provided to import the Tags:
+==== XSLT Import ====
+XSLT should be provided to import the Tags:
 * https://github.com/flavour/eden/blob/master/static/formats/s3csv/event/event.xsl [Example of a KV in an XSLT file]
 * https://github.com/flavour/eden/blob/master/static/formats/s3csv/doc/sitrep.xsl [File which needs modifying]