Many libraries depend on zip/postal codes, city, prov/state metadata to make financial and library service decisions. No subfields in the address field can be verified. The postal code has some verification, but the record can be saved if that field is not entered correctly. We would like the option to make the CITY, PROV/STATE, and POSTAL CODE/ZIP data verified, and to have a description beside each "expanded" address subfield to guide staff on how to enter the data.

Idea Value
Libraries should be able to verify the address subfields (like the city, prov/state, and postal/ZIP code).

Analytic tools (even Decision Center) have the potential to query very specific reports that are based on the Postal/ZIP Code, but we rely on standardized metadata for these reports. Additionally, once we find errors, it is very difficult to use Global Update to correct numerous types of errors that are possible.

While this is considered, we like the option to add description tags for each expanded address row. If validation is not an option, at least this would guide staff on how to make decisions during the patron registration process.

I cannot stress enough how important it is for Libraries with large geographic areas to map circulation activity trends and registrations. We can use this to determine collections, programming, promotions, hours, delivery service, branch locations, staffing etc.

The SDA patron registration is our one chance to get our contact with the customer set up. We no longer send mail (via the post), so if our registration has data entry errors, we lose the opportunity to reach our customers.

Related requests are here:

https://idealab.iii.com/alwaysopen/Page/ViewIdea?ideaid=5897

https://idealab.iii.com/alwaysopen/Page/ViewIdea?ideaid=7868