dhis2-devs team mailing list archive

[Trí Trần Thanh <tranthanhtri84@xxxxxxxxx>]

Hi .

I think dataset lock is use for the use like manager of system and completed
dataset is use for normal user. The normal user will use dataset completed
for confirm "our data was completed to  the manage user" and the manage user
can use this data and believe this data value is valid. If after 2,3 or 4
month,etc the user can change data, data will wrong. That why we need data
set locking.

This is the way we use for Vietnam. it just is my idea. If you don't then
leave it.






================================
Tran Thanh Tri
 HISP Viet Nam
 Cell phone: +84903670967
 Website: http://tringuyenvn.com
================================


2009/12/9 Lars Helge Øverland <larshelge@xxxxxxxxx>

>
>
> On Wed, Dec 9, 2009 at 9:20 AM, Ola Hodne Titlestad <olatitle@xxxxxxxxx>wrote:
>
>> Tri,
>>
>> If that is what you need in Vietnam, and I am sure you know that best,
>> then we need to support it.
>>
>> But that doesn't mean the rest of the world want it the same way, that was
>> my point. The way data is audited and who sets a dataset to completed or
>> locked varies from country to country. Such differences in use are best
>> modelled through optional system settings I think, that gives each country
>> or state the flexibility to choose the behaviour of the system that they
>> prefer.
>>
>> Ola Hodne Titlestad |Technical Officer|
>> Health Metrics Network (HMN) | World Health Organization
>> Avenue Appia 20 |1211 Geneva 27, Switzerland | Email: titlestado@xxxxxxx|Tel:
>> +41 788216897
>> Website: www.healthmetricsnetwork.org
>>
>> Better Information. Better Decisions. Better Health.
>>
>>
> I agree with Ola at this. We do have a data locking functionality (which is
> a little slow at the time though) which could take care of this. I think we
> should not mix data locking and completeness. Sorry Tri but I will revert
> this. Could you instead have a look at the data locking functionality and
> maybe improve that?
>
>
> Lars
>