ODK Collect: Time in Repeat Changes on Submit

1. What is the problem? Be very detailed.

We use ODK Collect with a form on a Google Drive. The form has a repeat question that asks for the time of an observation. If the data of a form is edited, specifically, if one of the repeats is deleted prior to sending the form, the recorded time for all the repeats is shifted +1 hour for all the repeats in that form. That is, if we check the Google Sheet that receives the data, as well as on the device in the "Sent Forms" the time is changed. The change only happens upon send, and it does not happen if repeats are not deleted.

2. What app or server are you using and on what device and operating system? Include version numbers.

ODK Collect v1.22.4 and Google Drive

3. What you have you tried to fix the problem?

We have a "test" entry that we can use to not have to delete entries of the repeat.

4. What steps can we take to reproduce the problem?

Build a form with a repeat questions that asks for the time, then delete repeats before sending.

You can also use our form and sheet. In the latter case, you will have to upload the Excel file as a Google Sheet to a Google Drive of your choice. Then adapt the submission URL on the settings sheet accordingly.

5. Anything else we should know or have? If you have a test form or screenshots or logs, attach below.

Excel sheet
XForm definition

Many thanks for your help! Also, ODK Collect is great and will streamline data collection greatly, even if the described behavior persists.

Hi @Roger welcome to the forum! Please introduce yourself here!

I tried reproducing the issue you're having but it looks like the form needs a .csv file to pull bee-ids from. Do you have an example of that?

Thanks for looking into this. I indeed forgot to add this csv file. Here it is:

CSV File with Bee IDs

Note that this resides in a subfolder of the Google Drive folder where the form is stored. The name of the subfolder is bees-neonic-visits-odk-media.

Oh, and I introduced myself in the thread you linked. Many thanks again!

@Roger really sorry for the late reply! I'll a look at that and see if there is anything I can understand from it.

@Roger sorry I'm having some problems filling in the form. Could you give me some exact steps to get to the problem you encountered (i.e what questions to fill in and what to fill them in with etc)?

Hi @seadowg! Thanks for looking into this ... What problem do you encounter when entering the form?

After downloading the form to ODK collect, we go to "Fill Blank Form". There we set the phase of that particular experiment, and the date for the observations that are to follow. Then we swipe from right to left to get to the actual data, which is implemented as a repeat. We need to pick a feeder, an observation time (in my case it is 14:03 now), and any bees that have visited the feeders, let's say "Test Bee". Now, we swipe left again, and we are asked to add another group, and we add a second group. The next time, instead of adding another group, we finalize and save the form. Now I go to "Edit SavedForm" where I select the form that I just filled in. I go to the "Visitation Repeat", select the "2. Visitor Information" (the time here is still correct), and I delete that. Then we save and finalize the form again. Now I go to "Send Finalized Form" and send the form I just edited. Now I go to "View Sent Forms" and select the form I just sent. This brings me to the date and experimental phase screen. I hit the "up" arrow at the top right corner to get to the page where I can select the "Visitation Repeat". Looking at the "1. Visitor Information", I now see that the observation time has shifted by 1 hour (i.e., it now says 15:03), and that is how the form's data are saved to the Google Sheet, too. So, only for edited sheets, upon sending the sheet the time is changed.

These times are essential for our data analysis, so it is lucky that we caught the shift, and we could reconstruct the original times so far. But it would be great if we could understand (and hopefully fix) what the underlying cause is.

P.S.: Is there an easy way to make screen casts of Androids? If so, I could demonstrate our particular case.

I ran through this with my Collect pointing at an Aggregate server and couldn't reproduce but I'll have a look at Google Drive once I set that up for myself.

I've also asked if someone can help out with how to do a screencast :grin:

@Roger I can't seem to reproduce this on Google Drive either. The times come through fine for me.

I'm interested to see if there's any possibility this could be a timezone issue: what timezone is your phone (the one with Collect installed on) set to?

That is odd, we have at least 3 phones that had the issue. We are in the Eastern US, so it is set to that time zone.
We also had more hourly shifts if more than one observation was deleted, so I am not sure how the time zone would play into that. Is your ODK Collect app the same version?

Yeah tried on 1.22.4. Was just hunch that it could be a programming error in Collect relating to timezones but I don't think that's right. I can't seem to reproduce it but going to see if anyone else can have a look.

@Roger @seadowg
I was able to reproduce the issue so I'll try to figure out what's going on or what kind of sorcery it is.

2 Likes

Thanks @Grzesiek2010 and @seadowg for your continued efforts to find the cause of this. In the meantime, we still collect data with the app, and it is awesome to just run it through the prepared scripts and getting live updates! :smiley: