dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

best regards,
Ola Hodne Titlestad
HISP
University of Oslo


2009/4/18 Lars Helge Øverland <larshelge@xxxxxxxxx>

>
>
> 2009/4/18 Murodullo Latifov <murodlatifov@xxxxxxxxx>
>
>> Hi,
>>
>> i see your point in that this would be easy and it would probably work.
>> But it sounds a little static to me. Wouldn't we want to have some
>> pre-defined and re-usable comments?
>>
>> Also, we definitely should have this for regular and multidimensional data
>> entry as well. I guess it is needed and otherwise we are making things
>> inconsistent...
>>
>> Hi,
>>
>> regular and multidimentional data entry is already inconsistent with
>> custom data entry. If custom data entry has dataset consisting two different
>> set of dataelement comboid combinations it will show only the first
>> dataelement comboid combination, not the rest.
>>
>
> I guess you mean two different set of dataelement category combo. You
> cannot have more than one category combo for data elements in a
> multidimensional data entry form (unless you use the sections but I have
> never seen that work). Anyway I don't see why this is an argument to make
> things even more inconsistent. This thing will also be used for the survey
> functionality we are planning to make.
>
>
>
>> Maybe my installation does not this.
>> Comments for my opinion should not be predefined, user should have freedom
>> to fill in what he wants to comment. what if his desire is not listed on
>> predefined options?
>>
>
>
> Sorry, I didn't mean predefined in terms of hard-coded. Poor wording on my
> side. I meant that we should have a GUI where we enter and persist comments,
> and then re-use these for all forms.
>
> I am little unsure of what you mean here. Do you mean the user should type
> in the options directly when he designs the form?
>
> I do agree that we could embed the options in the html form for cde. This
> sounds like a good idea. But we could still have user-defined, persisted
> options attached to a data element - data set combo. This would then be
> automated for the multidimensional data entry form.
>
>
>
> _______________________________________________
> 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
>
>
Just a quick comment.

The option list for data element+dataset combo will in the future also most
likely be needed in other use cases in addition to data entry so there is a
need to persist these in the model.

E.g. if you want to define some aggregation (e.g. from case based to routine
data) or validation, triggers etc. you will need to have these options
available when defining the rules, E.g.
if data element "Diagnosis" = 'Malaria' then .. do_something_. Filling such
rules without having the possible options available is error-prone and
tedious work.

Ola
----------