Configure the tag cloud

Administrators can configure the Tag Cloud portlet. Configure each individual tag cloud portlet instance separately. To do this, use the Edit Shared Settings option from the portlet menu.

Configure the following options:

Action modes

We can choose between two action modes. Depending on the option that selected, clicking a tag by a user can have to two different results:

Redirect to tag center

If you have this action mode selected and a user clicks a tag, the portal displays the Tag Center. It shows a list of resources that have been tagged with the tag that the user selected.

Expose public render parameter

If you have this action mode selected and a user clicks one or more tags, the tag cloud exposes the following shared render parameter containing the set of selected tags to which other portlets can react:

http://www.ibm.com/xmlns/prod/websphere/portal/v8.0/portal-contextual-portal}st

Scoping modes

Administrators can use this setting to define the scopethat users can select on used to auto-scope the cloud when it is rendered. Select the scoping mode for the tag cloud. We can set scoping either by categories, or by type schemes, or no scoping.

No scoping

If we select this scoping mode, the tag cloud will not be scoped.

Scope by categories

This scoping mode scopes the tag cloud by categoriedefined. Example categories are books or movies.

Scope by type schemas

This scoping mode scopes the tag cloud by type schemas defined.

For example, for pages and portlets this is usually a URI that begins with the string http:// .

Use the following entry fields to type categories and type schemas to use as scopes:

Categories to be used as scopes

Type the categorieto make available as scopes. Specify a comma separated list.

These scoping selections are not relevant for the IBM Connections tags view. In the IBM Connections view you scope explicitly by selecting the corresponding check boxes in the IBM Connections tags area.

Type schemas to be used as scopes

Type the type schemas to make available as scopes. Specify a comma separated list.

Select from the following pull-down menus to determine which scopes to show to users for selection and which scopes to preselect for automatic scoping:

Scopes displayed for selection by the user

Use this selection menu to determine which scopes to make available to users for scoping their tag cloud:

Preconfigured scopes

Allow scopethat you configured by categories or type schemas.

Transmitted scopes

Allow scopethat portlets transmit as additional scopes.

Preconfigured and transmitted scopes for the selected tags

Allow both preconfigured and transmitted scopes.

None

When we select this option, no scopes will be shown for selection to users.

Preselected scopes

Use this selection menu to define which scopes will be preselected for automatic scoping of the tag cloud:

Preconfigured scopes

Preselect scopethat you configured by categories or type schemas.

Transmitted scopes

Preselect scopethat portlets transmit as additional scopes.

Preconfigured and transmitted scopes

Preselect both preconfigured and transmitted scopes.

None

When we select this option, no scopes will be preselected for tag clouds.

Setting the scoping modes can lead to the following scenarios:

• The administrator has specified no scopes, and none of the components transmits a scope. In this case the tag cloud portlet does not perform any scoping, but displays a subset of all tags available.

• The administrator has defined scopes, and none of the components transmit a scope. In this case the tag cloud portlet either performs no scoping, but displays a subset of all tags available, or it scopes to the union of all scopethat the administrator has specified. Configure which of the two actions is performed as previously described under Action modes: Redirect to the tag center or Expose a public render parameter.

• The administrator has specified no scopes, but components transmit a scope. In this case the scope is initially set to the union of all scopethat all components transmit; by default users cannot change to another scope.

• The administrator has defined scopes, and components transmit a scope. In this case the scope is initially set to all scopethat all components transmit and users can change to another scope.

For more details about scopes, how they work, and how we can use them see For more information and a scoping example see How tagging and rating works in the portal and go to the section Grouping tags and ratings via resource categorization.

Display Settings

Select from the following options as required:

Default view mode

Choose between Cloud and List view modes by clicking the appropriate radio button:

Display related tags only

If you check this option, the Tag Cloud portlet shows only tags that have been applied to the listed resources, not the tags that are generally most popular. In other words, this option suppresses tags that have not been applied to the listed resources. Checking this option can make it easier for users to find content related to the selected tags.

Lowest number of tags at minimum position of slider

Select the minimum number of tags that the tag cloud shows to users. This number also defines the minimum position of the slider or other user interface control for scrolling the listed tags.

Maximum number of tags to display

Select the maximum number of tags that the tag cloud can show to users. This number of tags is shown to users when they place the slider at the maximum position.

Number of tags initially to be displayed

Type a number to define the default position of the slider or other user interface control for scrolling the listed tags. This number also determines how many tags are shown by default.

IBM Connections features to be used as scopes

If an IBM Connections server is integrated into the WebSphere Portal, check boxes for IBM Connections features such as Activities, Blogs, Bookmarks, Communities, Files, Forums, Profiles, and Wikis are displayed. Each IBM Connections feature can be deselected individually. Clicking the All check box selects or clears all of the IBM Connections features. When we select an IBM Connections feature, the corresponding IBM Connections tags are integrated in the IBM Connections tags view. If configured correctly, the tags will also be integrated in the All view of the tag cloud.

One or more IBM Connections check boxes can be hidden by setting a comma separated list of check box identifiers in the custom property com.ibm.wps.cp.tagging.federation.ui.disabled.idlocated in the WP CPConfigurationService Resource Environment Provider. For details about how to set properties in the Portal Configuration Service, see the topic about Setting service configuration properties. The identifiers of the Connections check boxes are: All, Activities, Blogs, Bookmarks, Communities, Files, Forums, Profiles, and Wikis.

For example, if you do not want the Blogs and Profiles check boxes to be shown, use the value Blogs,Profiles for the properties. We can integrate IBM Connections tags in the All view by selecting the check box Display IBM Connections tags in the All view.

Visible views

Check all viewto make available to users to select from:

All tags

Select this view so that users can choose to view all tags available in the portal.

IBM Connections tags

Select this view so that users can choose to view IBM Connections tags.

Others' tags

Select this view so that users can choose to view the tags that other users applied.

My public tags

Select this view so that users can choose to view only those portal tags that they have assigned themselves.

Latest tags

Select this view so that users can choose to view only the most recently created public portal tags.

My private tags

Select this view so that users can choose to view only those portal tags that they have assigned as private tags.

Click Submit to save the changes. To return to the tag cloud portlet without saving your changes, click Cancel.

Parent: Tag cloud
Related reference:
How tagging and rating works in the portal