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 Jan 10, 2020

Provide administrative control; for user access to Information Analyzer 'Discover' function

Function accessible via Information Analyzer:
Connections> Discover Assets
Connections> Browse> Actions> Discover
Currently access can only be controlled through IMAM roles.

IA ‘Discover Assets’ provides abilities not understood by typical user.  The options for controlling discovery do not provide the information needed to understand consequences and outcomes.  For example, creation of multiple import areas when running discover unfiltered against large data sources.   In one occurrence discovery was initiated against an Oracle DB resulting in the 1200+ import areas (one per schema) including several hundred user schema.  The number of imports running in parallel had impacted availability of the DB.

Behavior should be site and connector type specific. 
For example, enforce default import options such as ‘Schema name filter:’ for discovery run against Oracle databases.

Needed by Date Feb 7, 2020