Skip to Main Content
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 Planned for future release
Created by Guest
Created on Feb 22, 2018
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit WDS-I-72 Ability re-process documents without re-ingestion.

An API to automatically reprocess all documents enrichments against a new custom model. Merged

Currently, in several customer deployments of Watson Discovery Service currently implementing their MVPs, collections will be thought to contain hundreds of thousands of documents (even millions). Typically the modelling tasks to model custom and domain related analysis is thought to be refined in defined time slots so to obtain more and more accurate models over time. This currently imply that in order to apply the new model to a given collection, so to obtain the new textual analysis, the only way is to drop the current collection, create a new one configured with the new model and reinvest all the documents in the new collection. The impact of this option could be very expensive in a production environment while it could be really minimised if a suitable API to reprocess all the collection content would be available.

  • Guest
    Mar 28, 2018

    See also https://ibm-watson.ideas.aha.io/ideas/WDS-I-72

  • Guest
    Mar 9, 2018

    Yes please - even for small collections, having to reload all the docs just to apply an update to the WKS model or configuration set is a bunch of work.