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,
Post an idea
Upvote ideas that matter most to you
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.
IA thin client reference column from another table.
In IA thick client we can use reference column from another table and we can get result. When we try to run DQ analysis in thin client, its doesn't have option to select reference column from another table which are associated within project. This...
What we need is an alternative way to pull each ruleset at the data rule definition level of granularity, and at that level provide the business rule, severity, execution history, etc. Currently we were doing this by querying xmeta.
Subscription Manager Filtering for Email is inadequate
When setting up Subscription Manager for emails, the filter should be based on the names of the project and data rule, not the RID. That is the #1 requirement to make this feature at all usable and is an extremely high priority. It is simply a gam...
Rule output for not applicable rows (not part of DRD scope) should not be treated as "met"
Currently N/A (filtered out) rows that are not in scope of a certain data rule (definition) display status as "met". We would like to be able to toggle whether to include or exclude N/A rows from rule results while creating the rule. So as an exam...
Certify Information Analyser to profile Parquet files in an AWS S3 bucket
In order to provide effective Data Governance, we need the ability to run Column Analysis, Data Quality Analysis, and run Data Rules against Parquet files stored in Amazon S3 Buckets. These files form a significant portion of our data estate, and ...
Do not place IBM confidential, company confidential, or personal information into any field.