Browse Prior Art Database

Method and System for Generating Tag Clouds based on Information Context Associated with a User

IP.com Disclosure Number: IPCOM000202111D
Publication Date: 2010-Dec-03
Document File: 3 page(s) / 23K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is provided to generate tag clouds based on information context associated with a user. An information constraint associated with the user is received and content associated with one or more other users is determined. The method and system then generates a tag cloud reflective of the content associated with the one or more other users with respect to the information constraint associated with the user.

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

Page 01 of 3

Method and System for Generating Tag Clouds based on Information Context

Associated with a User

Disclosed is a method and system for generating tag clouds based on information context associated with a user.

The method and system receives an information constraint associated with a user. This constraint is used to generate a tag cloud which is pertinent to the interests of the user. For example, a manager may use the constraint of "my department" to generate a tag cloud reflective of the electronic activity of his or her department.

In an instance, the information may be constrained manually by the user. For example, the user may specify individuals or departments whose activity is to be included in a tag cloud. In this example, the user may specify an individual and an organization, such as a department to which the individual belongs. Thereafter, an LDAP server containing organizational linkages is consulted to retrieve information associated with the indicated department, such as identifiers for other department members. Subsequently, the tag cloud is constructed to include activity information associated with the members of the department specified.

Alternatively, the information constraint may be chosen based on a policy. For example, the user may express relevant topics and the information constraint may be chosen from a list based on the policy. The policy may be enterprise wide, department wide, or have other scope.

The method and system allows the user to explicitly specify topics that need to be filtered, that is, which will not appear in the tag cloud. For example, the user may specify that topics on Cisco* are to be filtered. The topics may also be filtered based on policies defined by the user. For example, topics involving confidential information, acquisitions, code names selected from a list may be specified as topics to be filtered. In an instance, the user may specify a category, for example topics associated with

1


Page 02 of 3

non-business activities, to be filtered by default.

Similarly, the method and system also allows the user to explicitly specify topics or sources to be included, for example, via email. The topics may also be included based on a policy. For example, the user may specify that all documents represented in corporate mail, browser histories, and databases may always be included. In an exemplary instance, the user is allowed an option of excluding an electronic document from being used by other users. In another exemplary instance, the user may exclude a web page in the browser history from being used by other users.

In response to receiving the information constraint associated with the user, the content associated with one or more other users is determined. The content associated with the one or more other users includes, but is not limited to, web pages represented in the browser history, database upda...