Change Trap number/code field to SITE number/code

Feature Requests
#1

The “Trap number / code field” would be so much better being renamed “Site Number/Code” and an additional field named “Trap ID”
Once again we have had people move traps, but instead of retiring the old site and adding a new one, they just move the trap on Trap.nz

Trap Removed Category
#2

Great idea :blush:. Up until now often when the traps are moved to a completely different location the trap has kept its original code. Keeping the trap code is fine when replacing the trap at the location, like for like, but not for when moving it to a new location.

1 Like
#3

I love the idea of a separate Trap ID field! I’ve been looking for a way to track which traps were donated by/inherited from which organisation (especially the ones that are on loan, e.g. from trap libraries). So far the only workaround I’ve found is to use the notes and/or tags fields, but then if that trap is pulled out and replaced with a new one from a different source there will be no prompt to update.
Without a Trap ID, there’s no way to track the physical trap’s data over time - for instance, did this trap have good kill rates at its previous site, has it been amazingly scent-marked, was it at a coastal site and might have a shorter lifespan, are there biosecurity concerns in the area like kauri dieback or myrtle rust…

1 Like
#4

If we are talking about an ID specifically for the hardware, the QR / NFC uuid should serve this purpose.

The uuid isn’t advertised, or searchable yet. We can look into that, no promises on timing :slight_smile:

Andy

1 Like
#5

I am sorry - But that is all gobbly gook to me. The problem is the trap.nz field name <Trap number / code> is inaccurate as it references a site position NOT a movable trap - Causes heaps of confusion. Solution is to rename the field as SITE or LOCATION number/code and add a trap ID code - so if a trap is moved to a different SITE it can be traced …
We could have SITE 10 with trap#xyz. Then we may retire SITE10 and move trap#xyz.to SITE13. I am not software developer, so what seems simple to me probably means a year of headaches to someone else :slight_smile:

#6

@faith I think Andy’s suggestion is that the existing “uuid” field could be developed to become the Trap ID field - currently that’s where the info for the QR codes and/or NFC tokens goes, and those IDs are often attached to the physical trap rather than the site. Once that field has more functionality (e.g. being searchable), then there will be two ID fields and it will be possible to differentiate the site name from the trap name.

1 Like