Hi Bob, The simple answer is to select the levels you have raw data for as your aggregation level.
Aggregation levels refer to the "source" level for upwards aggregation. If you enter data for both facilities and districts you select those two levels as your aggregation levels. Then district and all levels above will use district level data in (the first available aggregation level in a "current level" to bottom level search) and not go below that level. Facility, and any levels between facility and district level, will use the facility data. Guess we need to update the manual then if it is that confusing. Ola ----- ---------------------------------- Ola Hodne Titlestad (Mr) HISP Department of Informatics University of Oslo Mobile: +47 48069736 Home address: Vetlandsvn. 95B, 0685 Oslo, Norway. Googlemaps link<http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Vetlandsvn.+95B,+0685+Oslo,+Norway> On 14 March 2012 15:25, Bob Jolliffe <[email protected]> wrote: > I have an issue regarding dataelements which are entered at both > health centre and district hospital level. In order to see the actual > data at district hospital I have set the aggregation level for this > dataelement to the levels above district hospital. Is this a correct > interpretation of the manual. Doesn't seem to be working for me ie. > the district hospital is still showing the aggregate value of the > health centres. > > Using 2.7 stable. > > Any ideas? > > Bob > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
