Thanks Yaw.
Maybe just add an import export function for New and Edit Saved forms. That way you don't have to mess with all the internal file management code with the risk that the paths are handled different from device to device.
It might look like...
add a button on the Collect main menu labeled "Import/Export" that goes to a screen with a side by side list of new forms and edit forms on the left (Internal) AND new forms and edit forms on the right (SD). The user can slide the forms from one side to the other to accomplish a move of the form and its supporting media. There would be no risk about path because the user identifies the exact location on the external SD by navigating the file structure and select the location on the external SD.
Really people do this move procedure all the time when there is no internet. Might as well add a sidewalk where people have already worn a path in the grass.
The additional benefits will be that it will let enumerators...
- Free up internal memory by shuffling off to external SD forms that they have on hold.
- Make it cleaner to have hand off of a partly edited form from one enumerator or one device to another simply by passing an SD.
- Make it practical to distribute pre-edited forms, like inventory lists, that enumerators log any changes to the inventory.
- Keep a cleaner work space on their internal list(s) by reducing the clutter of too many forms.
Thanks!
Bob
Original message
···
From: "Yaw Anokwa" To: opendatakit@googlegroups.com; Dated: 7/19/2015 5:47:24 PM Subject: Re: [ODK Community] Re: Move ODK Collect data to SD card?Hi Bob,
Nafundi has tried implementing workarounds in an early internal fork
of Collect and a later internal fork. Neither ended well.
The only reasonable workaround is to hardcode every potential device
path and make some changes in how ODK handles files. This might work
OK if you control which devices are used in deployments, but this
still risks data loss because of how ContentProviders are initialized
and it's not sustainable because the Android team is clearly
discouraging external SDs for application data.
I'd recommend you use devices with only internal storage or use
manufacturers that display internal storage in a standard manner.
Yaw
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
On Sun, Jul 19, 2015 at 1:21 AM, Bob Achgill bobachgill@gmail.com wrote:
Is there any work around yet on getting ODK Collect to use the external SD card space?
What is entailed to make this code change?
If I had someone who can do it... is there a design yet?
Tks!
Bob--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to a topic in the Google Groups "ODK Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opendatakit/2ps9ClIOIWA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.