kazlauskis
commented
1 year ago OK, we can think of something.
The moth trap survey has a date field in the app. This field is prefilled to the current date when the record is created. I've checked it on the website, and it says "Please enter the date the trap was set (turned on)". Since most users will enter the moth trap data the following day it was set, then prefilling it to the current date is incorrect. Can we set the record's date to yesterday by default instead?
To capture the moth trap period spanning more than one night, you essentially want the date the trap was set up and the number of nights the trap was out. I suggest defaulting the trapping days field to 1 and keeping it hidden unless the user selects a trap set-up date to something older than yesterday. This way, the new field would be hidden for most users, but for those who want to trap for more than one night, it would allow them to enter that. Would that be OK?
larspett
ButterflyCount needs an option to allow moth trapping period to be more than one night. Trap periods spanning more than one night are common in standardised moth monitoring - traps are often kept a few days between emptying during less intensive flight periods. Not having this option will make users add data from multiple nights as one night. This will result in incorrect moth densities.
I do realise that this could complicate weather details but then again, weather info could simply be omitted when more than one night is used.