Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Planned for future release
Workspace Watson Discovery
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

  • 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.