Thanks a lot, Jason. I'll consider filing a blueprint for this. Regards,
Robin From: Jason Pickering [mailto:jason.p.picker...@gmail.com] Sent: 10 September 2014 17:55 To: Robin Martens Cc: Lars Helge Øverland; dhis2-users@lists.launchpad.net; dhis2-devs Subject: Re: [Dhis2-devs] DHIS2 - Indicator calculation over dimensions Hi Robin, It has been a discussed, and certainly not a bug. See a related thread here (https://lists.launchpad.net/dhis2-devs/msg27571.html) for a similar discussion on validation rules. It is essentially the same as indicators. What you will have to do is to create seperate indicator for each and every combination which you need. It can be painful, but the only way really which I know at the moment. Feel free to file a blueprint here. https://blueprints.launchpad.net/dhis2 Regards, Jason On Wed, Sep 10, 2014 at 5:37 PM, Robin Martens <mart...@sher.be<mailto:mart...@sher.be>> wrote: Dear all, I've been testing the indicator calculation algorithm and noticed something particular of which I'm not sure if it's a bug or a deliberate development choice. Indicators are not explicitly defined per category such as data elements but the reporting tools allow a disaggregated indicator calculation, which is definitely very useful. In a specific example, I want to know how many people were vaccinated this year and I have 3 kinds of vaccinations: A, B, and C. I have two data elements: the total population and the national vaccination levels (in %), with a custom category "vaccination type" which can be A, B, or C. My indicator would be "total population" x "national vaccination level (total)". That works fine when put in a pivot table. However, when trying to disaggregate the indicator calculation by adding my custom category to the pivot table, I don't have any values anymore. It seems the reason is that the "total population" data element does not have the "vaccination type" category (which seems logical) and therefore isn't found by the calculation algorithm. As a result, my table is empty. It seems useful that the algorithm would take the aggregated value (for population) available in such cases. Another example is over the period dimension: my population is a yearly value, so when calculating an indicator on a monthly basis, instead of taking the available yearly value, he takes zero. So my question: is this a deliberate choice in the development, a bug, or an idea for a future system improvement? Kind regards, Robin _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-d...@lists.launchpad.net<mailto:dhis2-d...@lists.launchpad.net> Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp -- Jason P. Pickering email: jason.p.picker...@gmail.com<mailto:jason.p.picker...@gmail.com> tel:+46764147049
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : dhis2-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
