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,
Post an idea
Upvote ideas that matter most to you
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.
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".
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.
Do not place IBM confidential, company confidential, or personal information into any field.