Thanks, Ola. That's very helpful to know what to consider when structuring this. I'm using UN population data which up to now they've made aggregate nicely. I have dropped categories that overlap figuring I can calculate them later (e.g. children 0-14 years). So I think it should be okay.
Tom ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Ola Hodne Titlestad Sent: 02 May 2012 16:16 To: Lars Helge Øverland Cc: Hiatt, Mr Tom (WPRO); [email protected] Subject: Re: [Dhis2-users] [Dhis2-devs] DHIS version 2.8 released Hi Tom, If I understand you correctly you have a data element called "Population" and a categorycombination with Age+Sex linked to this data element? If so, you should make sure that the total of the category option combinations (All ages and sex combinations) add up to the total population. The total for the data element is used in many places in DHIS 2 and if this total is not the correct total population you might confuse the users and also make indicator and report creation more complicated than it has to be. Typically the age groups for population is overlapping and not complete sets (e.g. <1, <5, female 15-49 (WRA), total), that is why I ask. If you have a complete set of disaggregated population data then categories will work fine. If not, I would use separate data elements for the different population groups. 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 1 May 2012 14:20, Lars Helge Øverland <[email protected]<mailto:[email protected]>> wrote: On Tue, May 1, 2012 at 2:15 PM, Hiatt, Mr Tom (WPRO) <[email protected]<mailto:[email protected]>> wrote: Ah yes, of course. Thanks! For me, I have individual codes for these data elements (population by age and sex), but previously I had them stored as individual variables rather than dimensions of the population variable. This time around I'm trying to store them in the "right" way as dimensions, which seems more logical. (I hope I don't get bit down the road for this...) For my use so far, this is a one-off data import exercise, but I could imagine scenarios where one would like to import more frequently from a database that stores them as individual variables as mine did. However, seeing as how these data would probably come from different systems that use different coding schemes, perhaps a mapping exercise would be necessary anyway. I'll let you know if I run into that hurdle. Tom Great. Let us know how it goes. _______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected]<mailto:[email protected]> Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp ==================================================== This message was scanned for viruses with Trend Micro ScanMail, GFI MailSecurity and GFI MailEssentials by the World Health Organization Regional Office for the Western Pacific. However, the recipient is advised to scan this e-mail and any attached files for viruses. Disclaimer: This e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may not copy or disclose its contents to anyone.
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
