dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

As usual, I am probably going to go totally off topic.

I think this is a very good point and raises other similar issues
regarding data elements which should not be aggregated over time. We
have one data element which is "Current ART count" which represents
the total number of people on ART at any given month. It does not make
any sense to aggregate this number across time. The operator which
should be used for this aggregate should be "LATEST" rather than "SUM"
or "AVERAGE".

I am thinking that the concept paper on categories should really be
more about dimensions and aggregation paths. In this case, we have an
indication that some data elements should not be aggregated in space,
or if they are aggregated, they are subject to particular rules. In
the example I provided with "Current ART count",it is desirable to
aggregate with "SUM" in the space dimension, but not in the time
dimension.

Perhaps these are just "exceptions" to the rule, but does point to a
weakness in the aggregation engine, and its assumption that things
should always be aggregated in time and space, which is not always the
case with some data.

Yeah, not very helpful, but I could not help myself.

Regards,
JPP


On 12/8/10, Shinichi Suzuki <shin461@xxxxxxxxx> wrote:
> Dear Thuy Nguyen, and others,
>
> I am not sure this is suitable for this DHIS2 or not.
>
> In the distribution system, there are no hierarchy such as National,
> District, Facility. Because they may have some stocks and shipped  and
> received. They are all same level for the distribution system. Them, it
> consider the aggregation as a different statistical-organization hierarchy.
> So, we have to consider the separate hierarchy on this discussion.
>
> Sorry disturbing but I hope this help you,
>      Shinichi Suzuki
>
> From: dhis2-devs-bounces+shin461=gmail.com@xxxxxxxxxxxxxxxxxxx
> [mailto:dhis2-devs-bounces+shin461=gmail.com@xxxxxxxxxxxxxxxxxxx] On Behalf
> Of Thuy Nguyen
> Sent: Wednesday, December 08, 2010 6:29 AM
> To: johansa@xxxxxxxxxx
> Cc: Sundeep Sahay; Ola Hodne Titlestad; dhis2-devs
> Subject: Re: [Dhis2-devs] DHIS and logistics management (Was: Re: New
> requirement from Sri Lanka)
>
> Dear Johan,
>
> Here also I'm not 100% sure, but if you go to edit data element, you will
> find the Aggregation Level check box, which if checked will produce a
> drop-down list of all the levels you can aggregate data from. From the
> manual:
>
> "Aggregation levels: The Aggregation Levels option allows the data element
> to be aggregated at one or more
> levels. When the user clicks on the Aggregation levels option, a drop down
> menu appears which displays available
> aggregation levels. The desired aggregation level is then selected by
> clicking the 'Add Selected' button. By default,
> the aggregation will start at the lowest assigned organisation unit."
>
> I'm not sure if this adequately explains the funcionality. Others would
> need to help here, but I *think* this is working by setting the levels
> that will use "it's own" data rather than aggregate from below. Default
> only the lowest level is selected, and all higher levels will use data
> from that level. For example, if you have three levels; Facility,
> District, National, the last two levels will by default aggregate the data
> from Facility. If you select District as aggregation level, queries on
> Facility will use Facility data, District will use District Data, and
> National will aggregate District data. So in the Sri Lanka case, you can
> have one data element that you can use for all levels, just set it to have
> all aggregation levels. But not 100% sure about this, so good if someone
> can confirm. Also not sure aggregation level is the best name, I vaguely
> remember some discussion about this.
>
>
> Thanks a lot for explanation about this aggregate. So one problem may solve
> is each org unit level will see their own data. But there is another
> problem.
>
> Example
> Hierarchy of org unit are like this: National, District, Subdistrict
> National level want to see 2 types of report
> - Their own data
> - Total District level data values(without aggregated with the data values
> at national level)
>
> Example National N will enter their data values is N'
> Districts will enter their data values as : District 1 enter D1, District 2
> enter D2
> in District 1 have many SubDistricts, these SubDistrict enter data values as
> : SubDistrict 1 enter S1, SubDistrict  enter S2, SubDistrict 3 enter S3
>
> Then the National level want to generate
> - 1st report with data values is N'
> - 2nd report with datavalues is D1+D2
>
> The district org unit want to generate
> - 1st report with datavalues is D1
> - 2nd report with data of its subdistrict : S1+S2+S3
>
> Note : N' not equal D1+D2, D1 not equal to S1+S2+S3 because each org unit
> level has their stocks, so total of received items is not equal to total
> issued items, coz they always sure that the items must be available in the
> stock more than the min limitation.
>
> >From above requirements, if we keep entering from bottom to top org unit
> levels by only one data element. The aggregated level attribute in data
> element can be set at national level, so that every org unit level can
> generate the 1st report. But how to generate the 2nd reports?
>
> Thuy
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190