Now in beta: Event Form Editor

form-builder-GIF-with-Bg

Hi EarthRanger fam!

Excited to share that the EarthRanger Event Form Editor is now in beta! The team has worked hard for the last year+ to get Admins a customizable/flexible way to customize the data you are collecting (i.e. those Event forms).

newsletter

Drag and drop, no coding (no JSON!) required! The clean interface means your field teams can adapt faster to what’s happening on the ground, whether that’s a new species sighting…or whatever!

Log into the EarthRanger Admin site and look under activity to find “Event Types and Categories 2.0 (Beta)”.

More information here…BUT A recap…

What’s new:

  • Create and organize Event Categories and Types in minutes
  • Add choice lists, text boxes, locations, and dates
  • Group related info with nested collections
  • Set defaults, required fields, and visibility with a few clicks

A few things to know:

  • Only v2 Event Types (created in the EFE) can be edited. v1 Event Types can’t be changed in the new editor.
  • There’s no versioning yet. Any changes our partners make could affect both new and existing events of that type.
  • If our partners delete or modify a field, related data in existing records might be hidden or lost.

As always, let us know what you think!

Hi ER, this will make event building much easier for other team members!

In a V1 event, I have source id as a dropdown selection option

            "type": "string",
            "title": "Unit ID",
            "enum": {{query___source___values}},
            "enumNames": {{query___source___names}} 

Can that also be added for V2? I see subject group selection and users in the ‘my data’ option, but not sources.

Thanks!

Hi Courtney,

Yes one should be able to use existing choices with the Form Builder as well.

To do this, select the “Existing Choice List” option next to the “My Data” option. With the next field you should be able to select an existing choice list value, in your example “source” should be an option.

Please let us know if this does not work for you.

Regards
Dewald

Thanks @Dewald, but “source” is not in the existing choice list, because it is not a choice of its own but I believe being queried directly.

For example, those fields called from my choice list are referenced in v1 like this (“enum”)

        "giraffe_sex":{ "type": "string",
		"title": "Giraffe sex",
        "enum": {{enum___sex___values}},
        "enumNames": {{enum___sex___names}}

but the source list is referenced like this so it always shows the up to date list (“query”)

            "unitupdate_unitid": {
            "type": "string",
            "title": "Unit ID",
            "enum": {{query___source___values}},
            "enumNames": {{query___source___names}} 

I would to reflect this same structure so I don’t have to add a unit ID to a choice list every time there’s a new one (there are many).

Thanks!
Courtney

Hi Courtney,

I am reaching out to you on email to discuss Dynamic Choices and the new Form Builder in more details with your use case.

This makes building events a lot easier. The “Create New Choice list” feature is not working as expected. After creating the new choice list one has to delete the dropdown list and then create it again.
Then a question, is there an option to create a button based data collection workflow? This would assist pilots for rapid data collection.
Thanks for the improvements.