3 ms·
Others have stated the reason for normalizing it already: interacting with third party software and/or services. It makes more sense to normalize it at the beg
by pyre 17y ago
Others have stated the reason for normalizing it already: interacting with third party software and/or services.
It makes more sense to normalize it at the beginning in order to give the user a chance to approve that it was processed correctly. You could just do the normalization at the point when you need to interact with the 3rd-party services, but then it's hidden in the back-end so you have to be confident in your normalization processing.
You could roll out a solution where the confirmation page is just there to allow the user to approve that normalization works on their free-form address, but still store it as a chuck of text in the database. Then when you are confident enough in your normalization process, you could just remove the user confirmation part.