dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Prosper,

you are right. Since data entry works offline we need to use the client
clock for the data entry periods. However we can do

- a check on the client side comparing server time to client computer time
and ask the user to update if not in sync.

- a check on the server when saving data using the data set(s) of the data
elements and look for restrictions for future data. If the data set is
locked for future periods we can deny saving of data.

Blueprint here:
https://blueprints.launchpad.net/dhis2/+spec/future-data-check

We can put it in for 2.18.

Lars




On Mon, Dec 1, 2014 at 11:34 AM, Prosper BT <ptb3000@xxxxxxxxx> wrote:

> Dear Developers,
>
> I have always known that this problem exists, but when it begins messing
> up data analytics then we need to worry and look out for a permanent
> solution to this problem.
>
> What is happening is that for say monthly reporting, if an enduser sets
> his date in the future, he can enter future data and when you do analytics
> that data will be missed out  for a particular past month.
>
> Shouldn't the system be restricting periods as picked from the central
> server? but having suggested that we also worry about offline entry unless
> we are able to sync periods together with Orgunits and Data sets?
>
> Regards
>
> --
> Prosper Behumbiize, MPH
> Phone:        +256 414 320076
> Cell:             +256 772 139037
>                      +256 752 751776
>
>
> _______________________________________________
> 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
>
>