IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Feature request: Enhance/add filters to fuzzy matching

I have a scenario where fuzzy matching should only be executed in regards to spaces and special characters such as (),.-  I do not want the fuzzy matching to apply to alphanumeric characters (letters or digits), as I am trying to match to an exact list of alphanumeric strings.

Real-life scenario: I have an entity list of California Vehicle Codes (traffic offense numbers e.g.  VC 21100.3).  There are several hundreds of them.  I have had to turn off fuzzy matching for that entity, as it is very important that I try to get an exact match on the user's query.  However, I would like to turn ON fuzzy matching for that entity if I could restrict it to being fuzzy about spaces and special characters only, but not be fuzzy about alphanumerics.

An example would be that "VC21452a" and "VC 21452a" and "VC21452(a)" and "VC21452 (a)" and "VC 21452 (a)" should all be a fuzzy match to "VC21452a" with the spaces and special characters stripped; but should not match a similar number or the same number with a different suffix.  So the fuzzy match should NOT match VC 21352e to VC 21352a, and should NOT match "VC 21352 (e)" to "VC 21352 (a)" or to "VC 21352".

  • Jana B
  • Dec 18 2019
  • Will not implement
Why is it useful?
Who would benefit from this IDEA? While programming my Watson Assistant, this would save me many hours of tedious effort and frustration in having to add acceptable aliases to my entity list of vehicle codes. I'm guessing that banks and insurance companies would also benefit from this.
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
  • Admin
    Mitch Mason commented
    30 Mar 06:32pm

    Would it be easier to identify this using a pattern entity and regular expressions?

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions