Comment 2 for bug 1915274

Marking this as a wishlist item, and noting that there are some lurking implementation dragons, including:

- If we add a constraint, dealing with existing vendor codes that would violate that constraint during upgrade
- warnings and/or reports of overlapping vendor codes would be easier to implement, but wouldn't provide as strong a guarantee as a database constraint
- Discussing consistency with the rest of Evergreen, since at present there are no coded fields to my knowledge that have a case-intensive uniqueness constraint. There are other bugs requesting that certain fields be made case-insensitive, e.g., bug 1744153 (usernames), bug 1548328 (circ modifiers) bug 1869896 (barcodes, although I think dragons _really_ reside there). There are also several bugs requesting case-insensitive filtering and sorting, although that's really a different class of issues.

Upshot: I'm sympathetic to this idea, but I think it would warrant broader discussion.