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.
Provide the ability to send, manage, and track GDPR delete requests to all the user of the affected assets.
Catalog Asset owners need the ability to send GDPR delete requests to users of assets that contain records requested to be deleted by a user, and have an automated mechanism to track their completion. This feature allows the Asset owner who has re...
Provide structured search support to NLU enrichments for textual data assets
Today, when a PDF or other text documents are profiled, NLU analyzes text with Keywords, Concepts and Categories. Such "enrichments" generated by NLU should be leveraged to find and select data assets.
In fact it looks like having an embedded WDS...
WKC needs to allow specification of access policies at the folder level within a data asset
a) We need to be able to set an access policy for a whole table that might be represented by multiple parquet files in a folder. b) We need to be able to set an access policy for all the files in a bucket.
WKC recognizes multiple files in a bucket as a single data asset,
We need this because we want to be able to enter metadata only and access policies once for all files that comprise a data source.
Specific examples: a) Uploading multiple pdfs needs to be able to store pdfs for a particular geo in a folder. Th...
Show description of data asset by Magazine view in Knowledge Catalog data asset list
-Use a real-life scenario to explain the problem statement/pain points
The customer can't see the data asset description in Knowledge Catalog's data asset list.
-state your current workaround(s)
Now the customer see the description by opening t...
Ability to distribute policies to specific catalogs
Today to have the capability of Policies and rules a user must purchase the Pro edition of Knowledge Catalog. What I anticipated was since I purchased Pro was, I would create a "dev" catalog, a "test" catalog and a "production" catalog. I would us...
In general the information shown on any asset in the Knowledge Catalog UI is fairly minimal, both on the overview page as well as the details page. Consider adding:
- size information for files
- record count information for data base tables etc...
Removing a data asset from a project or catalog does not delete it from COS
Whenever a data asset gets removed from either a Watson Studio Project or a Watson Knowledge Catalog the actual file is not removed from the underlying Cloud Object Storage bucket.
The result is that there will be a lot of unreferenced files in C...
Add from Catalog sometimes adds Connection and Asset, sometimes just Asset
We noticed that when adding a Data Asset from a Catalog into a Watson Studio Project it sometimes just adds the Data Asset into the project while sometimes it adds the Data Asset and a Connection into the project.
It's not obvious what causes the...
Add "issues" function to assets in the Knowledge Catalog
Allow users to add multiple "issues" to assets inside the Knowledge Catalog similar to how one would add issues to a file in a Git repo. This can be used to keep track of outstanding problems with an asset, document limitations, add requirements e...
Do not place IBM confidential, company confidential, or personal information into any field.