dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olatitle@xxxxxxxxx>]

Yusuph created a blueprint here:
https://blueprints.launchpad.net/dhis2/+spec/data-movement

-which I have now updated with the text from this discussion.

Ola

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.


2009/11/26 Lars Helge Øverland <larshelge@xxxxxxxxx>

>
>
> 2009/11/26 Ola Hodne Titlestad <olatitle@xxxxxxxxx>
>
> Hi,
>>
>> I am not sure this should go into the dataadmin module if that is what you
>> are thinking Lars.
>>
>> I understand your reasoning I guess, but the most common use case is a
>> data entry clerk e.g. at a district that is filling in forms for 15 clinics
>> every month and makes a mistake like selecting the wrong clinic or month and
>> needs to change back without first deleting and then filling all the data
>> again. I assume that this user does not have access to the data admin module
>> at all and that this functionality should be offered in the data entry UI in
>> a restricted manner based on which orgunints the user can manage, and which
>> data sets these orgunits are assigned to.
>>
>> Another less common use case that I can see now is more of a data cleaning
>> exercise done by an administrator where this user has found that data for
>> one or more months have been registered for the wrong orgunit, or for the
>> wrong year and then needs to move these to the correct orgunit or month.
>>
>> If possible I would suggest that we offer this functionality from both
>> modules, with the data admin being a bit more advanced with batch features
>> where collections of form instances can be moved around. I suggest we start
>> with the simple case in data entry where one specific form instance, the one
>> the user has opened, can be moved to a different orgunit and/or period given
>> that this new instance does not already have data in it.
>>
>> What do you think?
>>
>> Ola
>> -----------
>>
>
>
> That's fine with me.
>