For one project, we have about 60 fieldworkers, each of whom currently
covers one or more administrative area (known as a VDC). Each VDC is
divided into 9 wards.
We are planning to assign more fieldworkers to the project, and to
re-distribute the workload in such a way that some VDCs (but not wards)
will be split between fieldworkers. Our project has two case types, women,
who are identified by name (I mean, the CommCare case name is the woman's
name), and pregnancies, which are identified by a number that starts with
the VDC and ward numbers. We currently have over 16000 cases in all, a
considerable number of which may need to be re-assigned.
It is relatively easy (if tedious) to manually select the pregnancy cases
that need to be re-assigned to a new fieldworker. It's not possible to
identify the corresponding woman cases, without examining the detailed data
for each woman case (because the case name does not contain the relevant
information).
Is there some way to get round this? The things I've thought about as
potential solutions include:
Changing the name of the woman cases so that it is an ID number, like
that for the pregnancy cases, which contains the VDC and ward information.
I guess we could do this by changing the application to assign the ID as
the case name for new cases, and use Excel import to change the existing
cases, but again it's not obvious from the documentation if it's possible
to change the names of existing cases.
Does anyone have any comments / suggestions?
Incidentally, it seems to take a very long time before re-assigned cases
appear on the new fieldworker's phone (several hours). Any ideas why?
This is definitely the best option right now. It should work with existing
cases as long as you include and properly map the case IDs.
Incidentally, it seems to take a very long time before re-assigned cases
appear on the new fieldworker's phone (several hours). Any ideas why?
We're aware of slowness in our bulk data management tools, and the
re-assign cases tool is particularly slow and also dependent on your own
internet connection, which is something that is on our radar to fix. Also,
just wanted to confirm that you are manually syncing the phones once the
reassignment is done. Once CommCare HQ shows you that the import/assignment
has been completed it should show up on phones after a manual sync.
Thanks, that's really helpful. I'll test it out now I know it should work
to re-assign existing cases!
I assumed the users were doing manual sync, but I'll check.
ยทยทยท
On Friday, April 11, 2014 12:10:35 PM UTC, Cory Zue wrote:
>
> Hi James,
>
> Is there some way to get round this? The things I've thought about as
>> potential solutions include:
>> 1. Updating the cases with a new owner from an Excel spreadsheet (this is
>> described for new cases at
>> https://confluence.dimagi.com/display/commcarepublic/Assigning+imported+cases+to+a+user,
>> but that page doesn't say it's possible to do it for existing cases).
>> Probably the best solution, if it works.
>>
>
> This is definitely the best option right now. It should work with existing
> cases as long as you include and properly map the case IDs.
>
>
>> Incidentally, it seems to take a _very_ long time before re-assigned
>> cases appear on the new fieldworker's phone (several hours). Any ideas why?
>>
>
> We're aware of slowness in our bulk data management tools, and the
> re-assign cases tool is particularly slow and also dependent on your own
> internet connection, which is something that is on our radar to fix. Also,
> just wanted to confirm that you are manually syncing the phones once the
> reassignment is done. Once CommCare HQ shows you that the import/assignment
> has been completed it should show up on phones after a manual sync.
>
> cheers,
> Cory
>