Skip to Main Content
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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Submitted
Created by Guest
Created on Jun 27, 2022

Exclusion of HTML navigation elements in webcrawl

As users of WDS are currently not able to use SDU on crawled web documents, it is impossible to use the field definition and exclusion function WDS provides to exclude unwanted results from the index.

In our case, website navigation and footers create noise that leads to bad query results. Inclusion of positive examples through enrichments and relevancy training was not enough to offset the noise. In most cases, stopwords cannot be used, as the navigation elements are still terms we need to be able to search for. The bad query performance has been noticed by customers and we're having trouble explaining to them that exclusion of those elements is apparently not implemented.


The URL to be crawled is which is a website about muscular diseases in German. The navigation bar containing all the possible muscular diseases will remain the same for all pages below this path level, navigation does not show up in the URL. For which is the top page about ALS, the index will still include all the navigation for the website. In the case of a search for another muscular disease, the ALS subpage will still be shown, only because it contains the navigation. Since navigation does not show up in the URL, it cannot be excluded by using url processing settings. Same goes for common footers about GDPR regulations and such.

Depending on how websites are crawled, it could be made possible in the following ways:

  • identify certain HTML elements by tag at ingestion time and give users an option for exclusion of HTML elements (processing settings for collections)

  • make SDU availabe for webcrawl documents to use the existing field filter function

  • exclusion by default at ingestion time

Needed By Week