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:

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:

Status Future consideration
Created by Guest
Created on Feb 12, 2018

Delete button for individual docs/results

Currently there is no simple or interactive way to delete documents within the WDS toolkit making it difficult for non-developers to manage the WDS corpus without having to use curl/sdk/api. While it is easy to upload individual documents via drag and drop, it should be just as easy for a user to delete a document from the corpus as well. This could perhaps be implemented as a 'bin' button that is appended to each result in the query tab and clicking on it would initiate an api call to delete the document from the corpus. 

One side feature to consider would also be an update button that allows users to update particular document metadata fields as well.

  • Guest
    Apr 15, 2021

    So this is pretty basic functionality and this idea has been out there swince 2018. If I upload a few docs and I need to delete one of them, I can't through the UI. If you offer the UI to add a doc then you need to offer a UI to remove one.

  • Guest
    Jan 29, 2019

    Thinking very briefly about it I think that would be acceptable - i assume a use case where a user wanted to maintain the training they would upload the same docs to overwrite, since the doc ids matter

  • Admin
    Jan 29, 2019

    while it might not be expected, would it present a real problem if it was deleted?  basically, to help reduce scope for this feature, the simplest thing to do for a "delete all documents" function is for tooling delete the collection behind the scenes and then create a new one with the same name and collection id.  So while it would delete all docs and retain the original collection attributes, it would delete all collection data vs just the documents.  For the main scenario where this feature is likely helpful, the question is would that be acceptable behavior?

  • Guest
    Jan 29, 2019

    i wouldn't expect synonyms to be deleted, but i might expect training data to be deleted

  • Admin
    Jan 29, 2019

    I have quick question to those interested.  As part of implementing support for this feature, would it be acceptable if all collection assets such as training data, synonyms, etc.were all deleted when a user chose to "delete all documents" from a collection?  Note that deleting an individual document would not delete all collection assets.


Ability to DELETE all at once or specific documents from the tooling

Ability to DELETE all at once or specific documents from the tooling (now it is possible only via API). I always am enforced to delete the whole collection to "clear" docs (and repeat the collection and config creation steps).
about 4 years ago in Watson Discovery Service (WDS) 0 Future consideration