Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Created by Guest
Created on Feb 3, 2021

Include multiplier operator on filter

The multiplier operator only works on the query paramter. -

It would be useful if it could be used on the filter paramter or at least specify in the documentation that its a query exclusive operator.

  • Guest
    Feb 5, 2021

    I made the incorrect assumption that natural language query (returning passages) gives the same results as a structure query using the ’:’ operator. Please refer to the following post:

    In this case a multiplier operator on the filter parameter is a possible solution.

  • Guest
    Feb 3, 2021

    Given documents with fields product and text.

    Currently, I use a natural language query and filter by specific products as follows:

    Query:text:Where is this?


    I want to filter by the product field whilst weighting specific product fields with the multiplier operator. In the above example, I use the multiplier on product2 to improve its score. I would expect the following...

    Query:text:Where is this?


    At this point, I cannot use the multiplier on the filter; therefore, I would use my filter query on the query parameter instead of the filter parameter. To achieve the results, I'm looking for I have to do the following query...

    Query:text:Where is this?,(product::product1|product::product2^2)

    I understand the query is used to impact score; however, in my use case filter becomes redundant as I'm forced to filter using the query parameter. I think it would be useful to specify this in the documentation to be clear.

  • Guest
    Feb 3, 2021

    Hi Philip - what are you trying to do with the operator in filter exactly? I believe in query it's used to impact score however filter is not scored, thus nothing that affects score would be applicable