Background: Currently, during address curation, we populate the City Short Name based on the provided reference data source. If the source does not include a Short Name, we default to using the Full City Name as the Short Name. This approach is particularly inconsistent for German cities, where well-established short forms exist (e.g., "Frankfurt am Main" → "Frankfurt").
Idea: We will create a centralized reference list for approximately 2000 German cities, each entry including the Full City Name and its corresponding Short Name. When a feature toggle is activated during address curation, the system will automatically take the Full City Name from the corresponding field, compare it against the reference list, and populate the Short Name accordingly.
Benefits:
Consistent Short Names for German cities
Reduction of manual input and potential errors
Improved data curation quality
Technical Implementation:
Creation and maintenance of a centralized reference list
Introduction of a feature toggle enabling automatic Short Name population based on the reference list
Development of a matching algorithm to exactly match the Full City Name and populate the corresponding Short Name
Next Steps:
Validation and expansion of the existing reference list
Implementation of the feature toggle
Development of the matching functionality
The requested functionality for standardizing short city names in German addresses has been successfully implemented. As described in your initial idea entry, we now support the use of a centralized reference list (~2000 German cities) that maps full city names to consistent short names (e.g., "Frankfurt am Main" → "Frankfurt").
How to use the functionality:
To enable this logic during address curation, simply activate the feature toggle USE_LOCALITY_SHORTNAME_REFERENCE
Once the toggle is active, the system will:
Match the full city name against the reference list.
If a match is found, automatically set or overwrite the
shortNamefield with the standardized short version from the reference list.