FamilySearch - Please take care when working on standardization of place names
This matter has been raised previously (on the GetSat forum) but continues to give me work that should be quite unnecessary. It appears a (fairly) recent exercise to improve the database of standard place names backfired quite badly. The negative result was that many perfectly acceptable, existing place name lost their standard status, resulting in users having to "re-standardize" them to exactly the same format.
I have previously provided "proof" that FamilySearch programming has caused this - rather than it being my carelessness in not standardizing the name properly at the time. I just came across another example, where I had already corrected a place name (to make it a standard one), so have amended my reason statement from "Standardized place" to "Standardized place - again".
I would politely request the engineers / programmers / developers to take great care when undertaking future exercises in relation to this subject, so that the valuable time of users is not wasted still further.