Changes between Version 81 and Version 82 of Event/GHC2014


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

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/GHC2014

    v81 v82  
    9494For 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
    9595
    96 !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.
     96!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.
    9797
    98 So, we need a way to store these in the !SitRep. I would suggest a Key-Value system in a new table:
     98==== Data Model ====
     99I would suggest a Key-Value system in a new table:
    99100* {{{doc_sitrep_tag}}}
    100101
     
    107108* https://github.com/flavour/eden/blob/master/modules/s3db/doc.py#L664
    108109
    109 
     110==== UI ====
    110111For 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)
    111112
     
    124125* https://github.com/flavour/eden/blob/master/modules/s3db/hrm.py#L3995
    125126
    126 
    127 Ideally XSLT would be provided to import the Tags:
     127==== XSLT Import ====
     128XSLT should be provided to import the Tags:
    128129* https://github.com/flavour/eden/blob/master/static/formats/s3csv/event/event.xsl [Example of a KV in an XSLT file]
    129130* https://github.com/flavour/eden/blob/master/static/formats/s3csv/doc/sitrep.xsl [File which needs modifying]