Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Nov 12, 2019

Japanese Address standardization (UCSFREQADDR) stops dividing the Japanese Kanji characters

To compare the address data written in Japanese with the AXP, we should select the UCSFREQADDR for the Address standardization function. When we derive the data including the Japanese addresses, the Kanji characters in the prov and the city weren't divided, but the ones in the addrline1, the addrline2 and the addrline3 were divided.
 Please note that the Hiragana / Katakana characters are not divided.
Dividing the Kanji characters effects the following scenario,  
1. Similar town name ( only on characters missing )
2. Bad performance.  

We are using the Multi-Attr and the Edit Distance as work around.

In Japan, in general, we can convert the "Address  code" in numeric from the Address strings. 
So we can use the mult-attr and the Equivalent (or Edit Distance) instead of the AXP, but 
There are some address data which cannot be converted into the address code because of invalid address. 
In this case we want to use the AXP with the Address string data.
Needed by Date Dec 16, 2019
  • Admin
    Marcus Boone
    Nov 12, 2019


    Thank you for the submission and the detailed explanation of the issue. I will review with the team and update this Idea accordingly.