I enumerated data on a Chinese Huawei model 3 phone then moved the data to another phone by ... copying the /SurveyCTO directory to another phone replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both in the Fill Blank Forms and Edit Saved Forms areas. Though when I try to edit the existing form on the destination phone I get the error message that the file does not exist... and it says some funny path like ... "/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try to access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of internal versus external memory. Somehow OKD/SurveyCTO stored the virtual path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data. 
Thanks!
Bob
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
···
On Mon, Jun 30, 2014 at 11:51 AM, wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the data to
another phone by ... copying the /SurveyCTO directory to another phone
replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both in
the Fill Blank Forms and Edit Saved Forms areas. Though when I try to edit
the existing form on the destination phone I get the error message that the
file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try to
access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Agreed. This is an issue when moving across Android 4.x builds. Google
changed the full ExternalStorage path from 4.1 to 4.2 in order to support
multiple user profiles on one device.
In the face of this, the recommended solution from Google is to store only
partial paths -- e.g., when saving filepaths in the database, start the
path from the 'odk' directory, instead of from /sdcard/...
This would change a bunch of things in ODK Collect, as there are places
where we search for the form by the full pathname
To truly fix this, ODK Collect would need to increment its database
version, and, in the onUpdate() method, it would replace all the full
pathnames in the database with paths relative to the 'odk/' directory.
There would be two new methods in FileUtils:
class FileUtils {
...
public static String asRelativePath(File file)
{
// strip off all directories before 'odk'. return 'odk/...' relativePath.
}
public static File asFile(String relativePath) {
// prepend the ExternalStorage directory to the 'odk/...' relativePath.
}
...
}
···
--------------
I am unclear if the relative path would also need to support '../' as the
first segment to handle arbitrary file placement within the sdcard. Not
sure what external tools might require that (e.g., clinic)
If anyone wants to sleuth through and contribute the code to handle this,
I'd fold it in.
Mitch
On Mon, Jun 30, 2014 at 8:57 AM, Christopher Robert crobert@surveycto.com wrote:
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
On Mon, Jun 30, 2014 at 11:51 AM, bobachgill@gmail.com wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the data
to another phone by ... copying the /SurveyCTO directory to another phone
replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both in
the Fill Blank Forms and Edit Saved Forms areas. Though when I try to edit
the existing form on the destination phone I get the error message that the
file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try to
access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Thanks, Mitch.
Do we know of any devices that allowed users to update from 4.1 to 4.2+? If
not, this becomes purely a portability issue for data moved from one device
to another; the restriction becomes: for data captured on a pre-4.2 device,
you can only use it on another pre-4.2 device, and similarly for data
captured on a 4.2+ device. That would seem like a restriction that most
people might be able to live within.
Bob, that would mean that you wouldn't need a device to perfectly match,
but one that's either pre-4.2 or 4.2+, depending on your data-collection
device.
Best,
Chris
···
On Mon, Jun 30, 2014 at 3:45 PM, Mitch Sundt wrote:
Agreed. This is an issue when moving across Android 4.x builds. Google
changed the full ExternalStorage path from 4.1 to 4.2 in order to support
multiple user profiles on one device.
In the face of this, the recommended solution from Google is to store only
partial paths -- e.g., when saving filepaths in the database, start the
path from the 'odk' directory, instead of from /sdcard/...
This would change a bunch of things in ODK Collect, as there are places
where we search for the form by the full pathname
To truly fix this, ODK Collect would need to increment its database
version, and, in the onUpdate() method, it would replace all the full
pathnames in the database with paths relative to the 'odk/' directory.
There would be two new methods in FileUtils:
class FileUtils {
...
public static String asRelativePath(File file)
{
// strip off all directories before 'odk'. return 'odk/...'
relativePath.
}
public static File asFile(String relativePath) {
// prepend the ExternalStorage directory to the 'odk/...' relativePath.
}
...
}
I am unclear if the relative path would also need to support '../' as the
first segment to handle arbitrary file placement within the sdcard. Not
sure what external tools might require that (e.g., clinic)
If anyone wants to sleuth through and contribute the code to handle this,
I'd fold it in.
Mitch
On Mon, Jun 30, 2014 at 8:57 AM, Christopher Robert <crobert@surveycto.com wrote:
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
On Mon, Jun 30, 2014 at 11:51 AM, bobachgill@gmail.com wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the data
to another phone by ... copying the /SurveyCTO directory to another phone
replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both
in the Fill Blank Forms and Edit Saved Forms areas. Though when I try to
edit the existing form on the destination phone I get the error message
that the file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try to
access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mitch, I tried porting the /SurveyCTO directory to another device and it works with no path or missing file issue.
Here are the version levels on the three phones...
Origination device: Android 4.2 Emotion UI [Chinese brand Huawei Model Honor 3x, $217]
1st Destination device [missing file error]: Android 4.4.2 [Chinese brand Xiaomi "Showme" $200]
2nd Destination device [that does find the files!] Android 4.2.1
Does this fit your theory of why I was having a missing file error when moving my survey data from one device to another?
Thanks for your insights!
I am thankful not to lose the 30 man-hours that went into enumerating that data. 
Bob Achgill
···
On Monday, June 30, 2014 2:46:00 PM UTC-5, Mitch wrote:
> Agreed. This is an issue when moving across Android 4.x builds. Google changed the full ExternalStorage path from 4.1 to 4.2 in order to support multiple user profiles on one device.
>
Painfully, yes. ASUS Nexus 7 tablets.
Stumbled upon this during ODK 2.0 development last fall.
···
On Mon, Jun 30, 2014 at 12:52 PM, Christopher Robert <chrislrobert@gmail.com wrote:
Thanks, Mitch.
Do we know of any devices that allowed users to update from 4.1 to 4.2+?
If not, this becomes purely a portability issue for data moved from one
device to another; the restriction becomes: for data captured on a pre-4.2
device, you can only use it on another pre-4.2 device, and similarly for
data captured on a 4.2+ device. That would seem like a restriction that
most people might be able to live within.
Bob, that would mean that you wouldn't need a device to perfectly match,
but one that's either pre-4.2 or 4.2+, depending on your data-collection
device.
Best,
Chris
On Mon, Jun 30, 2014 at 3:45 PM, Mitch Sundt mitchellsundt@gmail.com wrote:
Agreed. This is an issue when moving across Android 4.x builds. Google
changed the full ExternalStorage path from 4.1 to 4.2 in order to support
multiple user profiles on one device.
In the face of this, the recommended solution from Google is to store
only partial paths -- e.g., when saving filepaths in the database, start
the path from the 'odk' directory, instead of from /sdcard/...
This would change a bunch of things in ODK Collect, as there are places
where we search for the form by the full pathname
To truly fix this, ODK Collect would need to increment its database
version, and, in the onUpdate() method, it would replace all the full
pathnames in the database with paths relative to the 'odk/' directory.
There would be two new methods in FileUtils:
class FileUtils {
...
public static String asRelativePath(File file)
{
// strip off all directories before 'odk'. return 'odk/...'
relativePath.
}
public static File asFile(String relativePath) {
// prepend the ExternalStorage directory to the 'odk/...' relativePath.
}
...
}
I am unclear if the relative path would also need to support '../' as the
first segment to handle arbitrary file placement within the sdcard. Not
sure what external tools might require that (e.g., clinic)
If anyone wants to sleuth through and contribute the code to handle this,
I'd fold it in.
Mitch
On Mon, Jun 30, 2014 at 8:57 AM, Christopher Robert < crobert@surveycto.com> wrote:
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
On Mon, Jun 30, 2014 at 11:51 AM, bobachgill@gmail.com wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the data
to another phone by ... copying the /SurveyCTO directory to another phone
replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both
in the Fill Blank Forms and Edit Saved Forms areas. Though when I try to
edit the existing form on the destination phone I get the error message
that the file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try
to access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Okay, that's too bad.
We need to see everywhere these paths appear. If it's just a matter of
deleting and re-downloading form definitions, that's not too bad. But if
the paths are in the form instances themselves (even if just for media
files), then that would not be good.
Thanks,
Chris
···
On Mon, Jun 30, 2014 at 4:14 PM, Mitch Sundt wrote:
Painfully, yes. ASUS Nexus 7 tablets.
Stumbled upon this during ODK 2.0 development last fall.
On Mon, Jun 30, 2014 at 12:52 PM, Christopher Robert < chrislrobert@gmail.com> wrote:
Thanks, Mitch.
Do we know of any devices that allowed users to update from 4.1 to 4.2+?
If not, this becomes purely a portability issue for data moved from one
device to another; the restriction becomes: for data captured on a pre-4.2
device, you can only use it on another pre-4.2 device, and similarly for
data captured on a 4.2+ device. That would seem like a restriction that
most people might be able to live within.
Bob, that would mean that you wouldn't need a device to perfectly match,
but one that's either pre-4.2 or 4.2+, depending on your data-collection
device.
Best,
Chris
On Mon, Jun 30, 2014 at 3:45 PM, Mitch Sundt mitchellsundt@gmail.com wrote:
Agreed. This is an issue when moving across Android 4.x builds. Google
changed the full ExternalStorage path from 4.1 to 4.2 in order to support
multiple user profiles on one device.
In the face of this, the recommended solution from Google is to store
only partial paths -- e.g., when saving filepaths in the database, start
the path from the 'odk' directory, instead of from /sdcard/...
This would change a bunch of things in ODK Collect, as there are places
where we search for the form by the full pathname
To truly fix this, ODK Collect would need to increment its database
version, and, in the onUpdate() method, it would replace all the full
pathnames in the database with paths relative to the 'odk/' directory.
There would be two new methods in FileUtils:
class FileUtils {
...
public static String asRelativePath(File file)
{
// strip off all directories before 'odk'. return 'odk/...'
relativePath.
}
public static File asFile(String relativePath) {
// prepend the ExternalStorage directory to the 'odk/...'
relativePath.
}
...
}
I am unclear if the relative path would also need to support '../' as
the first segment to handle arbitrary file placement within the sdcard. Not
sure what external tools might require that (e.g., clinic)
If anyone wants to sleuth through and contribute the code to handle
this, I'd fold it in.
Mitch
On Mon, Jun 30, 2014 at 8:57 AM, Christopher Robert < crobert@surveycto.com> wrote:
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
On Mon, Jun 30, 2014 at 11:51 AM, bobachgill@gmail.com wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the
data to another phone by ... copying the /SurveyCTO directory to another
phone replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both
in the Fill Blank Forms and Edit Saved Forms areas. Though when I try to
edit the existing form on the destination phone I get the error message
that the file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try
to access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
BTW...
2nd destination device [that worked] is an ASUS 7" pad Model Me173X running Android 4.2.1
Thanks for your insights!
I am thankful not to lose the 30 man-hours that went into enumerating that data.
CORRECTION: There were 5 people enumerating so that is 30hours x 5 = 150 hours saved!
I believe moving to relative paths also allows you to make the /odk
folder location configurable. That'd solve the issue of non-standard
Android devices which save to internal memory when external memory is
available.
Yaw
···
--
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
On Mon, Jun 30, 2014 at 1:23 PM, Christopher Robert chrislrobert@gmail.com wrote:
Okay, that's too bad.
We need to see everywhere these paths appear. If it's just a matter of
deleting and re-downloading form definitions, that's not too bad. But if the
paths are in the form instances themselves (even if just for media files),
then that would not be good.
Thanks,
Chris
On Mon, Jun 30, 2014 at 4:14 PM, Mitch Sundt mitchellsundt@gmail.com wrote:
Painfully, yes. ASUS Nexus 7 tablets.
Stumbled upon this during ODK 2.0 development last fall.
On Mon, Jun 30, 2014 at 12:52 PM, Christopher Robert chrislrobert@gmail.com wrote:
Thanks, Mitch.
Do we know of any devices that allowed users to update from 4.1 to 4.2+?
If not, this becomes purely a portability issue for data moved from one
device to another; the restriction becomes: for data captured on a pre-4.2
device, you can only use it on another pre-4.2 device, and similarly for
data captured on a 4.2+ device. That would seem like a restriction that most
people might be able to live within.
Bob, that would mean that you wouldn't need a device to perfectly match,
but one that's either pre-4.2 or 4.2+, depending on your data-collection
device.
Best,
Chris
On Mon, Jun 30, 2014 at 3:45 PM, Mitch Sundt mitchellsundt@gmail.com wrote:
Agreed. This is an issue when moving across Android 4.x builds. Google
changed the full ExternalStorage path from 4.1 to 4.2 in order to support
multiple user profiles on one device.
In the face of this, the recommended solution from Google is to store
only partial paths -- e.g., when saving filepaths in the database, start the
path from the 'odk' directory, instead of from /sdcard/...
This would change a bunch of things in ODK Collect, as there are places
where we search for the form by the full pathname
To truly fix this, ODK Collect would need to increment its database
version, and, in the onUpdate() method, it would replace all the full
pathnames in the database with paths relative to the 'odk/' directory.
There would be two new methods in FileUtils:
class FileUtils {
...
public static String asRelativePath(File file)
{
// strip off all directories before 'odk'. return 'odk/...'
relativePath.
}
public static File asFile(String relativePath) {
// prepend the ExternalStorage directory to the 'odk/...'
relativePath.
}
...
}
I am unclear if the relative path would also need to support '../' as
the first segment to handle arbitrary file placement within the sdcard. Not
sure what external tools might require that (e.g., clinic)
If anyone wants to sleuth through and contribute the code to handle
this, I'd fold it in.
Mitch
On Mon, Jun 30, 2014 at 8:57 AM, Christopher Robert crobert@surveycto.com wrote:
Hi Bob,
Just to cc: the community with our advocated approach: it seems like
editing paths in internal SQLite databases is dangerous. Rather, it seems
using a similarly-configured, similar-model device should use the same
directory structure and thus side-step this problem. Or, does anybody have
other ideas..?
Thanks,
Chris
On Mon, Jun 30, 2014 at 11:51 AM, bobachgill@gmail.com wrote:
I enumerated data on a Chinese Huawei model 3 phone then moved the
data to another phone by ... copying the /SurveyCTO directory to another
phone replacing the /SurveyCTO directory on the destination phone.
Everything is OK so far... All the same forms appear to be loaded both
in the Fill Blank Forms and Edit Saved Forms areas. Though when I try to
edit the existing form on the destination phone I get the error message that
the file does not exist... and it says some funny path like ...
"/storage/emulated/0" that clearly is not a ODK or SurveyCTO kind of path.
It's funny that I can see the title of the Edited form but when I try
to access it to edit it it can't find the file.
That bogus path is probably an artifact of the Huawei's management of
internal versus external memory. Somehow OKD/SurveyCTO stored the virtual
path and not the relative physical path.
Is there some file in the ODK/SurveyCTO data structure that I can do a
change all to fix the path to find the file(s)to edit?
Else, I will need to find that phone again just to retrieve the data.
Thanks!
Bob
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
... and relative paths sounds like it would open the door for having select-able instances of /SurveyCTO#001.
Some projects require a means to divide the forms up. With selectable instances the enumerator could just pick which project he/she is enumerating for this hour by selecting from a project list which points to the proper /SurveyCTO####. A relative path design would/could make it possible to be involved in enumerating on any global or business or hobby concern with out having to uninstall and re-install ODK and thereby wiping all the data from the other project.
Yes, that fits. The directory name changed between some version of 4.1 and
some version 4.2 (I think 4.1.2 and 4.2.1, but it has been a while).
···
On Tue, Jul 1, 2014 at 4:51 AM, wrote:
Thanks for your insights!
I am thankful not to lose the 30 man-hours that went into enumerating that
data.
CORRECTION: There were 5 people enumerating so that is 30hours x 5 = 150
hours saved!
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com