The portal tag cloud
The portal provides a tag cloud for aggregating tags for multiple resources. Users can select tags from the tag cloud.
The tag cloud is available as a portlet and as a Dojo widget. You can add the tag cloud portlet to any page as required.
The tag cloud shows the tags in alphabetical order. The font size indicates how often the tag has been applied within a defined scope. The larger the font of a tag is, the more often it as been applied. Users can select from the following options:
For more details refer to the help topic about the Tag cloud.
- Users can view in a cloud view or in a list view:
- In the cloud view users can determine whether they wan to view more or fewer tags by moving a slider to the left or right.
- The list view has a pagination bar.
- Users can select different tag cloud views to filter what is displayed in the tag cloud:
- The All view shows all tags that have been applied by users in the portal. This includes all community tags and all personal public and personal private tags of the user who is viewing the tags.
- The Community view shows all public tags applied by other users, except for the user's own personal public tags.
- The Personal view shows only the public tags that the user who invoked the cloud has assigned.
- The Latest view shows only the tags that have been created most recently.
- The Private view shows only the private tags that the user who invoked the cloud has assigned.
- Administrators can configure the following additional settings:
- Whether they want only related tags to be displayed when a users clicks a tag. For example, if a user clicks a tag TAG_1 Related means that the tag cloud then shows only the tag TAG_1 clicked by the user and all tags that have been applied to resources to which TAG_1 has also been applied. Tags that have been applied to resources without being in combination with TAG_1 are not shown.
- The minimum number of tags that they want to be displayed when the user moves the slider all the way to the minimum position
- The maximum number of tags that they want to be displayed, that is when the slider is moved all the way to the maximum position.
- The default number of tags that they want to be initially displayed and the corresponding position of the slider.
- Users can select between different scoping modes:
- Users can change the scope for which they want to view tags, for example books or movies. Users or administrators can configure the available scopes, depending on their access rights. For details about this refer to the topic about Configuring the tag cloud.
- Users or administrators can configure the available scopes by using the option Edit shared settings from the tag cloud context menu. When a users selects a scope, only tags that have been assigned to resources in that scope are displayed.
- The tag cloud can also be scoped in a way that it only shows tags that have been assigned to resources of a certain category or type schema. For details refer to the section about scoping modes.
The tag cloud portlet has several configuration options. You can configure each individual tag cloud portlet instance separately by using its Edit shared settings menu. For details refer to the help topic about Configuring the tag cloud.
Action modesAdministrators can set two action modes for the tag cloud. When a user clicks a tag, the result varies, depending on the selected option:
Redirect to Tag CenterIf the administrator selected this action mode and the 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. In the Tag Center users can select multiple additional tags. This can help narrow down large result lists. Clicking selected tags again deselects them; alternatively, tags can be deselected via the result list portlet (see …).
Expose a public render parameterIf the administrator selected this action mode and the user clicks a tag, the tag cloud exposes a public render parameter to which other portlets can react.
Scoping modesThis setting allows administrators to define the scopes that users can select or that are used to auto-scope the cloud when it is rendered. The following options are available:
Apart from administrator scope settings, other components that reside on the same page as the tag cloud can also transmit scopes. For example, this can be portlets or widgets on the same page. Depending on this, additional options on the pull-down menu allow you to define the following:
- The tag cloud does not allow for any scoping at all
- The tag cloud performs scoping based on type schemas or categories. For details about this refer to the topics about Configuring the tag cloud and How tagging and rating works in the portal, section about Grouping tags and ratings via resource categorization.
The scoping settings can lead to the following scenarios:
- Whether and from which set of scopes a user can manually select: from the set of scopes defined by the administrator, the set of scopes transmitted by other components, or both.
- To which scopes you want the tag cloud to scope when it is initially rendered. This can be the set of scopes defined by the administrator, the set of scopes transmitted by other components, or both.
- 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 that are 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 that are available, or it scopes to the union of all scopes that the administrator has specified. You can configure which of the two actions is performed as described above: 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 scopes that 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 scopes that all components transmit, and users can change to another scope.
Parent
The Tag Cloud
Configure the tag cloud