Re:When operating "at web scale", users often simply don't h...
by nradov on Sunday July 24, 2011 @10:43PM
(#2801088)
I am disappointed by how software developers continuously reinvent the wheel badly. There have been comprehensive data models for human names available for years. For example see the HL7 V3 EntityName data type.
http://www.hl7.org/v3ballot/html/infrastructure/datatypes_r2...
Any Entity can have multiple names, each of which is tagged with zero or more use codes such as "official", "pseudonym", "maiden", "tribal", etc. Each EntityName has one or more ordered parts which can optionally be tagged with a type: prefix, suffix, family name, given name. This data model isn't fully complete since it's missing some naming concepts such as patronymics but at least it's a better start than the mess that Google came up with.
[ Parent
| on HN ]
Re:When operating "at web scale", users often simply don't h...
by daemin on Monday July 25, 2011 @01:04AM
(#2801415)
Though what would be better and easier to fill out: (a) multiple text boxes with one for each important kind of name, (b) multiple text boxes together with some sort of code selection for each text box, or (c) a single text box that just says Name.
Re:When operating "at web scale", users often simply don't h...
by nradov on Monday July 25, 2011 @01:56AM
(#2801519)
The usual solution is to provide users with a choice. Default to showing a simplified field or set of fields that suit the common case for that locale. And provide an "advanced mode" with more fields and options to handle unusual cases.
Re:When operating "at web scale", users often simply don't h...
by daemin on Monday July 25, 2011 @03:34AM
(#2801724)
Well you could do that, but only if you must collect such information for governmental purposes, otherwise I would stick with just the single text box and allow them to put in whatever name they wanted.
I would especially do that for any sort of web startup for both simplicity of the interface and ease of implementation.
Re:When operating "at web scale", users often simply don't h...
by nradov on Monday July 25, 2011 @03:56AM
(#2801760)
It's not just for government purposes. If your hypothetical web startup has to integrate with any third-party systems (like anything in healthcare or financial services in the US) then you need the name broken into parts.
Re:When operating "at web scale", users often simply don't h...
by daemin on Monday July 25, 2011 @04:11AM
(#2801787)
Well I would consider that to be for government (mandated) purposes, since the service you're contacting with has a government mandated schema for the name it must use, and hence you must also use.
Of course you can always have different fields for billing information.