We'd like to have a sequential identifier but I don't think it is possible
given that each record is its own XML file, rather than a row in a table.
We also wanted to be able to pull data from one form's results into the
choices domain in another form. For example, I would have a form "subjects"
for subject characteristics, including "common_places" (e.g., home, mom's,
sister's, Trader Joe's). There would need to be only one record for that
form since those characteristics would be immutable over the course of the
1 seek survey.
The "places" form would optimally have its place names choices populated
from subjects.common_places. I also gather this is not possible though it
seems to be suggested by developers for a future revision.
You can't do cross form stuff in the ODK Collect, but a dev could add
this functionality pretty easily. Alternatively, you can wait for ODK
Survey to ship. I believe it'll have some of this functionality.
Yaw
···
--
Need more help? Go to http://nafundi.com for custom development,
professional support, form design, implementation advice, and user
training for ODK.
We'd like to have a sequential identifier but I don't think it is possible
given that each record is its own XML file, rather than a row in a table.
We also wanted to be able to pull data from one form's results into the
choices domain in another form. For example, I would have a form "subjects"
for subject characteristics, including "common_places" (e.g., home, mom's,
sister's, Trader Joe's). There would need to be only one record for that
form since those characteristics would be immutable over the course of the 1
seek survey.
The "places" form would optimally have its place names choices populated
from subjects.common_places. I also gather this is not possible though it
seems to be suggested by developers for a future revision.
If you need a sequential identifier, you could change the construction of
the meta/instanceID to be something like timestamp + deviceid. And have a
separate form for each entry in the diary.
The deviceid would enable you to record separate streams of commentary from
multiple devices at the same time without concern for the slight chance of
two devices making an entry at exactly the same moment in time.
Mitch
···
On Sat, Feb 9, 2013 at 8:46 AM, Yaw Anokwa wrote:
You can't do cross form stuff in the ODK Collect, but a dev could add
this functionality pretty easily. Alternatively, you can wait for ODK
Survey to ship. I believe it'll have some of this functionality.
Yaw
Need more help? Go to http://nafundi.com for custom development,
professional support, form design, implementation advice, and user
training for ODK.
We'd like to have a sequential identifier but I don't think it is
possible
given that each record is its own XML file, rather than a row in a table.
We also wanted to be able to pull data from one form's results into the
choices domain in another form. For example, I would have a form
"subjects"
for subject characteristics, including "common_places" (e.g., home,
mom's,
sister's, Trader Joe's). There would need to be only one record for that
form since those characteristics would be immutable over the course of
the 1
seek survey.
The "places" form would optimally have its place names choices populated
from subjects.common_places. I also gather this is not possible though it
seems to be suggested by developers for a future revision.
Or just leave everything the same and have 3 properties in the form --
start time, end time, and deviceid, then do all your sorting and processing
based upon the start time. See the bottom of the examples page
for the properties you can define in a form.
Mitch
···
On Mon, Feb 11, 2013 at 9:21 AM, Mitch S wrote:
If you need a sequential identifier, you could change the construction of
the meta/instanceID to be something like timestamp + deviceid. And have a
separate form for each entry in the diary.
The deviceid would enable you to record separate streams of commentary
from multiple devices at the same time without concern for the slight
chance of two devices making an entry at exactly the same moment in time.
You can't do cross form stuff in the ODK Collect, but a dev could add
this functionality pretty easily. Alternatively, you can wait for ODK
Survey to ship. I believe it'll have some of this functionality.
Yaw
Need more help? Go to http://nafundi.com for custom development,
professional support, form design, implementation advice, and user
training for ODK.
We'd like to have a sequential identifier but I don't think it is
possible
given that each record is its own XML file, rather than a row in a
table.
We also wanted to be able to pull data from one form's results into the
choices domain in another form. For example, I would have a form
"subjects"
for subject characteristics, including "common_places" (e.g., home,
mom's,
sister's, Trader Joe's). There would need to be only one record for that
form since those characteristics would be immutable over the course of
the 1
seek survey.
The "places" form would optimally have its place names choices populated
from subjects.common_places. I also gather this is not possible though
it
seems to be suggested by developers for a future revision.