Allow "Replace" option when recording a second trap record shortly after a previous one

Feature Requests
#1

User story
As a trap.nz app user, when adding a second new trap record shortly after saving a first one, I would like to be able to choose whether the second record entered should be in addition to the first, or to replace it.

Background
When using the trap.nz app, if you attempt to log a new trap record shortly after a previous one, a feature exists that prompts the user with the message “This installation has already been serviced today…”

As a user, the most common time I encounter this message is when I have realised that my first trap record was incomplete or inaccurate, and I am deliberately lodging a new record that is an improvement on the first. In this case, a much better outcome would be to allow me to choose “Replace” as one of the options, which would result in the previous trap record being deleted as well as the new record being saved.

Requirements

  1. When a user attempts to submit a new trap record that triggers the warning above, and the data that has triggered the message includes data has been submitted by the same user, modify the warning message as follows:
    a) The description includes “Choosing REPLACE will delete your last record and save this new one instead”
    b) “REPLACE” is an option on screen
  2. If a user chooses “REPLACE”, their new record is saved and their last record is deleted

Acceptance criteria
When I see the “installation already serviced” warning, and I have not logged any data with my username in the warning period, the warning message is unchanged from the current one.

When I see the “installation already serviced” warning, and I have logged data with my username in the warning period, I see the modified warning message.

When I choose REPLACE on the modified warning message, my last trap log is deleted and the new one is created.

When I choose SAVE or CANCEL, the existing behaviour is unchanged.

#2

Good idea @integersmirk! Less-confident users usually don’t go back through the website to delete their own duplicate records, and as an admin it’s quite time-consuming to clean up duplicates when someone’s entered a series of 3 or 4 entries, all slightly different. Data quality is much better if the person in the field can fix errors!

#3

I’d also love to see this implemented, its very easy to make duplicate records especially on big networks with dense traps on the map

1 Like
#4

Yes, I would also find it very useful to have that option and it would save time going back to the website to find and remove that incorrect record.

#5

Good idea or just be able to EDIT and have a revision that you can switch back to.