[ODK Community] Re: Move ODK Collect data to SD card?

Tks!
Bob

Our team is working on adding a general settings option to ODK Collect that
will be a data path for where to store Filled Forms data. We were running
out of room on internal memory due to all of our filled forms media.
Adding the flexibility to save forms data on the external SD is our last
resort.

The Forms data path option in the General Settings will open a File Chooser
so that the user can search for the external SD location. Once the User
locates the path to the external SD and presses enter then the existing
filled forms data will be moved over (if there is enough room). Any
subsequent reads and writes to forms will follow the new saved path.

Hopefully, getting the user involved in identifying the location of the
ext-SD using the File Chooser will remove ambiguity... as different devices
name their path to ext SD differently making it impossible to determine
pro-grammatically.

If you want to try to see if this filled forms data path fix will support
your device and version of Android, download this File Chooser demo and
surf to see if you can find your external SD. If you can then maybe this
mod will work on your device.

Here are the Android versions that we have tried the demo on so far...
? Ice Cream Sandwich (4.0–4.0.4)
WORKS! Jelly Bean (4.1–4.3.1)
WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2)
? Lollipop (5.0–5.1.1)
? Android M

Let me know if the demo does not work on your device and we we will try to
understand what tweak is necessary to support your device/version.

On one of my devices the extSD showed up as "ext SD" but on another device
it showed up as "removable" and the internal SD showed up as "sdcard". So
it is helping to have the user in the loop to discern the real external SD
location.

Even if you don't need the extra space ... this option might be useful to
you to make it easy for the Enumerator to shuffle the data to the ext SD to
send in when there is no reliable wifi to do so.

Stay tuned. The cook is still in the kitchen... it is not soup yet.

Any suggestions on a better way to implement a filled forms data path?

Thanks!
Bob

··· >

Note that this likely requires some changes to the content providers to
delay resolving the database path.

If memory serves, the constructor for the content provider is executed
before the Application object is created. If you are accessing shared
preferences to get the root location to construct the database path and
open it in the constructor, you might not have a valid context at that
point in time.

··· On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill wrote:

Our team is working on adding a general settings option to ODK Collect
that will be a data path for where to store Filled Forms data. We were
running out of room on internal memory due to all of our filled forms
media. Adding the flexibility to save forms data on the external SD is our
last resort.

The Forms data path option in the General Settings will open a File
Chooser so that the user can search for the external SD location. Once the
User locates the path to the external SD and presses enter then the
existing filled forms data will be moved over (if there is enough room).
Any subsequent reads and writes to forms will follow the new saved path.

Hopefully, getting the user involved in identifying the location of the
ext-SD using the File Chooser will remove ambiguity... as different devices
name their path to ext SD differently making it impossible to determine
pro-grammatically.

If you want to try to see if this filled forms data path fix will support
your device and version of Android, download this File Chooser demo and
surf to see if you can find your external SD. If you can then maybe this
mod will work on your device.

https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test

Here are the Android versions that we have tried the demo on so far...
? Ice Cream Sandwich (4.0–4.0.4)
WORKS! Jelly Bean (4.1–4.3.1)
WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2)
? Lollipop (5.0–5.1.1)
? Android M

Let me know if the demo does not work on your device and we we will try to
understand what tweak is necessary to support your device/version.

On one of my devices the extSD showed up as "ext SD" but on another device
it showed up as "removable" and the internal SD showed up as "sdcard". So
it is helping to have the user in the loop to discern the real external SD
location.

Even if you don't need the extra space ... this option might be useful to
you to make it easy for the Enumerator to shuffle the data to the ext SD to
send in when there is no reliable wifi to do so.

Stay tuned. The cook is still in the kitchen... it is not soup yet.

Any suggestions on a better way to implement a filled forms data path?

Thanks!
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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

And if you're making this change, it would be nice to change the paths
stored in the content provider / database to begin with the 'odk'
directory. i.e., strip off the user-defined path prefix that you're setting.

This would eliminate problems should someone have a device that they are
using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best
practice to remove the 'External Storage Directory' portion of a path
before storing it for reuse (and that is what precedes the 'odk' directory
currently -- with your change, you would be replacing that prefix with
another one).

You could achieve this with a version bump in the database version, and a
migration action.

