dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olatitle@xxxxxxxxx>]

2009/10/29 Lars Helge Øverland <larshelge@xxxxxxxxx>

>
>
> On Thu, Oct 29, 2009 at 5:29 AM, Hieu Dang Duy <hieu.hispvietnam@xxxxxxxxx
> > wrote:
>
>> Dear Thuy,
>>
>> I think your bug will be fixed as soon as possible from someone's help on
>> it. Abyota, maybe.
>> Previously, it's a joking mail less down your stress. I always know that
>> "one bug is one responsibility". Perhaps, you are misunderstanding on my
>> first mail. But still apologize if you dislike.
>>
>> Thanks
>>
>>
>
> Actually this behavior is intended. The reason is that categoryoptioncombos
> are being pre-populated, which happens when a categorycombo is being
> created. Categoryoptions being part of a category which is being part of a
> categorycombo cannot be changed, since that will mess up the pre-populated
> catoptcombos. I have did it this way to make it simple. We might improve it
> later.
>
> Lars
>
>
Hi Lars,

Not sure I understand 100% how this works, but during production (when data
is being registered in the system) I understand it can be quite meesy to
make changes to categories/options/combos, but in a pre-production phase
where you don't have any data and are experimenting with the categories and
options would it be possible to at least delete the generated
categoryoptioncombos and recreate these with a new set of options without
having to delete the exisiting categories and options? It is hard to get it
right the first time so it can be quite cumbersome if changes cannot be made
without having to redo the whole thing.

And for production... at some point we will have to provide some better
functionality for making changes to exisiting dimensions (the ones that
actually influence data values like orgunit, period, data element and
categoryoptioncombos), because most countries make such changes every year,
and it can be quite dificult (and dangerous) to do this manually. Sierra
Leone is phasing such a problem right now with huge changes to their
datasets for next year. You need to keep the exisiting data somehow linked
to the new structure for historical comparisons, so starting with a new
clean database is not really an option. E.g. tools for merging or splitting
data values would be desired.

Ola
-------------


> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> More help   : https://help.launchpad.net/ListHelp
>
>