Repeat in the same form like more forms

Support
11

Hi @giulia_tomasi
Maybe, some additional hints are helpful:

  • Did you test the mapping already? (The ODK map feature might not work as the geopoint is inside repeats now)
  • As you use "start" type, this will be set on first load of the form and never change and is invisible. So, time_specie will always stay the same, as long as you use one form. You might use once(now).
  • today metadata is the date of the first load and will not change. But today() function will always update when you open/edit the form, even later on server level. You might better use once(today()).
  • Avoid spaces in choice names (use _).
  • Better replace type "photo" with the official type "image" and "autocomplete" with search appearance (see new ODK XLSForm template).
  • The structure with the double nested repeats might be critical for the user to handle, as there are two +/- buttons with different meaning.
  • The nested inner repeat only makes sense if you often have multiple species at an identical location and an identical time to enter.
  • Review, please, how the date/time and location should best be related. At the moment, if the user needs to change one of both, she/he has to start a new outer loop.
  • The same form might be used more than one day, so your dates may need to allow more than one day. (Or the user shouldn't do this.)
  • How do you want to register the same species at the same location-time? Only once? With a number? At the moment you could create multiple repeat cases.
  • required no is not needed, this is the default.
  • Use and train the options for GPS improvement, see https://docs.getodk.org/collect-location/#improving-location-performance.
  • Make sure that data, time and timezone are configured correctly on each used device.

Now the form structure is oriented to one day with different location-time, and multiple species there (grouped as inner repeat by same location and time!). Nevertheless, a user may submit more than one form for the same day. You probably need good enumerator training and guideline, to avoid differently "packed" submissions, creating challenges for data analysis.

There might be other design options:

  • One form per location, with multiple species (different times?)
  • One form per species case (spotting), with last_saved value import, e.g. for location.
  • One form (specie or species), with entity reference (e.g. location).

Perhaps, for digging deeper for species surveys, also some of the showcases may be interesting for you, esp.

1 Like