Menu
  • UX Trending
  • UX PODCASTS
    • DESIGN UNTANGLED
    • UX CAKE
  • UX Reading Room
  • UX Portfolio Building
  • UX JOBS
    • Atlanta
    • Dallas
    • Los Angeles
UXShareLab… everything you need to know about UX and more…
for the user experience design community

Search

Browse: Home   /   Should nationalities in an input be listed in country name or adjective form?

Should nationalities in an input be listed in country name or adjective form?

by UXStackExchange on August 1, 2017 in country, uxstackexchange

When designing a data entry form for entering information about a person or an organization (e.g. customer info, international business partners, etc.), there arises a question about the best way to list nationalities/citizenships in a select box or typeahead.

Consider a form containing both an address section, including a "country" field, and separately a "nationality" field (since one does not necessarily imply the other).

The country field should clearly be backed by a simple list of country names. But I have had arguments over what should be listed in the nationality field. One approach is to just list country names there as well; the other is to use adjectives (e.g. "German" instead of "Germany"). On one hand, nationality and citizenship are probably more naturally expressed with adjectives. On the other hand, certain countries have adjectival forms such that it may be confusing to select that country in the address field, then try and find it in the adjective list, as it may show up in a totally different spot alphabetically.

This is not an issue for most countries, e.g. "Germany" → "German", "Japan" → "Japanese", etc. but there are several exceptions, which can be basically split into two cases:

  1. Countries with wordy prefixes, like "United States of America" or "People's Republic of China". "People's Republic" would appear in the "P" section for country, but "Chinese" would appear in the "C" section for nationality. This case isn't as problematic, since most or all cases can be solved by moving prefixes to the end, separated by a comma ("America, United States of", "China, People's Republic of").

  2. Countries whose adjectival form is significantly different from the country name, specifically those with a different first letter, e.g. "Netherlands" → "Dutch", "Côte d'Ivoire" → "Ivorian", "El Salvador" → "Salvadoran". This is the bigger point of contention.

The second case is really the one where the conversation gets hung up. It may be that if I'm not aware that "Dutch" is the correct adjective for people from the Netherlands, I probably will be confused if I enter "Netherlands" in the country field, then head to the nationality field and can't find "Netherlandian" or "Netherlandish" or anything else that looks right in the "N" section. "El Salvador" vs. "Salvadoran" is perhaps even more confusing, since a user would be almost correct in assuming they should look for something like "El Salvadoran", not realizing that the "El" is removed, but they will be a hundred items away from the correct adjective.

But with that said, this is certainly a minority case for most countries, and it may be that in the majority of these edge cases, the user is familiar enough to make the leap, or will be able to find out quickly enough.

So I'm unsure where I stand. Should a Nationality list use country names, or adjectives? Which will provide the better user experience overall?

Tags: UX Stack Exchange

Sign Up for the latest in UX News...

Enter your email address to subscribe to UXShareLab and receive notifications of new posts by email.

Join 834 other subscribers

Related Posts

Are there numbers and letters to avoid for activation codes via SMS?
Are there numbers and letters to avoid for activation codes via SMS?
Can the "$" symbol be safely considered as universal when making a graphic depicting money?
Can the "$" symbol be safely considered as universal when making a graphic depicting money?
How to design an "add n rows" button?
How to design an "add n rows" button?
Need help designing a full-screen (laptop) notification viewable at a glance from ~5-7 feet away
Need help designing a full-screen (laptop) notification viewable at a glance from ~5-7 feet away

Should nationalities in an input be listed in country name or adjective form?

by UXStackExchange on August 1, 2017 in country, uxstackexchange

When designing a data entry form for entering information about a person or an organization (e.g. customer info, international business partners, etc.), there arises a question about the best way to list nationalities/citizenships in a select box or typeahead.

Consider a form containing both an address section, including a "country" field, and separately a "nationality" field (since one does not necessarily imply the other).

