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 Jan 8, 2018

Data Catalog: Deny ability to publish data assets when asset with same name already exists in the catalog

Currently the WDP - Data Catalog allows any user of a project to publish any data asset and will always create a new set of assets. In my case when working with the catalog, I published the SAME data asset multiple times to my catalog because I was not sure if I had already published it. When I checked my catalog, I noticed that there were multiple data assets with the SAME name for the same data due to me hitting the publish button a few times. In a real world scenario, this can cause an organization to have a ton of data assets with the same name and can make it difficult for someone to find the data they want. I believe this defeats the purpose of the Data Catalog to make it easy for someone to shop for data, especially if they are unable to get the right file due to seeing multiple files with the same name. See the snapshot below.