This one is fun... You can input randomly cases branchcodes via the API for patrons without receiving an error. This appears to be because sql's foreign key constraints aren't being triggered. This is fine in the database, but as soon as we start returning the data via API javascript is case sensitive in the UI and can crash To replicate, try adding a library with the code `CAPITALS` and then add a user via the API with a library_id of `Capitals`. If you then search for that user, the patron search table will fail to load and you'll get errors in the console.
I think the only workaround is to force upper case at the API level, which is what the UI does? ```yaml attribute: type: string pattern: "^[A-Z]+$" ```