Repo for old location picker prototype. If you're looking for the latest location picker:
Home Page: https://github.com/alphagov/govuk-country-and-territory-autocomplete/
License: MIT License
This project explores patterns for country pickers that use data from open registers.
This is based on the GOV.UK prototype kit, so most instructions that apply to that work here too. In short:
git clone [email protected]:openregister/picker-prototypes.git
cd picker-prototypes
yarn # or npm i
yarn start # or npm start
open http://localhost:3000Tested on node v7.x, yarn v0.18.1, and npm v4.x.
Ivory Coast is also known by its French name of Côte d'Ivoire, but your picker doesn't recognize it, not matching anything after ‘Cô’:
It does work if you Asciify it as ‘Cote’ rather than ‘Côte’, but if somebody's going to use the French name they may expect it to have the French accent on it.
You could either add ‘Côte d'Ivoire’, and its longer form ‘The Republic of Côte d'Ivoire’, as additional endonyms. Or fix this more generally by ignoring all diacritics when matching.
Slovenija is the endonym for Slovenia - it's listed in the data spreadsheet and is found in the picker, but doesn't show in brackets like other endonyms.
Edit: I see the same exists for Singapura - perhaps there is a wider issue of endonyms not showing correctly?
We've seen at least two cases in user research of users being confused by the country Czechia when searching for The Czech Republic. The country name changed in April 2016, but this is probably not well known.
This is what the picker currently looks like when you search for Czech:
From the user's point of view, neither is correct. The first they've never heard of, and the second doesn't exist any more (but people may still think it more relevant). The second probably shouldn't show unless services explicitly want historic countries.
If the user types the full name they know, it works better:
This is better, but unless they type enough characters, they don't get the name they're familiar with.
When a country name changes, for a period of time after that (3-5 years?), show the historic name as well:
This feels like quite a nice use of registers - the correct current name is used, but users are 'eased' in to the new name.
We've seen in user research that users can be confused when historic countries appear in the picker. This causes concern that our data is out of date - as users don't immediately realise why the historic country is showing.
Hopefully the picker will be configurable so it doesn't display historic countries when not needed - but when they are needed, we could communicate their status better.
We could append extra text to historic countries:
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.