Can a rule be set that does not allow US state abbreviations and auto corrects for location?
Concerts are showing up as two different cities as in the attached example. Utica, New York has 788 concerts and Utica, NY has 86 concerts, yet they are the same place. This could also be standardized for imported concerts such as Songkick.
https://www.concertarchives.org/locations?utf8=%E2%9C%93&search=Utica%252C+ny
Brucefan24
shared this idea
Hey there, we do account for state abbreviations for the US, Canada, and Australia when we do concert imports from 3rd party services. The trouble is typically from users who input the locations manually as there typically isn't enough info (a valid country name, etc) for us to infer that they are abbreviating a state name. I'm going to mark this idea as 'Completed' but there are always improvements that we can make as we continue to build systems to standardize the data. Thanks for submitting this suggestion! --Justin