Browse Prior Art Database

Improved tag cloud

IP.com Disclosure Number: IPCOM000214942D
Publication Date: 2012-Feb-15
Document File: 2 page(s) / 22K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article proposes a new technique for an improved tag cloud which allows the tag cloud to adapt to the search query that was used by a user in a web search engine.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Improved tag cloud

Tagging and tag clouds are well known concepts in prior art. A web site displays a tag cloud that contains a set of tags, which were created by the users or were created automatically through further prior art functionality. The tags allow quick and easy navigation and searching: e.g. a user clicks on a tag contained in the tag cloud and the web site shows a list of resources that are associated with this tag, allowing him to easily find and access the resource.

Typically there are a lot of user-generated or automatically created tags in the web site so that its a non-trivial task to select the relevant tags to be included in the tag cloud. Prior art tag clouds may use a metric that is based on tag frequency, i.e. the tag cloud component counts tag frequency and selects the n most frequent tags, choosing a formatting that represents the tag frequency graphically (e.g. by font size). The problem with this simple approach is that it ignores the users current interest and in many cases selects an inadequate set of tags, i.e. selects tags that are not relevant for the user and simultaneously misses tags that are relevant. This shortcoming may drastically reduce the usefulness of tagging for the user.

This article proposes a new technique for an improved tag cloud which allows the tag cloud to adapt to the search query that was used by the user in a web search engine.

When the user follows a link from the search engine to the web site, the browser sends a HTTP request to the web site, and the request contains the Referer...