The country field should clearly be backed by a simple list of country names. But I have had arguments over what should be listed in the nationality field. One approach is to just list country names there as well; the other is to use adjectives (e.g. "German" instead of "Germany"). On one hand, nationality and citizenship are probably more naturally expressed with adjectives. On the other hand, certain countries have adjectival forms such that it may be confusing to select that country in the address field, then try and find it in the adjective list, as it may show up in a totally different spot alphabetically.

This is not an issue for most countries, e.g. "Germany" → "German", "Japan" → "Japanese", etc. but there are several exceptions, which can be basically split into two cases:

  1. Countries with wordy prefixes, like "United States of America" or "People's Republic of China". "People's Republic" would appear in the "P" section for country, but "Chinese" would appear in the "C" section for nationality. This case isn't as problematic, since most or all cases can be solved by moving prefixes to the end, separated by a comma ("America, United States of", "China, People's Republic of").

  2. Countries whose adjectival form is significantly different from the country name, specifically those with a different first letter, e.g. "Netherlands" → "Dutch", "Côte d'Ivoire" → "Ivorian", "El Salvador" → "Salvadoran". This is the bigger point of contention.

The second case is really the one where the conversation gets hung up. It may be that if I'm not aware that "Dutch" is the correct adjective for people from the Netherlands, I probably will be confused if I enter "Netherlands" in the country field, then head to the nationality field and can't find "Netherlandian" or "Netherlandish" or anything else that looks right in the "N" section. "El Salvador" vs. "Salvadoran" is perhaps even more confusing, since a user would be almost correct in assuming they should look for something like "El Salvadoran", not realizing that the "El" is removed, but they will be a hundred items away from the correct adjective.

But with that said, this is certainly a minority case for most countries, and it may be that in the majority of these edge cases, the user is familiar enough to make the leap, or will be able to find out quickly enough.

So I'm unsure where I stand. Should a Nationality list use country names, or adjectives? Which will provide the better user experience overall?

Tags: UX Stack Exchange

Related Posts

People like to read their own names and not others? - UX Design - psychology [on hold]
People like to read their own names and not others? – UX Design – psychology [on hold]
8 Podcasts Every Designer Needs to Hear
8 Podcasts Every Designer Needs to Hear
ATM Style Input Fields for Currency
ATM Style Input Fields for Currency
Where should text content be placed on screen?
Where should text content be placed on screen?
← 10 Custom CSS & JavaScript Hover & Click Effects
Effectiveness of numbers showing the amount of items related to each single filter →

Topics

Usability UX wordpress UX Jobs Los Angeles UX Jobs in Atlanta user-behavior User Interaction web-app UX Design WordPress Plugins Visual Design UX Toolbox Universal Design & Accessibility User Experience Web Design uxbooth UI User Research uxstackexchange UX Jobs Dallas User testing UI design UX Jobs Atlanta WordPress Gutenberg UX Rockstars

Feeds

UI UI design Universal Design & Accessibility Usability user-behavior User Experience User Interaction User Research User testing UX uxbooth UX Design UX Jobs Atlanta UX Jobs Dallas UX Jobs in Atlanta UX Jobs Los Angeles UX Rockstars uxstackexchange UX Toolbox Visual Design web-app Web Design wordpress WordPress Gutenberg WordPress Plugins

<span>recent posts</span>

  • UX in 2018: The human element

    • Anywhere
  • Three Takeaways from the Hawai’i Missile False Alarm

    • Anywhere
  • UX in 2018: Content

    • Anywhere
  • UX in 2018: Design, Development, and Accessibility

    • Anywhere
  • The Power and Danger of Persuasive Design

    • Anywhere

connect to uxsharelab

Enter your email address to subscribe to receive notifications of new posts by email.

UXShareLab. Copyright © 2018. All rights reserved.

  • Contact UXShareLab
  • UXShareLab Community
  • UX PROCESS
  • Recommended Reading
  • UX StackExchange