Prevent duplicate applications

[jcn]

My idea is to basically do a basic search against name, email, phone number, and description fields within a time frame - if they're the same, that should be enough to prevent duplication. Also, we can add a state to disable the submit button after it's been clicked.

[JoelPomerantz]

Since duplicates arrive seconds apart, it's clear that the problem is clicking the "Apply" button more than once out of impatience, slow connection, etc. The simplest short term solution is to change the label on the Apply button. "Apply (Do not click a second time - wait 1 minute then check your email)." If this works, there's no need for anything fancy.

[tibbon]

I'm thinking of putting in a unique composite index in the database to prevent dupes.

Instead of returning an error if they click it a second time, I'm thinking of changing the action to create or update if there's already one like that, so if they do submit a second time, it just updates the application.

[jcn]

@tibbon I think the best thing to do first would be a javascript-y thing that disables the submit button after it's been clicked. That should cut down on a lot of it.

I've got a (possibly unwarranted) concern about doing the restriction by index as I'm afraid it might actually be too heavy a hammer to hit this problem with, but it could be the right thing. I'd have to see the code. But a first stab would definitely be the JS solution and see what that takes care of.

[MicFin]

This is an interesting problem. I would like to take a look at the JS solution and see if that is sufficient.