-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle 3 disaggregations (4 including location) #72
Comments
LGTM |
Summarize upwards = totals in a disaggregation to roll up at a higher level. We want the application to support a likert scale indicator type. Do we want to support it at any disaggregated level.... from IP reporting side, answer is no, cluster side GBB, but no example available. Likert will be supported but only disaggregated by location. Latest report is taken per location. Cannot calculate across locations...... one opinion was to average, would assume each location has equal representation, but comparing a large province analysis might be not appropriate. Percentage, Ratio and rate behavior is somewhat similar, except for the parameters in which you'd want to constrain reporting around. Since weighting is not captured no disaggregation (like likert) be allowed for percentage. Eg. "Recovery rate in malnutrition centers". If just a # then # of children treated then we won't have percentage, since we don't have # that are. For "recovery rate" for example we'd need # children successfully treated and # admitted. 1 idea: Split into 2 indicators: one numerator and one denominator? Rather than asking people to fill in 2 things. The open question then is do we have way to setup a calculated indicator. Decision: for percentage capture numerator and denominator. From a math perspective likert, %, ratio and rate are same, with numerator and denominator, but units etc. might be different. Yes/no indicator: Questions:
|
Cleaned up draft API response below:
|
…ted list of IndicatorReport ids [#72]
+ Sort the Disaggregation choice array of arrays
…ported_on fields to IndicatorLocationData [#72] + factory and generate_fake_data update
+ disaggregation as cached_property + disaggregation_values as instance method
…cef/etools-partner-reporting-portal into feature-multiple-disaggregations-#72
…cef/etools-partner-reporting-portal into feature-multiple-disaggregations-#72
Updated API response to final version on Issue body. |
…uery parameter pks [#72] + Added safeguard for parsing comma-separated id list
…cef/etools-partner-reporting-portal into feature-multiple-disaggregations-#72
@n1207n extra comma can be problematic? "(1754,)": { |
+ Added flat kwarg for disaggregation_values in IndicatorReport object to return a flattened list of DisaggregationValue ids + Added validate method for SimpleIndicatorLocationDataListSerializer + Validation method to check tuple key number count against the level_reported + Validation method to IndicatorReport id lookup + Validation method to check tuple key lookup against DisaggregationValue ids from database
…-disaggregations-#35 # Conflicts: # polymer/src/elements/ip-reporting/indicator-details.html
…cef/etools-partner-reporting-portal into feature-multiple-disaggregations-#72
Feature multiple disaggregations (API and viewing) #72
PUT request work will be continued and be finalized in #35 issue. |
Currently we are designing for 3 disaggregations (4 including locations).
Entering data when 3 disaggregations mockup: https://projects.invisionapp.com/share/RDBE0T04F#/screens/230016139
We've mapped out in colors the data here (per level in JSON below): https://www.evernote.com/l/AAUnyhUkhr5GY4_LNUMwp9BJJGwSJQcYbLA
Showing four cases (0, 1, 2, 3 disaggregations): https://docs.google.com/spreadsheets/d/14lbalO2NlNdxDk03ShXy19TAZjXBESYZglHmENW3nDI/edit#gid=0
Open issues:
The text was updated successfully, but these errors were encountered: