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 Not under consideration
Created by Guest
Created on Oct 15, 2020

WKC - Multi select option in connected Asset Import in the catalog view

If we add connected assets to a catalog we can only select one asset and have to provide a name for that asset. Usually we import hundreds of tables and this seems quite painful. We would prefer a experience where we can select multiple tables, filter tables by regex or similar options, and use the asset name as is.

Needed by Date Oct 31, 2020
  • Guest
    Oct 26, 2020

    To add on to Marc's comment, we also are redesigning our metadata import and discovery services for a single entry point when adding assets to the catalog. This will simplify the experience for less confusion.

  • Guest
    Oct 23, 2020

    Thanks for your comment. You are correct, in the case you describe it is to allow a user to add individual assets to a Catalog, to augment the Catalog with added data sets. It is recommeneded to import many Tables / Files from a given system to leverage the Data Discovery capabilities of the tool, this will allow you to select a specific connection, sub-select a Schema / Folder or set of Assets, and import their metadata into a Catalog. Additionally, the discovery services will help automate the governance (and quality) functionalities - such as suggesting Terms to describe meaning, Classifications for identifying information and inferring Data and Quality Rules.