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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Created by Guest
Created on Mar 9, 2021

Arabic names parsing

We are looking for is to have configurable option to reparse the token based on culture and confidence.

Arabic name does not get parsed in the complete way, when for example; Muhammad Hafiz is compared with Hafiz and KHAN with KHAN and come back no match.

name_match_why
("Muhammad Hafiz KHAN","Hafiz KHAN")

The IBM suggestion to manually configure HAFIZ to always be treated as a GN does not sound feasible for 2 reasons.


- First of all because it is not reasonable to ask the client him to configure all possible middle names.
- Secondly, assume that the client will follow your advice what will happen if he then try to search "Muhammad Hafeeze KHAN" (middle name written differently).
Hafeeze is not configured anywhere so he will again get GN: "Muhammad" SN: "Hafeeze KHAN".
Now he will have 2 missing stems one in the GN and one in the SN and won't get a hit…

  1. The client wants is to be able to get both parses e.g.

When he provides "Muhammad Hafiz KHAN"

  • GN:"Muhammad Hafiz" SN: "KHAN"

  • GN:"Muhammad" SN: "Hafiz KHAN"

So, he can get a hit when comparing with either:

    • "Muhammad KHAN"

or

      • "Hafiz KHAN"

  • Currently even if we set the re-parse threshold to be high enough so that the name will be re-parsed, we are not able to guarantee to the client he will get the second parse of the name.
    That is as the second name parsing confidence must be higher than the first name parse confidence for us to get the second parse.
    I think it is reasonable to return the second parse with its confidence and let us (via internal configuration of course) to decide ourselves what to do with the second parse.
    I think that when middle names are involved, especially 3 tokens names, it make sense to always do the following:

    • If the middle name in the first parse was attached to the GN return it in the SN.

    • If the middle name in the first parse was attached to the SN return it in the GN.

And return both parses and their confidence.

Needed by Date Apr 3, 2021
  • Admin
    MAY LI
    Mar 9, 2021

    Thank you - Ronen - for submission. We will investigate and follow up here with status.