But that change is secondary. It would be a nice future-proofing and
clean-up of the code, but not critical.

··· On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt wrote:

Note that this likely requires some changes to the content providers to
delay resolving the database path.

If memory serves, the constructor for the content provider is executed
before the Application object is created. If you are accessing shared
preferences to get the root location to construct the database path and
open it in the constructor, you might not have a valid context at that
point in time.

On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill bobachgill@gmail.com wrote:

Our team is working on adding a general settings option to ODK Collect
that will be a data path for where to store Filled Forms data. We were
running out of room on internal memory due to all of our filled forms
media. Adding the flexibility to save forms data on the external SD is our
last resort.

The Forms data path option in the General Settings will open a File
Chooser so that the user can search for the external SD location. Once the
User locates the path to the external SD and presses enter then the
existing filled forms data will be moved over (if there is enough room).
Any subsequent reads and writes to forms will follow the new saved path.

Hopefully, getting the user involved in identifying the location of the
ext-SD using the File Chooser will remove ambiguity... as different devices
name their path to ext SD differently making it impossible to determine
pro-grammatically.

If you want to try to see if this filled forms data path fix will support
your device and version of Android, download this File Chooser demo and
surf to see if you can find your external SD. If you can then maybe this
mod will work on your device.

https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test

Here are the Android versions that we have tried the demo on so far...
? Ice Cream Sandwich (4.0–4.0.4)
WORKS! Jelly Bean (4.1–4.3.1)
WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2)
? Lollipop (5.0–5.1.1)
? Android M

Let me know if the demo does not work on your device and we we will try
to understand what tweak is necessary to support your device/version.

On one of my devices the extSD showed up as "ext SD" but on another
device it showed up as "removable" and the internal SD showed up as
"sdcard". So it is helping to have the user in the loop to discern the
real external SD location.

Even if you don't need the extra space ... this option might be useful to
you to make it easy for the Enumerator to shuffle the data to the ext SD to
send in when there is no reliable wifi to do so.

Stay tuned. The cook is still in the kitchen... it is not soup yet.

Any suggestions on a better way to implement a filled forms data path?

Thanks!
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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Thanks Mitch!

Just to clarify expectations... we were thinking the data path option will
ONLY allow for moving the data directory that contains filled forms data
(/instances) to the external SD NOT the application database also, etc.

Thanks again!

Bob

··· On Tuesday, August 11, 2015 at 2:28:45 PM UTC-5, Mitch Sundt wrote: > > And if you're making this change, it would be nice to change the paths > stored in the content provider / database to begin with the 'odk' > directory. i.e., strip off the user-defined path prefix that you're setting. > > This would eliminate problems should someone have a device that they are > using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best > practice to remove the 'External Storage Directory' portion of a path > before storing it for reuse (and that is what precedes the 'odk' directory > currently -- with your change, you would be replacing that prefix with > another one). > > You could achieve this with a version bump in the database version, and a > migration action. > > But that change is secondary. It would be a nice future-proofing and > clean-up of the code, but not critical. > > > > On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt <mitche...@gmail.com > wrote: > >> Note that this likely requires some changes to the content providers to >> delay resolving the database path. >> >> If memory serves, the constructor for the content provider is executed >> before the Application object is created. If you are accessing shared >> preferences to get the root location to construct the database path and >> open it in the constructor, you might not have a valid context at that >> point in time. >> >> >> >> >> On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill <bobac...@gmail.com > wrote: >> >>> Our team is working on adding a general settings option to ODK Collect >>> that will be a data path for where to store Filled Forms data. We were >>> running out of room on internal memory due to all of our filled forms >>> media. Adding the flexibility to save forms data on the external SD is our >>> last resort. >>> >>> The Forms data path option in the General Settings will open a File >>> Chooser so that the user can search for the external SD location. Once the >>> User locates the path to the external SD and presses enter then the >>> existing filled forms data will be moved over (if there is enough room). >>> Any subsequent reads and writes to forms will follow the new saved path. >>> >>> Hopefully, getting the user involved in identifying the location of the >>> ext-SD using the File Chooser will remove ambiguity... as different devices >>> name their path to ext SD differently making it impossible to determine >>> pro-grammatically. >>> >>> If you want to try to see if this filled forms data path fix will >>> support your device and version of Android, download this File Chooser >>> demo and surf to see if you can find your external SD. If you can then >>> maybe this mod will work on your device. >>> >>> >>> https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test >>> >>> Here are the Android versions that we have tried the demo on so far... >>> ? Ice Cream Sandwich (4.0–4.0.4) >>> WORKS! Jelly Bean (4.1–4.3.1) >>> WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2) >>> ? Lollipop (5.0–5.1.1) >>> ? Android M >>> >>> Let me know if the demo does not work on your device and we we will try >>> to understand what tweak is necessary to support your device/version. >>> >>> On one of my devices the extSD showed up as "ext SD" but on another >>> device it showed up as "removable" and the internal SD showed up as >>> "sdcard". So it is helping to have the user in the loop to discern the >>> real external SD location. >>> >>> Even if you don't need the extra space ... this option might be useful >>> to you to make it easy for the Enumerator to shuffle the data to the ext SD >>> to send in when there is no reliable wifi to do so. >>> >>> Stay tuned. The cook is still in the kitchen... it is not soup yet. >>> >>> Any suggestions on a better way to implement a filled forms data path? >>> >>> Thanks! >>> Bob >>> >>>> -- >>> -- >>> Post: opend...@googlegroups.com >>> Unsubscribe: opendatakit...@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...@googlegroups.com . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Mitch Sundt >> Software Engineer >> University of Washington >> mitche...@gmail.com >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com >

