Names in forms

Is it better to create a name field that allows the users to type in their names anyway they want, or should the first and last names be separated into different fields for better data management?

By Kim Siever

I am a copywriter and copyeditor. I blog on writing and social media tips mostly, but I sometimes throw in my thoughts about running a small business. Follow me on Twitter at @hotpepper.

9 comments

  1. It depends on how the data will be used. I like websites that display a “welcome” message with my first name. If you plan on doing variable data print projects (or mail merge) separate fields provide similar flexibility to address a letter “Dear John,”.

    If a full name is needed just create a conditional in the code combining the two to check for a first name AND last name and add a space between the two if they both exist.

    But, I also think you should limit a data set to as many fields as possible.

  3. Agreed with Hugh. If you need to be able to search/sort data by first name or last name, putting them in separate fields is faster and easier.

  4. Is the developer’s need (or the data analyst’s) more important than ease of use?

  5. It depends on the need of the data. For example, if the form was to be used for student registration, it would be necessary to have first and last name split up, perhaps even a field for middle name/initial in case there are duplicates of a name. However, for a form that is simply taking shipping information for a CD I just purchased (which is really only used for the address label), first and last combined is fine.

  6. That’s a good question Kim.

    When it comes to First and Last name, I think the data analyst wins.

    When it comes to other data such as whether to have one or two address fields I think ease of use should win.

    An ease of use trick I add to my own databases includes a zip code lookup (for us in the states). A zip code is entered first and then the city and state are automatically entered using a database lookup.

    I’m surprised I haven’t seen web2.0 gurus code this feature.

    BTW you can find a somewhat recent US zip code lookup data file on my site.

  7. That sounds like a cool feature Hugh. How do you account for mobile devices or JavaScript-disabled browsers? Is it populated server-side when it is processed?

  8. I only use zip code lookups locally right now, and not in a web environment so I don’t have to address mobile and javascript issues.

Comments are closed.