I think I agree with Lars as well. Our use case was we wanted to restrict values between 0 and 31, and not do it with a validation rule, to provide visual clues during data entry.
As an aside, one may also want to calculate these values and save them to the database. The current algorithm uses a standard deviation approach, which is problematic, in that in many cases the data which is typically observed does not follow a normal Gaussian distribution. Other statistical models often provide better estimates of the mix/max, but currently, cannot be calculated automatically by the system. If these values are calculated externally in some statistical package, they can be inserted back into the system (or even automated). Regards, Jason On Thu, Sep 19, 2013 at 6:25 PM, Juma Lungo <jlu...@yahoo.com> wrote: > I agree with Lars > > Lungo > > ------------------------------ > *From:* Lars Helge Øverland <larshe...@gmail.com> > *To:* Jason Pickering <jason.p.picker...@gmail.com> > *Cc:* dhis2-devs <dhis2-devs@lists.launchpad.net> > *Sent:* Thursday, September 19, 2013 2:43 PM > *Subject:* Re: [Dhis2-devs] Setting MinMax Values > > Hi Conrad, > > the min-max data element is per org unit and data element like you say, so > it applies to all current and future periods by definition. I don't know > your use-case... but in general one might want to think twice before > setting the same max value for all facilities, since they usually have very > different catchment population and hence natural variations in numbers. > > Lars > > > _______________________________________________ > 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 > > >
_______________________________________________ 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
