I believe with clear guideline on when the data is to be locked is of paramount. Data locking should be uniform so as to make right decision and not having data changing over time. In Kenya we are planning to lock data after one month to give room for any missing reports, correction or update.
On Wed, Apr 20, 2011 at 11:21 AM, Hieu Dang Duy firstname.lastname@example.org wrote:
Junk Score: 2 out of 10 (below your Auto Allow threshold) | Approve sender | Block sender | Block domain
Hi Indian folks,
How are you all ?
As we know that, there is a locking data set functionality in Data Administration menu in DHIS2 now. This one is very good one and running stable. But do you feel that this functionality which is quite inconvenience and uncomfortable in using. Because of the reason is that how do we know which data set has been locked for which organization unit belongs to the respective period or not.
So, basically on this issue, I have developed a new clone for this functionality. We called it Data Set Grid Locking. It would be able to an another view-point for this func. Please take a look at the attached pics belong to this mail to get more details. And feel free for your all comments about this. And if you think this new one is useful for your situation then I will send to the patch file to Lars for applying. But at least after releasing version 2.2
Thanks for all your free-time while reading this mail.
Good health !
Mailing list: https://launchpad.net/~dhis2-devs
Post to : email@example.com
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Ministry Of Health
P.O. Box 20781
Don’t Compromise The Quality! Don’t Risk It! apply Available Standards to Achieve Your/organizational Goal.