Ah, OK. That sounds much easier to accomplish.

··· On Tue, Aug 11, 2015 at 3:16 PM, Bob Achgill wrote:

Thanks Mitch!

Just to clarify expectations... we were thinking the data path option will
ONLY allow for moving the data directory that contains filled forms data
(/instances) to the external SD NOT the application database also, etc.

Thanks again!

Bob

On Tuesday, August 11, 2015 at 2:28:45 PM UTC-5, Mitch Sundt wrote:

And if you're making this change, it would be nice to change the paths
stored in the content provider / database to begin with the 'odk'
directory. i.e., strip off the user-defined path prefix that you're setting.

This would eliminate problems should someone have a device that they are
using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best
practice to remove the 'External Storage Directory' portion of a path
before storing it for reuse (and that is what precedes the 'odk' directory
currently -- with your change, you would be replacing that prefix with
another one).

You could achieve this with a version bump in the database version, and a
migration action.

But that change is secondary. It would be a nice future-proofing and
clean-up of the code, but not critical.

On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt mitche...@gmail.com wrote:

Note that this likely requires some changes to the content providers to
delay resolving the database path.

If memory serves, the constructor for the content provider is executed
before the Application object is created. If you are accessing shared
preferences to get the root location to construct the database path and
open it in the constructor, you might not have a valid context at that
point in time.

On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill bobac...@gmail.com wrote:

Our team is working on adding a general settings option to ODK Collect
that will be a data path for where to store Filled Forms data. We were
running out of room on internal memory due to all of our filled forms
media. Adding the flexibility to save forms data on the external SD is our
last resort.

The Forms data path option in the General Settings will open a File
Chooser so that the user can search for the external SD location. Once the
User locates the path to the external SD and presses enter then the
existing filled forms data will be moved over (if there is enough room).
Any subsequent reads and writes to forms will follow the new saved path.

Hopefully, getting the user involved in identifying the location of the
ext-SD using the File Chooser will remove ambiguity... as different devices
name their path to ext SD differently making it impossible to determine
pro-grammatically.

If you want to try to see if this filled forms data path fix will
support your device and version of Android, download this File Chooser
demo and surf to see if you can find your external SD. If you can then
maybe this mod will work on your device.

https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test

Here are the Android versions that we have tried the demo on so far...
? Ice Cream Sandwich (4.0–4.0.4)
WORKS! Jelly Bean (4.1–4.3.1)
WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2)
? Lollipop (5.0–5.1.1)
? Android M

Let me know if the demo does not work on your device and we we will try
to understand what tweak is necessary to support your device/version.

On one of my devices the extSD showed up as "ext SD" but on another
device it showed up as "removable" and the internal SD showed up as
"sdcard". So it is helping to have the user in the loop to discern the
real external SD location.

