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 Feb 23, 2018

InfoSphere Governance Catalog (IGC) Enhancement System Errors See Server Logs or Browser Console

The user should not need to refer to any logs (in almost all instances where errors occur). Enough information needs to be provided as part of the message to be able to resolve the issues with the import, including:
• An (error) message that clearly articulates what the problem is
• The position in the file where problem occurred
• Information to help resolve the problem e.g. text included as part of the message or a hyperlink to useful documentation.
In the extreme cases where it is not possible to provide this, the relevant information from all logs should be combined and made accessible in IGC (this alone would save a lot of wasted time trying to track down where the error is in the logs).
If the error can still not be resolved, the last resort would be to look into server logs.