Hi All,
I have a group of users that went out to collect data but used an old
version of a particular form. They send the data in and it goes into
different fields on the new form. Is there any workaround fixing this? They
issue here is the users can't go back to the field to get the data as it
is very remote, so my best bet now is to extract data from the old forms.
Kind regards
Adah
Adah,
I would probably just note those instances as different and tweak them
when you export your data into your analysis tools. Only other option
is to mess with the data in the database (not recommended) or dump all
the data with Briefcase, make the changes in the XML to fit whatever
form version, and re-upload them (not recommended either) to
Aggregate. Next time, use new form ids when updating forms.
Yaw
···
--
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
On Thu, Aug 7, 2014 at 6:33 AM, Adakole Kennedy akennedy@camfed.org wrote:
Hi All,
I have a group of users that went out to collect data but used an old
version of a particular form. They send the data in and it goes into
different fields on the new form. Is there any workaround fixing this? They
issue here is the users can't go back to the field to get the data as it is
very remote, so my best bet now is to extract data from the old forms.
Kind regards
Adah
--
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.
Reiterating what Yaw says:
-
Change the formID whenever you change the meaning of a field in that form.
-
Use the same formID only if you are simply changing the wording of the
questions in the form. In that case, use the version field to track each
such revision to the form.
These are central assumptions for ODK Aggregate. Other systems, such as
FormHub, are more flexible -- allowing you to jumble several different
meanings into one "formID" bucket, but requiring you to tease out the
different meanings in your post-processing -- the task you now face.
Unfortunately, the untangling of multiple meanings is so complex and
form-specific, we see no way to provide generic tools to assist with it,
and instead structured our usage assumptions and the design to explicitly
avoid facing this problem.
Good luck,
Mitch
···
On Thu, Aug 7, 2014 at 8:30 AM, Yaw Anokwa wrote:
Adah,
I would probably just note those instances as different and tweak them
when you export your data into your analysis tools. Only other option
is to mess with the data in the database (not recommended) or dump all
the data with Briefcase, make the changes in the XML to fit whatever
form version, and re-upload them (not recommended either) to
Aggregate. Next time, use new form ids when updating forms.
Yaw
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
On Thu, Aug 7, 2014 at 6:33 AM, Adakole Kennedy akennedy@camfed.org wrote:
Hi All,
I have a group of users that went out to collect data but used an old
version of a particular form. They send the data in and it goes into
different fields on the new form. Is there any workaround fixing this?
They
issue here is the users can't go back to the field to get the data as it
is
very remote, so my best bet now is to extract data from the old forms.
Kind regards
Adah
--
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 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
Thank you very much yaw for this.
Kind regards
Adah
···
On Thursday, August 7, 2014 4:31:27 PM UTC+1, Yaw Anokwa wrote:
>
> Adah,
>
> I would probably just note those instances as different and tweak them
> when you export your data into your analysis tools. Only other option
> is to mess with the data in the database (not recommended) or dump all
> the data with Briefcase, make the changes in the XML to fit whatever
> form version, and re-upload them (not recommended either) to
> Aggregate. Next time, use new form ids when updating forms.
>
> Yaw
> --
> Need ODK services? http://nafundi.com provides form design, server
> setup, professional support, and software development for ODK.
>
> On Thu, Aug 7, 2014 at 6:33 AM, Adakole Kennedy <aken...@camfed.org > wrote:
> > Hi All,
> >
> > I have a group of users that went out to collect data but used an old
> > version of a particular form. They send the data in and it goes into
> > different fields on the new form. Is there any workaround fixing this?
> They
> > issue here is the users can't go back to the field to get the data as it
> is
> > very remote, so my best bet now is to extract data from the old forms.
> >
> > Kind regards
> >
> > Adah
> >
> > --
> > --
> > 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.
>
Thank you Mitch, I am going to download a backup of our db and see if I can
dig up the XML file. Just to see the structure of the form itself.
Many thanks
Adah
···
On Thursday, August 7, 2014 7:59:30 PM UTC+1, Mitch Sundt wrote:
>
> Reiterating what Yaw says:
>
> * Change the formID whenever you change the meaning of a field in that
> form.
>
> * Use the same formID only if you are simply changing the wording of the
> questions in the form. In that case, use the version field to track each
> such revision to the form.
>
> These are central assumptions for ODK Aggregate. Other systems, such as
> FormHub, are more flexible -- allowing you to jumble several different
> meanings into one "formID" bucket, but requiring you to tease out the
> different meanings in your post-processing -- the task you now face.
>
> Unfortunately, the untangling of multiple meanings is so complex and
> form-specific, we see no way to provide generic tools to assist with it,
> and instead structured our usage assumptions and the design to explicitly
> avoid facing this problem.
>
> Good luck,
>
> Mitch
>
>
>
>
>
>
> On Thu, Aug 7, 2014 at 8:30 AM, Yaw Anokwa <yan...@nafundi.com > wrote:
>
>> Adah,
>>
>> I would probably just note those instances as different and tweak them
>> when you export your data into your analysis tools. Only other option
>> is to mess with the data in the database (not recommended) or dump all
>> the data with Briefcase, make the changes in the XML to fit whatever
>> form version, and re-upload them (not recommended either) to
>> Aggregate. Next time, use new form ids when updating forms.
>>
>> Yaw
>> --
>> Need ODK services? http://nafundi.com provides form design, server
>> setup, professional support, and software development for ODK.
>>
>> On Thu, Aug 7, 2014 at 6:33 AM, Adakole Kennedy <aken...@camfed.org > wrote:
>> > Hi All,
>> >
>> > I have a group of users that went out to collect data but used an old
>> > version of a particular form. They send the data in and it goes into
>> > different fields on the new form. Is there any workaround fixing this?
>> They
>> > issue here is the users can't go back to the field to get the data as
>> it is
>> > very remote, so my best bet now is to extract data from the old forms.
>> >
>> > Kind regards
>> >
>> > Adah
>> >
>> > --
>> > --
>> > 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.
>>
>> --
>> --
>> 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
>