We are currently working on a continuous project where we send about
300 phones with ODK out into the field every 6 weeks (for about 4 days
at a time). In the first round, the phone was functioning completely
which resulted in people getting confused, they played with random
buttons and apps, turned off GPS, etc. So, in the second round, we
locked down the phone completely (ie: the only app they can see is ODK
and everything else needs a password). We are now half-way through the
second round and people are complaining that there is no form to fill
out on ODK. Since I personally checked each phone before it went out
into the field, I know that the only way there could be no form is if
they deleted it themselves.
So, for the next round, is there any way to make adding and deleting a
form password protected on ODK?
If not, is someone in the community interested in developing that for
us? We have a small budget to pay for programming and it will save us
the headache and pain for the next 2 years.
Contributions of any code to provide an administrative lock-down mode will
be greatly appreciated.
Mitch
···
On Thu, Nov 1, 2012 at 9:02 AM, Evelyn Castle wrote:
Hi All,
We are currently working on a continuous project where we send about
300 phones with ODK out into the field every 6 weeks (for about 4 days
at a time). In the first round, the phone was functioning completely
which resulted in people getting confused, they played with random
buttons and apps, turned off GPS, etc. So, in the second round, we
locked down the phone completely (ie: the only app they can see is ODK
and everything else needs a password). We are now half-way through the
second round and people are complaining that there is no form to fill
out on ODK. Since I personally checked each phone before it went out
into the field, I know that the only way there could be no form is if
they deleted it themselves.
So, for the next round, is there any way to make adding and deleting a
form password protected on ODK?
If not, is someone in the community interested in developing that for
us? We have a small budget to pay for programming and it will save us
the headache and pain for the next 2 years.
I dont know if this is similar to what we have been trying.
For our project we require preemptive authentication which is checked on
the server side.
So i am trying to add username password in http header and setting
preemptive auth as true.
Currently I am struggling to get this working. If anyone is aware of any
such code done before then that would be helpful
Thanks,
Parikshit
···
On Thursday, 1 November 2012 12:02:56 UTC-4, Evelyn Castle wrote:
>
> Hi All,
>
> We are currently working on a continuous project where we send about
> 300 phones with ODK out into the field every 6 weeks (for about 4 days
> at a time). In the first round, the phone was functioning completely
> which resulted in people getting confused, they played with random
> buttons and apps, turned off GPS, etc. So, in the second round, we
> locked down the phone completely (ie: the only app they can see is ODK
> and everything else needs a password). We are now half-way through the
> second round and people are complaining that there is no form to fill
> out on ODK. Since I personally checked each phone before it went out
> into the field, I know that the only way there could be no form is if
> they deleted it themselves.
>
> So, for the next round, is there any way to make adding and deleting a
> form password protected on ODK?
>
> If not, is someone in the community interested in developing that for
> us? We have a small budget to pay for programming and it will save us
> the headache and pain for the next 2 years.
>
> Please let me know. Thanks,
> Evelyn
>
> --
> Evelyn Castle
> Director, eHealth Nigeria
> www.eHealthNigeria.org
> 25 Race Course Road, Kano, Ng
> mobile: (NG) 0809-515-0585
> (NG) 0813-883-2395
> (US) 714-627-9289
>
Have you considered the KoBo Enum app? It's a locked down version of KoBo
Collect designed specifically for enumerators who do not need control over
forms like deleting them. KoBo is based on ODK.
I hope the ODK project could have something similar.
···
On Friday, November 2, 2012, Evelyn Castle wrote:
Hi All,
We are currently working on a continuous project where we send about
300 phones with ODK out into the field every 6 weeks (for about 4 days
at a time). In the first round, the phone was functioning completely
which resulted in people getting confused, they played with random
buttons and apps, turned off GPS, etc. So, in the second round, we
locked down the phone completely (ie: the only app they can see is ODK
and everything else needs a password). We are now half-way through the
second round and people are complaining that there is no form to fill
out on ODK. Since I personally checked each phone before it went out
into the field, I know that the only way there could be no form is if
they deleted it themselves.
So, for the next round, is there any way to make adding and deleting a
form password protected on ODK?
If not, is someone in the community interested in developing that for
us? We have a small budget to pay for programming and it will save us
the headache and pain for the next 2 years.