Checkout: Shouldn't Be Able to Create Duplicate Loan Records

Actually, I'm closing this as a duplicate of . I don't think there is value in keeping them both around.

Looks like we sort of half completed this. I now get an error when I try to check out an item that is already checked out, but it's ugly and we want to replace it with the validation messaging described in this story. See for details on the error displaying.

Right, I didn't expect you to since it has no UX implications, I think. I just mention that choice to indicate how the front-end part of this depends on the back-end implementation.

Good point. I don't actually care if the validation comes before or after attempted selection. I think you guys should decide what makes sense.

Originally you could make multiple checkouts of the same item and then multiple check-ins of the same item (i.e. until all of them were gone). For a while, I have not been working in that area, but the described behavior is what we've had from the beginning, based on my recollection from extensive testing before review meets back then.

IMO, the right way to go about this, is to make sure the back-end prevents duplicates, no matter what the UI does. With that in place we can make the front-end behave user friendly, whether by forwarding an error message from the back-end as the back-end rejects the check-out request (i.e. "Item is not available for checkout") OR by having the UI make a validation request up-front, before attempting to submit the check-out. From a UX perspective the two approaches (fail on submit, or check pre-submit) probably appear exactly the same in this case, since there's only that one field and a submit button.