dhis2-devs team mailing list archive

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

I am not sure how this is going to work really. What is going to
happen to data values that  when a category option is removed? Will
they too be removed?

I would think the better design would be able to add new category
options, but have an option for which ones are actually active in the
data entry form at a given point in time. This may be adding some
complexity, but it does not seem really entirely desirable to delete
data if the category options simply change.



2009/10/29 Lars Helge Øverland <larshelge@xxxxxxxxx>:
>
>
> 2009/10/29 Thuy Nguyen <thuy.hispvietnam@xxxxxxxxx>
>>
>> Example when the data values are already entered.
>> And later there is some changings in category options. So I will have to
>> create new category with completely new category options which are not the
>> old ones. Will those data values be there?
>>
>> And when I create new category, with new category options. By mistake I
>> click Create button while I haven't finished add all category options yet.
>> And I have to delete category and start the process again to add more
>> category options
>>
>> And this is also happen in ICD report. In the district level, this reports
>> included more than 300 data elements and category combo with 8 categories
>> option, in province level, this report has more category options added. In
>> the old version. I could add more category options without creating new
>> category combination and again assign each data element to new category
>> combination.
>>
>> May be you have other way to solve this problem but I haven't study it
>> yet. I will look at it and know what this can do.
>>
>>
>> 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
>>>
>
>
> Yes I will include add/remove in edit category as soon as I have implemented
> appropriate deletion handlers for this.
>
> Managing data when data elements are changed/edited is another issue which
> we will face regardless of using plain dataelements or categories. The good
> news is that after the model change catoptcombos are now uniquely identified
> by its set of categoryoptions, which will make such a process easier.
> Remember that we in any case can rename existing category options and
> categories.
>
> _______________________________________________
> 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
>
>