The new search is awesome, so thanks for that! However, I have two entries for London. One is “LONDON”, and the other is “London”. I guess that the merchant provided strings need to have their case normalised.
I had a similar situation where the location add an extra space at the end. I submitted a merchant correction and it went away.
Both this cases can be prevented in the search logic by searching/matching lowercased trimmed operands, regardless of the actual display case. But ideally they could be normalised before being stored in the data backend.
Thanks Duncan! We’re working on fixing that – we need to do some fixing up on the backend