Loading problem...
A customer identity platform receives user names from many upstream systems with inconsistent casing.
Table: users
Task: Produce a normalized result where each name follows this exact casing format:
Output requirements:
Supported submission environments:
users:
| user_id | name |
|---------|-------|
| 1 | aLice |
| 2 | bOB |[
{"user_id":1,"name":"Alice"},
{"user_id":2,"name":"Bob"}
]Each row is normalized independently by uppercasing the first letter and lowercasing the rest.
users:
| user_id | name |
|---------|-----------|
| 10 | cHARLIE |
| 4 | EVE |
| 7 | m |
| 6 | dAvId |[
{"user_id":4,"name":"Eve"},
{"user_id":6,"name":"David"},
{"user_id":7,"name":"M"},
{"user_id":10,"name":"Charlie"}
]Single-character names remain one character, and output sorting is by user_id rather than input order.
users:
| user_id | name |
|---------|-----------|
| 21 | ALPHA |
| 22 | alpha |
| 23 | AlPhA |[
{"user_id":21,"name":"Alpha"},
{"user_id":22,"name":"Alpha"},
{"user_id":23,"name":"Alpha"}
]Different source casing variants converge to the same canonical display format.
Constraints