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.
default for catalog shows 4 assets.if you collapse the "recent" it almost shows 10.
So if there is 100, what shows? what 1k, 10k, 100k, 1M.
This is way to few since we expect catalogs to be well populated to be useful.
users of WDP, not just Data Catalog Admins, should be able view policies that are in place and they are responsible for following
Currently on the Admin of the policy manager can see the actual policies that are created. It's critical that other users should at least be able to view policies that they themselves are suppose to be compliant with, and they will be subject to w...
Add ability to modify or delete the artifacts (policies, rules, catagories) created in Policy Manager
Right now the UI doesn't allow any modifications of any type/form in the UI. This makes it really hard to use, since it's impossible to recover from accident mistakes when authoring a policy, catagory, or rule.
Should make it easy to create references not only to connections, or individual assets (file, table, doc, etc). So including the notion of directory, containers, schemas, etc.
While the individual file or table is useful, more often than not there use cases where their are a set of tables, docs, objects that are related and dependent. It would be very useful to keep that organizational structure and be able to catalog, ...
Do not place IBM confidential, company confidential, or personal information into any field.