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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


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.

Example:

The URL to be crawled is https://www.dgm.org/muskelerkrankungen/ 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 https://www.dgm.org/muskelerkrankungen/amyotrophe-lateralsklerose-als 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