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?
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.
On Mon, Dec 1, 2014 at 11:34 AM, Prosper BT ptb3000@gmail.com 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?
For now we have to call on all enduser involved in data entry to ensure that their systems dates are correct.
Was able to quickly notice this because one of my dashboard shows reporting rates for last month, and today I see some reporting rates percentage for last month which ended last night and analytics only run in the night. Since we only run analytics at night, there was no way this could have happened. When I drilled to see the facility found some had entered data on November 10, 2014.
Regards
···
On Mon, Dec 1, 2014 at 2:32 PM, Lars Helge Øverland larshelge@gmail.com wrote:
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.
On Mon, Dec 1, 2014 at 11:34 AM, Prosper BT ptb3000@gmail.com 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?
For now we have to call on all enduser involved in data entry to ensure that their systems dates are correct.
Was able to quickly notice this because one of my dashboard shows reporting rates for last month, and today I see some reporting rates percentage for last month which ended last night and analytics only run in the night. Since we only run analytics at night, there was no way this could have happened. When I drilled to see the facility found some had entered data on November 10, 2014.
Regards
On Mon, Dec 1, 2014 at 2:32 PM, Lars Helge Øverland larshelge@gmail.com wrote:
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.
On Mon, Dec 1, 2014 at 11:34 AM, Prosper BT ptb3000@gmail.com 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?