Filter for Ready to Send and Sent Forms in Collect

What high-level problem are you trying to solve?
Making it easier for enumerators to find specific forms the've already finalized that are to be sent, or already sent in order to edit.

Any ideas on how ODK could help you solve it?

Upload any helpful links, sketches, and videos.
Imagine you are an enumerator and you've just filled out X number of forms, but you realize one of your forms has an incorrect ID number or something else that is fairly significant that they know the incorrect and the correct value that it needs to be changed to.

In Collect, when tapping the sent button the enumerator is greeted by nearly identical forms that have just been sent with no way of easily distinguishing between each one besides tapping each one and sifting through to find the correct one. I see that forms can be sorted and the search can be used, but what fields is that search limited to? My assumption is that it is limited to the form Title.

In my recent case I had about 80 submissions that all look like this:

I'm proposing a way that the search could actually be used to look for data inside forms so that in this example an enumerator could enter the ID number they know is incorrect, which would bring up any associated surveys with that ID number. I don't know how much others are interested in this, but for my particular case if the search had access to all the forms data, an ID number would be fairly good at limiting the results to only those that contain that string in any response. My most recent case I needed to change 160 to 161 in a field that was inside a group so I had to do 2 taps deep to determine if that form was the correct one or not. When all the forms were sent at nearly the same time, this becomes difficult to keep track of which forms you've already checked vs haven't checked yet and it would be easy to accidentally skip one.

If you wanted to get fancy, you could have an advanced search where an enumerator could select from a list of unique forms on the device, and by tapping on that form, it would open up the list of potential questions from that specific form and the enumerator could then pick the specific question/field that they knew what they are searching for would be in. This list would display the Label names to the enumerator. I'm not proposing anything fancy, but just throwing out ideas.

Can you explore the possibility of dynamically naming the filled forms/drafts by concatenation of questions within the form for easy identification and search. I think this approach may serve your intended purpose. Use the instance_name on settings tab to define the unique submission name.

1 Like