- Article Type: General
- Product: Aleph
- Product Version: 16.02
When entering a patron ID in the borrower box of the Circulation module (Loan or Patron tabs), the input is forced to be upper case, no matter what is actually typed at the keyboard. If the ID we are attempting to match on is stored in lower case (character data), then there is no match. Is there a way to change how this input box handles the input data? Is Aleph assuming that all IDs are upper case to begin with? Could an ID be used that contained both upper and lower case characters? When we try to use this ID to log on to the Web, it stays in lowercase, but it doesn't find a match. Our type 03 ID (net id) is a campus assigned alphanumeric ID used by the campus LDAP system and is used widely across campus. The netid is normally treated as lower case by campus systems and pretty much all other applications that make use of this ID.
Yes, ALEPH is assuming that IDs are in uppercase. This SQL can be used to change lowercase type '03' IDs to upper: SQL> update z308 set z308_rec_key = upper (z308_rec_key) where z308_rec_key like '03%'; If the user enters the ID in uppercase, it will match. If the user enters the ID in lowercase, the system will uppercase it and it will match.
case sensitivity, patron ID
- Article last edited: 10/8/2013