dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #30338
Re: "Atomic" data validation rules
Sounds good to me as well and think it will be very useful.
Another feature we should probably think about as well, is extending this
type of thing to indicators. We have forms where we need these validation
rules, but also it would be neat to have indicators be also able to be
defined by the pattern of the common category combos. As an example,
consider below:
Number of people who tested HIV negative (by Male/Female + Age groups)
+
Number of people who tested HIV positive (by Male/Female + Age groups)
+
Number of people who tested HIV indeterminate (by Male/Female + Age groups)
=
Number of people of people tested for HIV (by Male/Female + Age groups)
The indicator/calculated data element (Number of people of people tested
for HIV) would then "inherit" all of the category combo options of the
component parts. Right now, we would need to define many separate
indicators for these calculated totals, which is a bit clunky.
Regards,
Jason
On Sun, May 25, 2014 at 9:47 PM, Jim Grace <jimgrace@xxxxxxxxx> wrote:
> I also like the simpler option better (surprise).
>>
>
> WITYWS.
>
>
>> If the default option clearly states that there is no change then we are
>> not forcing the users who do not need this feature to even understand it.
>>
>
> Good. I think this will be a neat feature. The only challenges will be the
> users understanding it. Will give my best shot a the the UI and the
> documentation to facilitate this. ;)
>
>
>
References