I had an issue where I removed a xml file from the Aggregate server and I
re-added it. The file was the same name but the file actually is not the
same, if you look at the server there are some numbers after the file name
Thanks,
Alex
If the data being collected by the form changes materially (e.g., new
questions, removed questions ), the id of the form should be changed. If
you simply delete the old definition and upload the new definition in its
place, when users submit data filled out will the old definition of this
form, ODK Aggregate will assume it was filled out using the new definition
and attempt to interpret this submission using that newer form definition
-- matching tag names in the submission to tag names in the form
definition. This may or may not yield any meaningful results for you.
Note that ODK Aggregate does not run any relevancy or constraint tests when
it processes a submission, it just matches and stores the submitted values.
The support added in ODK Aggregate 1.1 will allow updates to forms with no
material changes to the data being collected (e.g., changes to question
text, additional translations).
Mitch
I had an issue where I removed a xml file from the Aggregate server and I
re-added it. The file was the same name but the file actually is not the
same, if you look at the server there are some numbers after the file name
- the database also created a new table. I assume that users in the field
can not submit data collected using the old xform to the new xml file. How
can I proceed if the field teams already collected data with the original
xform?Thanks,
Alex--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Great! Nothing was changed. The form was simply removed from Aggregate
and re-added without any modification. I will have the teams attempt to
send the data using the original survey and let you and the group know how
it went.
Thanks,
Alex
If the data being collected by the form changes materially (e.g., new
questions, removed questions ), the id of the form should be changed. If
you simply delete the old definition and upload the new definition in its
place, when users submit data filled out will the old definition of this
form, ODK Aggregate will assume it was filled out using the new definition
and attempt to interpret this submission using that newer form definition
-- matching tag names in the submission to tag names in the form
definition. This may or may not yield any meaningful results for you.Note that ODK Aggregate does not run any relevancy or constraint tests
when it processes a submission, it just matches and stores the submitted
values.The support added in ODK Aggregate 1.1 will allow updates to forms with no
material changes to the data being collected (e.g., changes to question
text, additional translations).Mitch
On Wed, Jun 27, 2012 at 7:55 AM, Alex Pavluck apavluck@gmail.com wrote:
I had an issue where I removed a xml file from the Aggregate server and I
re-added it. The file was the same name but the file actually is not the
same, if you look at the server there are some numbers after the file name
- the database also created a new table. I assume that users in the field
can not submit data collected using the old xform to the new xml file. How
can I proceed if the field teams already collected data with the original
xform?Thanks,
Alex--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en--
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