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


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


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
    Reply
    |
    Nov 12, 2019

    Murai-san,

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