Even if you don't need the extra space ... this option might be useful
to you to make it easy for the Enumerator to shuffle the data to the ext SD
to send in when there is no reliable wifi to do so.

Stay tuned. The cook is still in the kitchen... it is not soup yet.

Any suggestions on a better way to implement a filled forms data path?

Thanks!
Bob

--
--
Post: opend...@googlegroups.com
Unsubscribe: opendatakit...@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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

--

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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Does anyone know what the status of this update is? Is it possible to implement this in ODK currently?

Thanks,
Jared

··· El martes, 11 de agosto de 2015, 18:16:13 (UTC-4), Bob Achgill escribió: > Thanks Mitch! > > > Just to clarify expectations... we were thinking the data path option will ONLY allow for moving the data directory that contains filled forms data (/instances) to the external SD NOT the application database also, etc. > > > Thanks again! > > > > Bob > > > On Tuesday, August 11, 2015 at 2:28:45 PM UTC-5, Mitch Sundt wrote: > And if you're making this change, it would be nice to change the paths stored in the content provider / database to begin with the 'odk' directory. i.e., strip off the user-defined path prefix that you're setting. > > > This would eliminate problems should someone have a device that they are using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best practice to remove the 'External Storage Directory' portion of a path before storing it for reuse (and that is what precedes the 'odk' directory currently -- with your change, you would be replacing that prefix with another one). > > > You could achieve this with a version bump in the database version, and a migration action. > > > But that change is secondary. It would be a nice future-proofing and clean-up of the code, but not critical. > > > > > > > On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt wrote: > > Note that this likely requires some changes to the content providers to delay resolving the database path. > > > If memory serves, the constructor for the content provider is executed before the Application object is created. If you are accessing shared preferences to get the root location to construct the database path and open it in the constructor, you might not have a valid context at that point in time. > > > > > > > > > > > On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill wrote: > > > > Our team is working on adding a general settings option to ODK Collect that will be a data path for where to store Filled Forms data. We were running out of room on internal memory due to all of our filled forms media. Adding the flexibility to save forms data on the external SD is our last resort. > > > The Forms data path option in the General Settings will open a File Chooser so that the user can search for the external SD location. Once the User locates the path to the external SD and presses enter then the existing filled forms data will be moved over (if there is enough room). Any subsequent reads and writes to forms will follow the new saved path. > > > Hopefully, getting the user involved in identifying the location of the ext-SD using the File Chooser will remove ambiguity... as different devices name their path to ext SD differently making it impossible to determine pro-grammatically. > > > If you want to try to see if this filled forms data path fix will support your device and version of Android, download this File Chooser demo and surf to see if you can find your external SD. If you can then maybe this mod will work on your device. > > > https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test > > > Here are the Android versions that we have tried the demo on so far... > ? Ice Cream Sandwich (4.0–4.0.4) > WORKS! Jelly Bean (4.1–4.3.1) > WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2) > ? Lollipop (5.0–5.1.1) > ? Android M > > > Let me know if the demo does not work on your device and we we will try to understand what tweak is necessary to support your device/version. > > > On one of my devices the extSD showed up as "ext SD" but on another device it showed up as "removable" and the internal SD showed up as "sdcard". So it is helping to have the user in the loop to discern the real external SD location. > > > Even if you don't need the extra space ... this option might be useful to you to make it easy for the Enumerator to shuffle the data to the ext SD to send in when there is no reliable wifi to do so. > > > Stay tuned. The cook is still in the kitchen... it is not soup yet. > > > Any suggestions on a better way to implement a filled forms data path? > > > Thanks! > Bob > > > > > > > > > > -- > > -- > > Post: opend...@googlegroups.com > > Unsubscribe: opendatakit...@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...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com > > > > > > -- > > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com

No code changes were contributed.

As stated earlier in this thread (or another one), the first step is to
consolidate all file path construction so that it is done by a single class
used by everything. Then provide some mechanism to configure what the
methods in that class do. By only moving the instance files out, it does
become easier.

··· On Wed, Sep 28, 2016 at 10:42 AM, Jared wrote:

Does anyone know what the status of this update is? Is it possible to
implement this in ODK currently?

Thanks,
Jared

El martes, 11 de agosto de 2015, 18:16:13 (UTC-4), Bob Achgill escribió:

Thanks Mitch!

