While combing through addresses on a data hygiene quest, I’ve run across a few interesting city names.... These were all records created via the Constituent Import Utility, and the city name came through the process as "Bra #..." (see screenshot). It’s happened on different records, from different imports run by different users.
When I checked back in the txt files with the data for these imports, the city names listed there are more mundane.
Any theories as to what these bras are and how they got in my database?
Thanks!
Hi Jennifer!
I recommend checking out your TR_CITYSTATE table. If a US zip code has a row in the table, the city gets auto-populated when a zip code is entered. Each Bra # seems to correlate to a different zip code, so it may be pulling these faux-cities from TR_CITYSTATE.
Best,
Darryl
Thank you, Darryl! There are indeed "Bra"s in our TR_CITYSTATE table. I found 31 rows of them. Which leads to other questions....
I have 31 Bra's in my TR_CITYSTATE table as well. The column listed as "usps_code" seems to have a useful value. We might want to create a little bit of SQL to clean this up. We might also want to ask Support Team to see if a fix be made across the network as part of a SP or upgrade.
I'm going to guess if you have this and I have this then it's either a Science Museum thing.
Or something that happened back in 2000 when Tessitura was born at the MET Opera. Chuck Reif any ideas?
--Tom
Interesting...
Yes.
We periodically reload our TR_CITYSTATE table with data from https://www.zip-codes.com/ and there are no Bra cities in that data. It appears zip 33139 should be Miami Beach. Anyway, if you do some sort of refresh of the TR_CITYSTATE data (which is useful anyway because the city/state mappings to zip can change over time), that should prevent more of these from appearing.
These rows can be safely removed from the TR_CITYSTATE table. These errant rows will be removed en-masse with the Tessitura v15.1 upgrade.
Bob Bell
Thanks,