Hi, just after thoughts and advice when making changes to existing trap installations.
I have 2 examples to consider. In both cases, I am looking for suggestions on how to handle the changes on the ground when updating Trap.NZ, in order to get the best results out of reporting and data analysis.
Example 1: Trap location is not changing, trap type is
We have a bunch of T-rex rat traps in corflute tunnels that are under-performing. On my last check, every single one of them was “not sprung, bait missing”. During this run, I replaced every other one with a Victor professional trap. Should I edit the existing traps to reflect the new trap type? Or should I retire the existing trap and add a new one with the same location?
Example 2: Trap location is changing, new trap going where the trap was
Today I put out 10 DOC200s at 50m spacing. The intention is that these will end up at 100m spacing, with a rat trap in corflute tunnel going inbetween. The DOC200s that get removed will end up on a parallel line with the same alternating pattern of DOC200s and rat traps at 50m intervals. When making this change, should I retire the DOC200s that are being moved? Edit these trap installations to reflect the new trap type? Or edit these trap installations to reflect their new position?
Any thoughts welcome, I just am hoping that whatever I do, the trap reporting will remain useful.
@integersmirk for your example 1 I think it would probably depend how you want to look at the trap performance over time. If you use the Trap records with map report, editing the trap type lets you keep the running total of catches for the tunnel location going, while retiring it gives you two traps at the same location with the newer one starting its count at zero. This can be frustrating if you want to look at pest hotspots over the life of the whole project, and especially if half the traps are suddenly at zero while the other half aren’t! On the other hand, I don’t know whether editing the trap type will propagate back through older records - if so, this could be a problem later if you want to look at the catch rates for T-rex vs Victor.
For example 2 - definitely retire the trap. If you move the trap location via the app, it will automatically retire the old location and create a new trap as part of the move, no extra effort required. If you’re editing on the website and change the trap location, it will apply the new location to all earlier records too, and all your past catches will appear as if they are made at the new location, which is not useful for the reports!
If you have a usual set of reports that you run, you could try creating some ‘dummy records’ with made-up traps, try both edit methods on them, and then run the reports to check how the changes compare. When you’re done testing you can then just delete the fake records/traps again without having to worry that you might be affecting your real dataset.
In both cases retiring and creating a new one is the correct approach IF trap records exist. If they don’t it doesn’t really matter.
Traps entities are the combination of trap type + trap location. Christina’s hunch is correct, records derive their trap type from the associated Trap entity at reporting time. If you change it, all historical records will report as the current type. You don’t want that.
Andy
1 Like
Thanks Andy, that’s perfect.
Are the unique requirements for trap codes limited to active traps?
Or will I need to use a different trap code for the new trap entity?
Cheers
Mike
@integersmirk as you are retiring the original installation, the new trap can use the original code, (it only becomes confusing when you have multiple active installations with the same code) If you want to refer to the retired installation it will show with (retired) beside it in your “manage” section on the website.