in DHIS1.4 there was a functionality where people can move data from one facility to another if they made a mistake, I think this is a useful tool to be added on the DHIS2. comments are welcome.
I remember it was discussed long time ago, not sure why it was never prioritised or implemented.
There are two specific features here if I remember correctly.
The ability to move all data in a form instance (orgunit+period+dataset) to a new orgunit
The ability to move all data in a form instance (orgunit+period+dataset) to a new period
This is very useful when the user has either filled the form for the wrong period or the wrong orgunit, which happens quite frequently.
and both these are available via the data entry module I think. Right Yusuph?
Whether it is allowed to move the data or not of course depends on the user privileges and whether the new orgunit is assigned to the dataset or not, same validation as for normal data entry I guess.
in DHIS1.4 there was a functionality where people can move data from one facility to another if they made a mistake, I think this is a useful tool to be added on the DHIS2. comments are welcome.
Everything is doable. Yusuph, this sounds like a nice task for you, why don’t you give it a try?
Lars
···
On Wed, Nov 25, 2009 at 9:43 AM, Ola Hodne Titlestad olatitle@gmail.com wrote:
Hi Yusuph,
I agree, that is a nice feature of DHIS 1.4.
I remember it was discussed long time ago, not sure why it was never prioritised or implemented.
There are two specific features here if I remember correctly.
The ability to move all data in a form instance (orgunit+period+dataset) to a new orgunit
The ability to move all data in a form instance (orgunit+period+dataset) to a new period
This is very useful when the user has either filled the form for the wrong period or the wrong orgunit, which happens quite frequently.
and both these are available via the data entry module I think. Right Yusuph?
Whether it is allowed to move the data or not of course depends on the user privileges and whether the new orgunit is assigned to the dataset or not, same validation as for normal data entry I guess.
On Wed, Nov 25, 2009 at 9:43 AM, Ola Hodne Titlestad olatitle@gmail.com wrote:
Hi Yusuph,
I agree, that is a nice feature of DHIS 1.4.
I remember it was discussed long time ago, not sure why it was never prioritised or implemented.
There are two specific features here if I remember correctly.
The ability to move all data in a form instance (orgunit+period+dataset) to a new orgunit
The ability to move all data in a form instance (orgunit+period+dataset) to a new period
This is very useful when the user has either filled the form for the wrong period or the wrong orgunit, which happens quite frequently.
and both these are available via the data entry module I think. Right Yusuph?
Whether it is allowed to move the data or not of course depends on the user privileges and whether the new orgunit is assigned to the dataset or not, same validation as for normal data entry I guess.
Devs, is this doable?
Everything is doable. Yusuph, this sounds like a nice task for you, why don’t you give it a try?
On Wed, Nov 25, 2009 at 9:43 AM, Ola Hodne Titlestad olatitle@gmail.com wrote:
Hi Yusuph,
I agree, that is a nice feature of DHIS 1.4.
I remember it was discussed long time ago, not sure why it was never prioritised or implemented.
There are two specific features here if I remember correctly.
The ability to move all data in a form instance (orgunit+period+dataset) to a new orgunit
The ability to move all data in a form instance (orgunit+period+dataset) to a new period
This is very useful when the user has either filled the form for the wrong period or the wrong orgunit, which happens quite frequently.
and both these are available via the data entry module I think. Right Yusuph?
Whether it is allowed to move the data or not of course depends on the user privileges and whether the new orgunit is assigned to the dataset or not, same validation as for normal data entry I guess.
Devs, is this doable?
Everything is doable. Yusuph, this sounds like a nice task for you, why don’t you give it a try?
OK I have created a new branch for you, you can check it out from:
lp:~dhis2-devs-core/dhis2/data-movement
You can put the service functionality in the dhis-service-administration module, and the web functionality in the dhis-web-maintenance-dataadmin module.
For further requirements it’s a good idea to simply refer to what’s been done DHIS 1.4.
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.
I can try the implementation, but expect alot of questions on the way,
cheers.
NB. in the latest built I think there is a bug on the save calculated data element, it does not compute run the action,
and also in the new excell reports, I think there is something wrong when you are trying to add a formula in the selection list.
OK I have created a new branch for you, you can check it out from:
lp:~dhis2-devs-core/dhis2/data-movement
You can put the service functionality in the dhis-service-administration module, and the web functionality in the dhis-web-maintenance-dataadmin module.
For further requirements it’s a good idea to simply refer to what’s been done DHIS 1.4.
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.
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.