This idea should include postal code logic as well.

Greg's comment below really stuns me. I had no idea that Polaris that this functionality. I bet "most" Sierra libraries would love the option to enter the zipcode (and postal codes for Canadian libraries) and auto fill the remaining city etc. As a Sierra library, I really don't care that this change would involve a lot of clean up in my patron records. I know everyone has to agree on a change like this, but some Sierra libraries would like to simplify the data errors that are made by the public when filling out an address. We need accurate addresses to understand collection use, population, and targeting promotions.

I previously marked this Important, but it really is Critical for Polaris libraries. If a registration submitted through Discover has a different city/county/state combination than what's in the Postal Codes table in Polaris, then a new entry is created in that table. My library has around 50 new entries from Discover registrations since we went live a little more than a month ago. Staff suddenly have to choose between different combinations.

What's really neat about how this has worked in Polaris for years is that it's a miniature validation: put in the postal code and then the city, county, and state are pre-populated. While postal codes can be shared between cities, I'm starting to see unnecessary clutter coming in via Discover. A partial screenshot from Leap is attached.

We don't have this in Sierra (online registration), would be nice to have what you have in LEAP/PAC.