IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Not under consideration
Workspace Watson Discovery
Created by Guest
Created on May 13, 2019

RELATED IDEAS

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": [
                            {
                                "text": "program manager",
                                "location": [
                                    139,
                                    154
                                ]
                            },
                            {
                                "text": "program manager",
                                "location": [
                                    2001,
                                    2016
                                ]
                            }
                        ],
                        "relevance": 0.495976,
                        "type": "JobTitle"
                    },

 

When I issue the NLQ query  "2016" thinking that NLQ will only search ALL TEXT FIELDS, this document is returned. No other mentions of 2016 is in the document.

Enhancement request is that WDS NLQ not search fields that do not represent CONTENT of the document. An numerical offset does not reflect the contents of the document and is causing false positives in search results.

  • Guest
    Reply
    |     Sep 20, 2019

    Count and location in this example are both not document content.  I would also argue that the text of the entity should be included in the search, but the text of the entity mentions might be redundant since that text is already in the top level fields that were processed by NLU.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.