A way to implement a safeguard/flood control for issuing same badge accidentally
-
Many of my users end up submitting the same badge submission multiple times in a row by spamming the submission button. This results in their submission showing up multiple times in the submission queue (even if the badge has a submission limit they’ve exceeded).
Usually, I notice this and delete the extra submissions – no big deal. But occasionally, I’m reviewing submissions too quickly and accidentally award the same badge to the same user twice. If I happen to notice this fact, I can of course manually revoke the badge – but that’s problematic as I often *don’t* notice, and if I do, I then have to remember to also manually subtract the points earned since revoking a badge doesn’t subtract the corresponding points.
Certainly a minor annoyance; however, I’m wondering if there’s an easy way to build in a safeguard? I see three possible solutions:
– as soon as a user hits submit, some kind of “submitting, please wait” message appears so they know they’ve successfully hit the button (I think most duplicate submissions are because their attachments are loading and they’re being too impatient) … this solution would not eliminate all instances of this, but would certainly help
– some kind of flood control that blocks multiple submissions on the same badge (within a given time period?)
– if not possible to deal with it on the submitting end, on the reviewing end we’d need some kind of ‘user has already earned this badge today – are you sure you want to award this badge again?’ prompt if the user already has the badgeThoughts?
- The topic ‘A way to implement a safeguard/flood control for issuing same badge accidentally’ is closed to new replies.
