A fork for the time-zone database?
A fork for the time-zone database?
Posted Oct 10, 2021 19:36 UTC (Sun) by divanise (subscriber, #71550)In reply to: A fork for the time-zone database? by mbunkus
Parent article: A fork for the time-zone database?
Mostly agree, but storing two fields ("full name", eg "Johnathon Hancock", and "goes by", eg "Johnny") is a significant improvement for roughly equivalent effort over the naive "first name/last name" approach. I've advocated for "full/goes by" ever since I first came across it, but often fail due to either legal obligations or API restrictions that require collecting "first name/middle initial/last name".
Posted Oct 10, 2021 19:52 UTC (Sun)
by mbunkus (subscriber, #87248)
[Link] (1 responses)
I fear such two fields would be even more confusing to users than the typical but widely used "given & family name" or similar, meaning the entity storing the data couldn't realistically make good use of it.
Of course there are instances where you need specific pieces of information, e.g. if you need a person's name as given on their passport (for official things such as crossing borders). And maybe it's useful to have an additional fields for more informal communication between that entity and you. But if that's the case (and I'd guess that such cases are really rare), be explicit in what you name those fields, really explicit, so that there's no doubt what they'll be used for. For example: "Name as written on your passport" and "Preferred name for us to use when communicating with you".
Posted Oct 11, 2021 15:04 UTC (Mon)
by smurf (subscriber, #17840)
[Link]
As one datapoint, nowadays I need to provide all three of my "first" names on banking-related douments because of the current crop of gobsmackingly dumb regulations. But nobody should ever use anything but the second of those names to address me. No, not the first, and certainly not all three, I'm not the male equivalent of Pippi Longstockings dammit.
Now this is certainly a First World Problem compared to people who are named O'Hare and cannot even enter that due to broken Bobby Tables Prevention filters, much less my acquaintance Aahz (yes that's his single real-life name), or … the list goes on.
Posted Oct 10, 2021 20:07 UTC (Sun)
by mpr22 (subscriber, #60784)
[Link] (1 responses)
If I were more conservative about correspondence etiquette, I would expect it to open with "Dear Mr (Surname)"... but if I were that conservative about correspondence etiqutte and had a knighthood that they knew about, I would expect them to address me as "Sir (Forename)". And I would expect all of that without having to "jump through hoops" on their website, expecting simply putting my title, forename, and surname to be sufficient.
And as I am, I get mildly grumpy about letters opening "Dear (Forename) (Surname)" because they fall between two stools, satisfying neither my own casualism nor the standards expected by the formalist in my head.
Posted Oct 23, 2021 15:23 UTC (Sat)
by nix (subscriber, #2304)
[Link]
Given the perennial state of UK government software I'm sure this is all a thousand times better by now! (Oh wait, that was a typo. I meant "worse".)
Posted Oct 11, 2021 9:25 UTC (Mon)
by farnz (subscriber, #17727)
[Link]
Ultimately, the "right" thing to do is to have a "name for this purpose" field, provide some pre-fill features that helps someone with an expected naming convention fill in what you expect. Bear in mind that "full name" is itself ambiguous - is the full name "Paul Daniels" (which was the only name on much of his ID), or "Newton Edward Daniels" (as per his birth certificate, and marked as an additional full name on his passport)? You may even need multiple full names for one person…
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?