Just to clarify expectations... we were thinking the data path option
will ONLY allow for moving the data directory that contains filled forms
data (/instances) to the external SD NOT the application database also, etc.

Thanks again!

Bob

On Tuesday, August 11, 2015 at 2:28:45 PM UTC-5, Mitch Sundt wrote:
And if you're making this change, it would be nice to change the paths
stored in the content provider / database to begin with the 'odk'
directory. i.e., strip off the user-defined path prefix that you're setting.

This would eliminate problems should someone have a device that they are
using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best
practice to remove the 'External Storage Directory' portion of a path
before storing it for reuse (and that is what precedes the 'odk' directory
currently -- with your change, you would be replacing that prefix with
another one).

You could achieve this with a version bump in the database version, and
a migration action.

But that change is secondary. It would be a nice future-proofing and
clean-up of the code, but not critical.

On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt mitche...@gmail.com wrote:

Note that this likely requires some changes to the content providers to
delay resolving the database path.

If memory serves, the constructor for the content provider is executed
before the Application object is created. If you are accessing shared
preferences to get the root location to construct the database path and
open it in the constructor, you might not have a valid context at that
point in time.

On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill bobac...@gmail.com wrote:

Our team is working on adding a general settings option to ODK Collect
that will be a data path for where to store Filled Forms data. We were
running out of room on internal memory due to all of our filled forms
media. Adding the flexibility to save forms data on the external SD is our
last resort.

The Forms data path option in the General Settings will open a File
Chooser so that the user can search for the external SD location. Once the
User locates the path to the external SD and presses enter then the
existing filled forms data will be moved over (if there is enough room).
Any subsequent reads and writes to forms will follow the new saved path.

Hopefully, getting the user involved in identifying the location of the
ext-SD using the File Chooser will remove ambiguity... as different devices
name their path to ext SD differently making it impossible to determine
pro-grammatically.

If you want to try to see if this filled forms data path fix will
support your device and version of Android, download this File Chooser
demo and surf to see if you can find your external SD. If you can then
maybe this mod will work on your device.

https://play.google.com/store/apps/details?id=ar.com.
daidalos.afiledialog.test

Here are the Android versions that we have tried the demo on so far...
? Ice Cream Sandwich (4.0–4.0.4)
WORKS! Jelly Bean (4.1–4.3.1)
WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2)
? Lollipop (5.0–5.1.1)
? Android M

Let me know if the demo does not work on your device and we we will try
to understand what tweak is necessary to support your device/version.

On one of my devices the extSD showed up as "ext SD" but on another
device it showed up as "removable" and the internal SD showed up as
"sdcard". So it is helping to have the user in the loop to discern the
real external SD location.

Even if you don't need the extra space ... this option might be useful
to you to make it easy for the Enumerator to shuffle the data to the ext SD
to send in when there is no reliable wifi to do so.

Stay tuned. The cook is still in the kitchen... it is not soup yet.

Any suggestions on a better way to implement a filled forms data path?

Thanks!
Bob

--

--

Post: opend...@googlegroups.com

Unsubscribe: opendatakit...@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...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

--

Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

--

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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

I've filed this at https://github.com/opendatakit/collect/issues/208.
If anyone has code that they want to contribute for this feature,
please send in a pull request.

Yaw

