Settings and activity
201 results found
-
5 votes
Greg Nordyke
supported this idea
·
-
25 votes
An error occurred while saving the comment
Greg Nordyke
supported this idea
·
-
6 votes
Greg Nordyke
supported this idea
·
-
7 votes
Greg Nordyke
supported this idea
·
-
7 votes
Greg Nordyke
supported this idea
·
-
24 votes
Greg Nordyke
supported this idea
·
-
68 votes
Greg Nordyke
supported this idea
·
-
18 votes
Greg Nordyke
supported this idea
·
-
54 votes
Greg Nordyke
supported this idea
·
-
37 votes
Greg Nordyke
supported this idea
·
-
17 votes
Greg Nordyke
supported this idea
·
-
15 votes
Greg Nordyke
supported this idea
·
-
53 votes
MEEP 2026 Winner
Greg Nordyke
supported this idea
·
-
14 votes
Greg Nordyke
supported this idea
·
-
18 votes
Greg Nordyke
supported this idea
·
-
39 votes
Greg Nordyke
supported this idea
·
-
70 votes
Greg Nordyke
supported this idea
·
-
9 votes
Greg Nordyke
supported this idea
·
-
6 votes
Greg Nordyke
supported this idea
·
-
21 votes
Greg Nordyke
supported this idea
·
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.