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 Dec 12, 2017

Allow user to specify catalog as the target for automatically discovered data assets

Currently when user checks the option to discover data assets on a connection, the discovered data assets are always added to a (staging) project first, with expectation that the user will then go to the project, and then select the ones he wishes to catalog.

The proposed idea is to allow user the choice to have the discovered data assets added directly to catalog instead, completely bypassing project.

The point is to avoid requiring user the tedious step to manually select which ones to publish to catalog, but rely on a robust and intelligent search in catalog to help catalog members find the assets they need.

With this, we can also simplify the UI:

- If discovering from project connection, add discovered assets to the project.

- If discovering from catalog connection, add discovered assets to the catalog.

That'll be straightforward and easy for user to understand. 


  • increase speed to catalog assets
  • reduce steps for user to get assets into catalog
  • tags are immediately visible in catalog (e.g. discovered, schema)


  • profiling process will need to handle influx of data assets added to governed catalog

[The idea was originally raised by Dirk deRoos.]

  • Guest
    Dec 14, 2018

    Promoted to