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 Delivered
Created by Deleted user
Created on Jun 12, 2017

Discovery comprehensive handling of domain-specific dictionaries

Discovery is being positioned as replacement for R&R yet search (and not even WKS-based enrichment) cannot handle a comprehensive handling of domain-specific language, such as technical support. In R&R this was achieved by direct access to Solr configuration.

With Discovery, at this time, the only way to get close to text normalization based on domain-specific language is to use Conversation entities to get the relevant domain language for a doc and store it as a field in discovery. Then do the same to get domain language for each query and use the entities to expand your query ..while this gives you some matches, it completely prevents us from exploiting keyword proximity measures to improve ranking of most relevant records.

there several levels in which this can be achieved:

0. integrate dictionaries from WKS with Elastic Search

1. give full access to elastic search - which will give full benefit the powerful search engine on top of discovery enrichment - such as scoring function

2. ensure that synonyms in domain-specific language are applied to the enrichment output - as of now, they are completely disconnected

  • Guest
    Oct 2, 2017

    Interest in this topic area in particular level 2 mentioned above:ensure that synonyms in domain-specific language are applied to the enrichment output - as of now, they are completely disconnected

  • Guest
    Jun 20, 2017

    Customer for which the Watson Solution Delivery team is building solutions requires Domain Specific Dictionaries to better enable normalization.  A few examples are

    1. Mapping different strings to the same entity (e.g.Firm ->firm, Firm, firms, Firms),
    2. to support  phrases that are "terms of art"  that would be invalidated by general english normalization (e.g. Exchange Traded Funds if normalized could result in Exchange Trade Fund) and
    3. Domain acronyms conventions (mixed case)  e.g. messenger RNA  -> mRNA, transfer RNA -> tRNA would need to be normalized as the same concept with lowercase "m" and "t" maintained
  • Guest
    Jun 16, 2017

    The Watson Solution Delivery team also has many customer solutions that can be benefited by the support of Dictionaires and the normalization of mentions.