dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Including Calle(can someone please check that I got his address
right,I'm on my cell and not able to load it from gmail) here as I am
sure he has given this much thought in the past.
What do you think of this Calle?
Ola

2009/5/2, Johan Ivar Sæbø <johansa@xxxxxxxxxx>:
> While it might not be necessary to use a prefix, it is GOOD PRACTICE. For
> one not living in the databasee world, I usually encounter the OU names in
> reports, or pivot tables. In a pivot table, filtering a pivot field is
> hopeless with duplicates instead of prefixes...
>
> Suppose you want to list a few facilities, and that the district they are in
> contain other facilities you don't want to see. This is quite a common
> situation. Then you would have to filter the "facility" field, which will
> show ALL facilities, thus your list might look like this (also quite
> typical, in for instance Sierra Leone)
>
> ...
> Red Cross Clinic
> Red Cross Clinic
> Red Cross Clinic
> ...
>
> instead of
> ...
> BO Red Cross Clinic
> BM Red Cross Clinic
> WA Red Cross Clinic
> ...
>
> Just my five cents.. If you're making a H1N1 A (well, I will still call it
> swine flu) database covering the whole world, maybe a postfix would be
> better, if it turns out to be a long string...also easier for sorting
> Johan
>
>
> Jason Pickering wrote:
>>
>> Hi Ola,
>>
>> I am sitting here with Knut, and I am going to support him on this
>> one. :) The actual "real" relationship should be as Knut states. There
>> are many Pickens Counties in the USA, but only one in Georgia (my home
>> town).
>>
>> The prefix method has been implemented in Zambia, but I would regard
>> this as very messy as well, particularly since it does not actually
>> reflect the actual name of the orgunit. I would really regard this
>> more of a kludge than anything else. In the reports that I have
>> created in Zambia, we have trimmed out the two characters, as they
>> make the reports messy.
>>
>>
>>
>>
>>>
>>> Orgunit hierarchy is not referenced from the data values so the
>>> proposed change would easily cause problems when dealing with the data.
>>>
>>>
>>
>> What does this mean? Every value is referenced to an orgunitid ?
>>
>> In my opinion, we should try and model the actual physical world.
>> Generally, there are never duplicates of an orgunit within a
>> particular parent. There are Oslo's in both Norway and Peru, but they
>> are unique within their own hierarchy. The constraint should be that
>> for any given parentid, the names of orgunits should be unique. I am
>> not sure why this will result in a messy database, but at the present,
>> the database and its constraints simply do not reflect reality.
>>
>> Regards,
>> Jason
>>
>> _______________________________________________
>> 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
>> >From - Sat
>>
>
>
>


-- 
best regards,
Ola Hodne Titlestad
HISP
University of Oslo