Search results: Watson Discovery

Showing 56 of 2943

Ability to disable or customize stemming

Watson Discovery uses stemming to identify valid matches. Based on our experience it appears that stemming is applied in both Natural Language Queries and also Discovery Language Queries. It seems to also enforced in phrase searching. This is usef...

over 6 years ago in Watson Discovery 13 Not under consideration

35 VOTE

Delete All Documents API

Right now if you want to delete all documents, you either need to delete the collection (which could mean code changes to point to a new ID), or you need to write a script to delete every document one by one which is time consuming.

over 8 years ago in Watson Discovery 2 Not under consideration

8 VOTE

Need access control at project level of Watson Discovery

Customer will use Watson Discovery as the NLP solution. Customer has very specific requirement that group A can only see data set 1, while group B only see data set 2, but in WD, all people can see all projects (including all the files/ data) with...

over 2 years ago in Watson Discovery 1 Not under consideration

8 VOTE

Improve Smart Document Uderstanding processing time

Real-life scenario: the user uploads a document and the extracted info are needed as input for another tool or ML model (real time scoring is needed). The customer experience suffers from the waiting time. The processing time of one document is to...

almost 3 years ago in Watson Discovery 2 Not under consideration

6 VOTE

IBM to enhance the Filters for Sharepoint connector so that besides specifying which file extensions to crawl (viz. .aspx pages) one should be able to specify exclude ListItemCollection pages

This enhancement will allow more fine grained control over which items to crwal using Watson Discovery v2 Sharepoint connector. For one use case, there are 11362 ListItemCollection type .aspx pages and 1000 real .aspcx pages. Currently Sharepoint ...

over 2 years ago in Watson Discovery 1 Not under consideration

15 VOTE

Need to return Normalized entity values from WKS custom model

Applying annotation to documents ingested into WDS using a custom WKS model allows the client to tag content based on their own vocabulary/domain. Currently WKS model can't be configured with the normalizeEntities flag (like Alchemy used to be) an...

about 8 years ago in Watson Discovery 0 Not under consideration

14 VOTE

Delete button for individual docs/results

Currently there is no simple or interactive way to delete documents within the WDS toolkit making it difficult for non-developers to manage the WDS corpus without having to use curl/sdk/api. While it is easy to upload individual documents via drag...

over 7 years ago in Watson Discovery 6 Not under consideration

1 VOTE

Make the annotation tool in Watson Discovery colorblind safe

During a recent Client Enablement Workshop, we presented an overview of Watson Discovery and followed it with a hands-on session. This allowed participants to explore the product through guided exercises. However, we encountered an important acces...

7 months ago in Watson Discovery 0 Submitted

10 VOTE

Ability to clone collection from one environment to another

We have some collections in Dallas and others in Tokyo to secure the redundancy. All collections must have completely the same ranking as each other. For that reason, we need to clone collections of Watson Discovery from one environment to another.

over 6 years ago in Watson Discovery 1 Not under consideration

9 VOTE

Allow custom IDs for documents when adding them to the discovery index

Whenever we face discovery setups with multiple stages or environments, its very hard and time consuming to manage multiple copies of the same document as discovery generates a new, different ID for each document in each collection. It would make ...

almost 7 years ago in Watson Discovery 1 Functionality already exists

Please enter your email address

FILTER BY CATEGORY