Hi Maheed I am sure you will get much more informed feedback on this question because I think its something many folk grapple with. Just a quick observation regarding implementation.
> I don't know if anybody have similar issues or requirements like this one. > > I think 2 thinks are missing here: > > 1- Cannot define the target value for a data element within the data > element itself. It should be defined using another data element > > 2- The target value are not time-bound. This means we cannot set > that the target value should be reached starting date X and ending date Y. > These two seem to be contradictory. Associating a target value with a data element sounds sensible enough except that it would then lose the sense of target time. So you need to use another dataelement. ( I am not sure whether that is in fact what you are saying with 1 or you are pointing out what is missing). Note the same time boundedness can also be true of space. It is possible that different countries, provinces, districts set different target values. Do you think it makes more sense to focus on target values for indicators than dataelements? (Oddly enough I imagine the measured value should be an indicator and the target value should be a dataelement because you'd want to enter these targets directly). So maybe what is missing is the ability to assign a target dataelement to an indicator definition. So an indicator can have (an optional) dataelement associated with it for its target values. Of course you can do this "manually" but, as you say, the reports become laborious. Having an explicit association might make it easier to design smart reports. Look forward to hear what other people's experience is.
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
