Hi there,
As you know we are happily using ODK collect for data gathering in the
field however the program is branded differently (CKW Program). As
other applications offered by us to the users are named CKW (e.g. CKW
Search, CKW Pulse, etc.) our users find it confusing to look for ODK
in the icons and also in the app pages.
Is it possible to add a field to a config file for the brand and
mention to ODK in the about of the application or in the footer? In
our case, the text would look like this: CKW Survey, powered by ODK
Any solution which can address the brand inconsistency is much
appreciated.
we've loosened the request to put odk in the names of your apps.
we are now been asking people to put "powered by open data kit" or
"built on open data kit" or something similar in the description of
the application so when people search for "open data kit", they can
see all the odk related applications in the android market.
for apps that aren't in the market, we'll be adding some code that
puts a small "powered by open data kit" on the main screen.
···
On Wed, Aug 11, 2010 at 17:42, shayan@grameen wrote:
> Hi there,
> As you know we are happily using ODK collect for data gathering in the
> field however the program is branded differently (CKW Program). As
> other applications offered by us to the users are named CKW (e.g. CKW
> Search, CKW Pulse, etc.) our users find it confusing to look for ODK
> in the icons and also in the app pages.
>
> Is it possible to add a field to a config file for the brand and
> mention to ODK in the about of the application or in the footer? In
> our case, the text would look like this: CKW Survey, powered by ODK
>
>
> Any solution which can address the brand inconsistency is much
> appreciated.
>
> Thanks,
> Shayan
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
If your organization is configuring phones for your workers, there are
applications, like FileOrganizer Lite, that allow you to define new
shortcuts and icons for an application, giving you a means to brand the
desktop icons and labels for your organization.
The ODK team will shortly release an ODK Collect that supports adding a
customized splash screen on application start-up and for displaying an image
on the form-start page (which has been cleaned up a bit) for branding
purposes. Attached is a screen shot of the new form-start page showing the
customization possibilities.
I've looked into what would be required to directly support customized icons
and shortcut labels within ODK Collect. Unfortunately, it is a sizable
chunk of code to write and maintain. Using an application like
FileOrganizer Lite makes the most sense.
Mitch
···
On Wed, Aug 11, 2010 at 5:49 PM, Yaw Anokwa wrote:
we've loosened the request to put odk in the names of your apps.
we are now been asking people to put "powered by open data kit" or
"built on open data kit" or something similar in the description of
the application so when people search for "open data kit", they can
see all the odk related applications in the android market.
for apps that aren't in the market, we'll be adding some code that
puts a small "powered by open data kit" on the main screen.
On Wed, Aug 11, 2010 at 17:42, shayan@grameen shayan@gmail.com wrote:
Hi there,
As you know we are happily using ODK collect for data gathering in the
field however the program is branded differently (CKW Program). As
other applications offered by us to the users are named CKW (e.g. CKW
Search, CKW Pulse, etc.) our users find it confusing to look for ODK
in the icons and also in the app pages.
Is it possible to add a field to a config file for the brand and
mention to ODK in the about of the application or in the footer? In
our case, the text would look like this: CKW Survey, powered by ODK
Any solution which can address the brand inconsistency is much
appreciated.
Hello. I am trying to figure out how ODK flags instances so that they become hidden to the user but stay on the SD card (e.g. after they are sent to Aggregate server). I am using adb to pull data and and I would like to make the completed instances disappear from the UI after pulling.
if you delete an instance from the sd card, it should not appear in
the list of forms. after pulling, try 'adb shell rm filename'
···
On Sun, Aug 15, 2010 at 10:32, Andrew Azman wrote:
> Hello. I am trying to figure out how ODK flags instances so that they become hidden to the user but stay on the SD card (e.g. after they are sent to Aggregate server). I am using adb to pull data and and I would like to make the completed instances disappear from the UI after pulling.
>
> Thanks,
> andrew
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
After sending to the Aggregate server, though...the surveys are no
longer visible in the ODK interface, but do they remain on the SD
card?
···
On 8/17/10, Yaw Anokwa wrote:
> if you delete an instance from the sd card, it should not appear in
> the list of forms. after pulling, try 'adb shell rm filename'
>
> On Sun, Aug 15, 2010 at 10:32, Andrew Azman wrote:
>> Hello. I am trying to figure out how ODK flags instances so that they
>> become hidden to the user but stay on the SD card (e.g. after they are
>> sent to Aggregate server). I am using adb to pull data and and I would
>> like to make the completed instances disappear from the UI after pulling.
>>
>> Thanks,
>> andrew
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
sorry, I wasn't clear. I want to keep it on the SD card. I tried using adb
shell mv in a script to move it to another folder and it doesn't work so
well. I noticed that sometimes after pulling data the viewable instances
goes to zero despite the fact that they are still in the instances
directory.
How does uploading to aggregate make them disappear from collect?
andrew azman
if you delete an instance from the sd card, it should not appear in
the list of forms. after pulling, try 'adb shell rm filename'
that is correct. we mark them as sent and hide them in the db.
···
On Wed, Aug 18, 2010 at 06:19, Neil Hendrick wrote:
> After sending to the Aggregate server, though...the surveys are no
> longer visible in the ODK interface, but do they remain on the SD
> card?
>
> On 8/17/10, Yaw Anokwa wrote:
>> if you delete an instance from the sd card, it should not appear in
>> the list of forms. after pulling, try 'adb shell rm filename'
>>
>> On Sun, Aug 15, 2010 at 10:32, Andrew Azman wrote:
>>> Hello. I am trying to figure out how ODK flags instances so that they
>>> become hidden to the user but stay on the SD card (e.g. after they are
>>> sent to Aggregate server). I am using adb to pull data and and I would
>>> like to make the completed instances disappear from the UI after pulling.
>>>
>>> Thanks,
>>> andrew
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
> --
> ☞§※⌘✈☂
> ~Neil
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
The instance files themselves. This is the .xml file and any associated
binary files. These are never deleted by Collect.
A metadata database. This database keeps track of the status of forms
(complete, incomplete, sent, etc..). It may get slightly more complicated
in the future, but for now that's all it does. The numbers that appear on
the main menu are generated by counting entries in the database.
You can only send 'complete' forms, and once you send a form using Collect
the form gets marked as 'sent' in the database. 'sent' forms are not
displayed by Collect, but the instance directories/files remain on the SD
card.
If you delete or rename an instance directory, that entry is deleted from
the database since it's presumed to no longer exist. Also, 'adb pull' only
copies files, it doesn't delete them. Moving the directory elsewhere will
also remove it from the database.
Hope that helps clear up what's happening. This interaction seemed to make
the most sense to us at the time, but if you have other ideas it'd be great
to hear them!
-Carl
···
On Wed, Aug 18, 2010 at 8:20 AM, Andrew Azman wrote:
sorry, I wasn't clear. I want to keep it on the SD card. I tried using adb
shell mv in a script to move it to another folder and it doesn't work so
well. I noticed that sometimes after pulling data the viewable instances
goes to zero despite the fact that they are still in the instances
directory.
How does uploading to aggregate make them disappear from collect?
Thanks for the clarification Carl. Is there an "easy-ish" manual way to manipulate the db through adb? If not, I will play around with it a bit and get back to you all if I figure something out. I think this would be useful for those of us not using Aggregate.
Thanks,
andrew
···
On Aug 18, 2010, at 4:48 PM, Carl Hartung wrote:
There are two forces at work here:
The instance files themselves. This is the .xml file and any associated binary files. These are never deleted by Collect.
A metadata database. This database keeps track of the status of forms (complete, incomplete, sent, etc..). It may get slightly more complicated in the future, but for now that's all it does. The numbers that appear on the main menu are generated by counting entries in the database.
You can only send 'complete' forms, and once you send a form using Collect the form gets marked as 'sent' in the database. 'sent' forms are not displayed by Collect, but the instance directories/files remain on the SD card.
If you delete or rename an instance directory, that entry is deleted from the database since it's presumed to no longer exist. Also, 'adb pull' only copies files, it doesn't delete them. Moving the directory elsewhere will also remove it from the database.
Hope that helps clear up what's happening. This interaction seemed to make the most sense to us at the time, but if you have other ideas it'd be great to hear them!
-Carl
On Wed, Aug 18, 2010 at 8:20 AM, Andrew Azman andrewazman@gmail.com wrote:
sorry, I wasn't clear. I want to keep it on the SD card. I tried using adb shell mv in a script to move it to another folder and it doesn't work so well. I noticed that sometimes after pulling data the viewable instances goes to zero despite the fact that they are still in the instances directory.
How does uploading to aggregate make them disappear from collect?
you can use sqlite3, but I think it requires root access on your phone to
access the right directory.
That is, from an adb shell, cd to:
cd /data/data/org.odk.collect.android/databases
then run
sqlite3 data
(I think 'data' is the name of the database. if you do a 'ls' it should be
pretty obvious)
Then you can run sql commands on the database.
For the next release, we've moved the metadata database to the sdcard so it
won't require root access to manipulate, but in the current release it's
still stored in the phone's memory.
-Carl
···
On Wed, Aug 18, 2010 at 10:24 AM, Andrew Azman wrote:
Thanks for the clarification Carl. Is there an "easy-ish" manual way to
manipulate the db through adb? If not, I will play around with it a bit and
get back to you all if I figure something out. I think this would be useful
for those of us not using Aggregate.
Thanks,
andrew
On Aug 18, 2010, at 4:48 PM, Carl Hartung wrote:
There are two forces at work here:
The instance files themselves. This is the .xml file and any
associated binary files. These are never deleted by Collect.
A metadata database. This database keeps track of the status of forms
(complete, incomplete, sent, etc..). It may get slightly more complicated
in the future, but for now that's all it does. The numbers that appear on
the main menu are generated by counting entries in the database.
You can only send 'complete' forms, and once you send a form using Collect
the form gets marked as 'sent' in the database. 'sent' forms are not
displayed by Collect, but the instance directories/files remain on the SD
card.
If you delete or rename an instance directory, that entry is deleted from
the database since it's presumed to no longer exist. Also, 'adb pull' only
copies files, it doesn't delete them. Moving the directory elsewhere will
also remove it from the database.
Hope that helps clear up what's happening. This interaction seemed to make
the most sense to us at the time, but if you have other ideas it'd be great
to hear them!
-Carl
sorry, I wasn't clear. I want to keep it on the SD card. I tried using
adb shell mv in a script to move it to another folder and it doesn't work so
well. I noticed that sometimes after pulling data the viewable instances
goes to zero despite the fact that they are still in the instances
directory.
How does uploading to aggregate make them disappear from collect?
