I noticed today that when I run the ‘Trap Records’ report with status ‘sprung’ to see which lures are having success, many of the records have “none” in the “initial bait” column. As far as I can see, this is happening when the trap was not relured on the previous visit.
I had thought that when you enter a trap record and select that the bait is OK and you haven’t relured, the lure type from the previous visit would automatically carry over to all following visits till you either relure or have missing bait, but it looks like that isn’t what’s been happening!
Is this a user error, where I should be doing something differently when I enter my data and it’s caused the lure to enter incorrectly as “none”, or is it a software issue?
@christina.g looking at the records it is predominantly one of the members who is getting this in the records. It would be good to see what their trap.nz practise is and why this is showing in their records. If you’d like to know more contact me on support@trap.nz
In case anyone else is having this issue, my current work-around is to manually edit any lure types of “none” back to what they should be. In order for this to propagate into later records, though, I have to perform some kind of edit/save combination with each newer record - even if it’s just opening the record in ‘edit’ mode and then saving without making any changes. Otherwise the ‘previous bait type’ field stays as ‘none’.
I still don’t know why adding a “bait OK”/“not relured” combo in new catch records is giving me a default lure type of “none” instead of autofilling from the previous record, though. @lenore-admin, unfortunately the app changes I mentioned in my email don’t seem to have fixed the issue after all - the ‘lure type’ box is hidden now, but not-relured records still have a lure of “none” when I check them on the website.
@christina.g the previous bait type - none, was a bug and a fix has been released this week for it so it should now show the correct previous bait type
Thanks @lenore-admin! I see the fix for previous bait type.
I’m still getting a default lure type of “none” when I enter new not-relured data, though, which means that the ‘previous lure type’ field is only carrying through one visit before it gets overwritten by the ‘none’ lure type in the following record. With the traps that have long-life lures, it’s common to have several visits in a row where I don’t need to relure, so how can I get new records to autofill the lure type from the previous visit into the ‘current lure’ field as well?
I’d especially like the lure type to autofill when I enter multiple no-catch/not-relured records for a whole line through the add-catches website interface. I’m mostly using this feature for other people’s data, and the form keeps defaulting the lure type to “none” whenever I leave it blank. Is there a way I can get rid of that default? If I have to look up the previous visit’s lures for every trap before I can enter the new visit data, and then re-enter up to 6 different multi-lure combinations per line plus any lure notes, that’s a lot of extra time spent compared to being able to select the whole line and add “bait OK” “not relured” to all traps at once!
You are correct, what we should be doing is automatically pre-filling the bait type from the previous record automatically instead of defaulting it to “None”. I have made a task in our system to do this once we have secured funding to be able to work on it.
In the meantime I’m afraid you’ll need to manually select the bait/lure when you add a new record. I understand that is annoying when you need to do that for multiple traps. Hopefully you know which lures are used with each trap, in which case you can use the Add Catches page and select a default value in the Rebaited with selection and apply that to all the traps in the list. Then make sure to un-tick the traps which don’t use that lure, or manually change the ones which need a different lure.
