dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Olav,

we simply use the start date of a week and see which month it falls within.
This applies to all period types.

This has the consequence, which you point out, that for a month you the
system might include a week which is not currently finished, and hence
cannot have any data, making the completeness statistic funny.

There might be better ways of handling this, like not including periods in
aggregation periods which are not complete. On the other hand, a week must
contribute to a month in any case - it is also not that good to include
weeks which starts in a previous month.

Aggregating weeks to months is in any case dodgy business and I am not
aware of any standardized rules for this (please educate me if someone
knows better).

cheers

Lars







On Fri, Jul 19, 2013 at 2:30 PM, Olav Poppe <olav.poppe@xxxxxx> wrote:

> Hi,
> I have a question regarding how the monthly completeness figures for
> weekly datasets are counted. Some users have complained that even in months
> where all weekly reports are complete, the monthly figure is 85%.
>
> What are the criteria for the week to fall within a month for the "target"
> and "complete" respectively. For example, is week 31 (29 July to 4 Aug)
> counted as July or August? Is it the same for the "target" and "actual" in
> completeness (if not, that could explain how monthly completeness is not
> 100% when all individual weeks are complete)?
>
> Olav
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>