Watson Discovery

Showing 250 of 15643

Method / Option within Sync Setting to initiate a complete reload of the documents that have already been crawled.

Currently even if you make changes to the schedule or the SDU collection, which is the normal trigger to re-read a set of documents or Web site that has already been crawled. Documents that have not been altered / edited will not be include within...

over 5 years ago in Watson Discovery 0 Not under consideration

1 VOTE

Return Lemma for the sentences while using Rule Based model

Return Lemma for the sentences while using Rule Based model, Provide API access to retrun the lemma's ,surface forms

over 5 years ago in Watson Discovery 0 Not under consideration

1 VOTE

NLQ should not search numeric fields that specify e.g. offset of entity within text

The json document https://ibm.box.com/s/32mis3zwbzk3t913wdrbmcl30i3at129 ingested into WDS ends up with this out of the box NLU detected "Jobtitle" entity, with location offset ending at 2016: { "count": 2, "text": "program manager", "mentions": ...

over 5 years ago in Watson Discovery 1 Not under consideration

1 VOTE

Retain new line formatting with SDU

For customers who used non-SDU collections, some of them were using "html" field to retain formatting of text. Now with SDU, this feature is no longer there. We understand that retaining formatting is not possible in SDU. However, newlines are als...

over 5 years ago in Watson Discovery 1 Planned for future release

1 VOTE

Update Entity Type Version 2 for NLU pre annotation for supported languages

Although the latest version of NLU use Entity Type Version 2 for Italian and some other languages, WKS still uses NLU Version 1 for all languages, not just Italian. Until WKS will use V1 version for pre annotation the new V2 entities will not be ...

over 5 years ago in Watson Discovery 0 Not under consideration

1 VOTE

Smart Document Understanding returns document structure

Right now, the output of SDU is aggregated into a JSON array. It would be great if SDU could return the parsed structure of the document. This way we can know for sure if this word in the document is a 'Table of Content' type, or 'Subtitle' type.

over 5 years ago in Watson Discovery 1 Functionality already exists

1 VOTE

Extract insights from an image using smart document understanding (WDS)

IBM Sellers, Offering managers and marketing team can extract Use case1: Extract the company location in the magic quadrant like if IBM is listed in Leader's quadrant (Currently WDS can extract the list of companies present in the image) Use case2...

over 5 years ago in Watson Discovery 1 Not under consideration

1 VOTE

Include Query parameter in results from the query and event log

When we query the /logs for a particular query ID, we can get the natural_language_query paratmer returned which contains the query string. { customer_id: '', environment_id: 'XXXX', natural_language_query: 'are there any capital metrics?', query_...

over 5 years ago in Watson Discovery 2 Not under consideration

1 VOTE

Stop words should not impact phrases in Discovery Query Language

WDS enables you to define your own set of stop words. We recently noticed that the stop words are removed from searches even when using phrases with the Discovery Language syntax. For example if we search for the phrase "we the people" and we and ...

almost 6 years ago in Watson Discovery 0 Not under consideration

1 VOTE

Add support for Finnish language

Finnish language as an example - we have build support for finnish and swedish language for Watson Explorer (oneWEX and AC Miner) using external language parser. There is guidelines available internally to IBM and BPs how to do it. We believe our ...

almost 6 years ago in Watson Discovery 0 Planned for future release

Please enter your email address

FILTER BY CATEGORY