··· On Thu, Sep 29, 2016 at 2:24 AM, Mitch Sundt wrote: > No code changes were contributed. > > As stated earlier in this thread (or another one), the first step is to > consolidate all file path construction so that it is done by a single class > used by everything. Then provide some mechanism to configure what the > methods in that class do. By only moving the instance files out, it does > become easier. > > > On Wed, Sep 28, 2016 at 10:42 AM, Jared wrote: >> >> Does anyone know what the status of this update is? Is it possible to >> implement this in ODK currently? >> >> Thanks, >> Jared >> >> El martes, 11 de agosto de 2015, 18:16:13 (UTC-4), Bob Achgill escribió: >> > Thanks Mitch! >> > >> > >> > Just to clarify expectations... we were thinking the data path option >> > will ONLY allow for moving the data directory that contains filled forms >> > data (/instances) to the external SD NOT the application database also, etc. >> > >> > >> > Thanks again! >> > >> > >> > >> > Bob >> > >> > >> > On Tuesday, August 11, 2015 at 2:28:45 PM UTC-5, Mitch Sundt wrote: >> > And if you're making this change, it would be nice to change the paths >> > stored in the content provider / database to begin with the 'odk' directory. >> > i.e., strip off the user-defined path prefix that you're setting. >> > >> > >> > This would eliminate problems should someone have a device that they are >> > using and upgrading across OS versions (e.g. 4.1 -> 4.2). It is now best >> > practice to remove the 'External Storage Directory' portion of a path before >> > storing it for reuse (and that is what precedes the 'odk' directory >> > currently -- with your change, you would be replacing that prefix with >> > another one). >> > >> > >> > You could achieve this with a version bump in the database version, and >> > a migration action. >> > >> > >> > But that change is secondary. It would be a nice future-proofing and >> > clean-up of the code, but not critical. >> > >> > >> > >> > >> > >> > >> > On Tue, Aug 11, 2015 at 12:12 PM, Mitch Sundt wrote: >> > >> > Note that this likely requires some changes to the content providers to >> > delay resolving the database path. >> > >> > >> > If memory serves, the constructor for the content provider is executed >> > before the Application object is created. If you are accessing shared >> > preferences to get the root location to construct the database path and open >> > it in the constructor, you might not have a valid context at that point in >> > time. >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On Mon, Aug 10, 2015 at 11:54 AM, Bob Achgill wrote: >> > >> > >> > >> > Our team is working on adding a general settings option to ODK Collect >> > that will be a data path for where to store Filled Forms data. We were >> > running out of room on internal memory due to all of our filled forms media. >> > Adding the flexibility to save forms data on the external SD is our last >> > resort. >> > >> > >> > The Forms data path option in the General Settings will open a File >> > Chooser so that the user can search for the external SD location. Once the >> > User locates the path to the external SD and presses enter then the existing >> > filled forms data will be moved over (if there is enough room). Any >> > subsequent reads and writes to forms will follow the new saved path. >> > >> > >> > Hopefully, getting the user involved in identifying the location of the >> > ext-SD using the File Chooser will remove ambiguity... as different devices >> > name their path to ext SD differently making it impossible to determine >> > pro-grammatically. >> > >> > >> > If you want to try to see if this filled forms data path fix will >> > support your device and version of Android, download this File Chooser demo >> > and surf to see if you can find your external SD. If you can then maybe >> > this mod will work on your device. >> > >> > >> > >> > https://play.google.com/store/apps/details?id=ar.com.daidalos.afiledialog.test >> > >> > >> > Here are the Android versions that we have tried the demo on so far... >> > ? Ice Cream Sandwich (4.0–4.0.4) >> > WORKS! Jelly Bean (4.1–4.3.1) >> > WORKS! KitKat (4.4–4.4.4, 4.4W–4.4W.2) >> > ? Lollipop (5.0–5.1.1) >> > ? Android M >> > >> > >> > Let me know if the demo does not work on your device and we we will try >> > to understand what tweak is necessary to support your device/version. >> > >> > >> > On one of my devices the extSD showed up as "ext SD" but on another >> > device it showed up as "removable" and the internal SD showed up as >> > "sdcard". So it is helping to have the user in the loop to discern the real >> > external SD location. >> > >> > >> > Even if you don't need the extra space ... this option might be useful >> > to you to make it easy for the Enumerator to shuffle the data to the ext SD >> > to send in when there is no reliable wifi to do so. >> > >> > >> > Stay tuned. The cook is still in the kitchen... it is not soup yet. >> > >> > >> > Any suggestions on a better way to implement a filled forms data path? >> > >> > >> > Thanks! >> > Bob >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > -- >> > >> > -- >> > >> > Post: opend...@googlegroups.com >> > >> > Unsubscribe: opendatakit...@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...@googlegroups.com. >> > >> > For more options, visit https://groups.google.com/d/optout. >> > >> > >> > >> > >> > >> > -- >> > >> > Mitch Sundt >> > Software Engineer >> > University of Washington >> > mitche...@gmail.com >> > >> > >> > >> > >> > >> > -- >> > >> > Mitch Sundt >> > Software Engineer >> > University of Washington >> > mitche...@gmail.com >> >> -- >> -- >> 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. > > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitchellsundt@gmail.com > > -- > -- > 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.