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.
Allow for retrieving data quality rule definitions, but not the bindings (I'll call them instances) of those definitions to actual tables and columns. It makes no sense to me why the existing endpoint to list the definitions would be useful without a related endpoint to show the bindings. There are several reasons I see the additional endpoint as needed.
The first is that there does not appear to be any functioning method of backing up and restoring what data rule bindings have been created. Having an endpoint that could retrieve (and better yet create them) would allow the user to create a backup/restore functionality that was left out of the product.
Also the existing web GUI to manage data quality rules is very difficult to use, it only provides a small window to display the data quality rules for a given asset and you have to expand the "Rule name" section to even see what the rule is, and when you do that the screen gets almost taken up by that one entry and you lose your place in the list.
So in addition to the backup/restore need above, if the REST API provided an endpoint for retrieving the bindings for a quality rule definition it would allow the user to produce a formatted dump of the rule bindings to work around the shortcomings of the IBM supplied GUI.
As someone who has entered a large number of data quality rules and bindings I can tell you this is a significant pain point.
Do not place IBM confidential, company confidential, or personal information into any field.