AtAGlance Indicators by Districts

[Ghislain Hachey]

A requirement born in FSM to disaggregate indicators by states.

After discussion between Ghislain and Brian it was agreed to quickest path to ticking this ToR item is to have a first implementation of this done simply building on the current VERMPAF xml architecture.

[Brian Lewis]

Moving parts:

1) verm data - this is the xml file containing the the data. We can dig specific values out of this using 'xpath' In some cases, we get an indicator by finding 2 values in the vermdata and creating a ratio. XML

2) Pineapples - this is a service that provides the AtAglance API. Basically for each indicator, it constructs the XPAth into the vermdata to get the required value. If it needs a ratio or sum, it will do that. JAVASCRIPT

3) AtAGlance - this is an object, not a service or controller. This object holds precalculated indicator values. The prupose is so that we do not do the expensive vermdata loookups on each digest cycle. i.e. a 'facade' JAVASCRIPT

4) AtaGlanceMgr - service, this contructs the AtAGlance object required by the particular page. JAVASCRIPT

5) AtAGlanceController - Controller user interaction with the Page, TYPESCRIPT

Routing and Templates

There are specific templates by Education Level (note these are also overridable in the usual 'context' method for localisation) Routes are created by a function, which sets up the route parameters, including the template path ()

[Ghislain Hachey]

Complete