+

Search Tips   |   Advanced Search

Tips for tagging and rating


Tips for developers and portal administrators

Tagging and rating only supports the Portal 8.0 theme and the Page Builder theme.

The portal supports tagging and rating only with the Portal 8.0 theme and the Page Builder theme. If we select the Portal theme as the default site theme, the Tag Center might not be displayed as expected.

Administrators can assign users access roles for tagging and rating content. The portal user roles give users the following rights:

Users can only work with tagging and rating according to their access rights on portal resources.

Examples:

Limitation: There is not security handling for tag clouds. When a user clicks a tag, the resources are filtered by the user's access rights and then listed for the user to view. Consequently, users might see tags, even if they have no access rights on the tagged resources; when the click the tag, the list will be empty.

Only portal content can be pre-tagged.

We can pre-tag only portal resources, such as pages and portlets. We cannot pre-tag custom content or WCM content.

Tags in a virtual portal can be seen only is that virtual portal.

If the portal contains virtual portals, the tags and ratings are limited to the virtual portal in which they were created. It is not possible to share tags across several virtual portals. Consequently tags created in a virtual portal cannot be seen anywhere else.

Tagspace cleanliness

The portal implementation of tagging prevents tagspace littering. the inclusion of tags that do not contribute to categorizing content. This manifests mostly in the following two issues:


Staging and migrating tagspaces

We can transfer the tagspace from one portal to another, for example for staging, or for migrating from one portal version to another. You do this using xmlaccess.sh. For details refer to the topic about Migrating tagspaces.

Users can create private and public tags. Private tags are stored in the customization database, whereas public tags are stored in the community database. Only content of the community database is staged and migrated.


Tagging custom content requires UI development

If you want the users to be able to tag and rate custom content, you have to write code that allows finding this content using the public APIs. We also have to add the resources you want the users to tag to the portal. Custom content is anything apart from portlets, portal pages, and Web Content Manager resources. For details refer to the topic about Allow custom content to be tagged and rated and the section about Designing a portal site.


Tag filtering

We can apply tag filters to suppress words that you do not want to be used as tags in the portal. As we can have more multiple active filters, a tag must pass all filters to be applied. A simple filter is shipped with the portal. If you need more advanced filtering, you have to provide our own filters. For more information about creating custom filters, see How tagging and rating works in the portal and go to the section Filtering content for tagging.


SQL server URI length limit for custom resources

For SQL Server, tags for custom resources with URIs of which the scheme specific part in UTF-8 is larger then 850 bytes cannot be stored. As a workaround we can either use URIs with shorter scheme specific parts or drop the respective index in the database table. Due to this limitation, a warning about the index key length is written when transferring the database for SQL Server.


Tag Cloud, Tag Center, and Results List portlets do not support WSRP

The Tag Cloud and Tag Center portlets, including the Result List portlet, do not support WSRP. This means that it is not possible for a Producer portal to provide these portlets as remote Web services, or for a Consumer portal to consume them so that its users can use them.


Maximum number of available tags

By default the tag widget can show up to 50 different tag names. This limit applies separately to each kind of tags, community tags, personal public, and personal private tags. Configure these maximum values using the following two properties:

Increasing the 50 maximum figures can lead to slower responses of the default user interface of the tag widget. The number of tags per resource typically averages out at 5 to 8, as users tend to reuse tag names that other users used already and that the tag widget then suggests by the type ahead feature.

You configure these two properties globally in the CP Configuration Service for tagging and rating or for individual widgets in the widget properties. For details refer to the topics about the Parameter reference for tagging and rating, Portal configuration services, section CP Configuration Service for tagging and rating, and Setting service configuration properties.


Angled brackets are not allowed in tag names.

Angled brackets ( < and > ) are not allowed within tag names. Therefore no matter how you customize the regular expression, angled brackets are not accepted.


Tips for portal users

Tag names must contain at least one alphanumeric character. Tag names that consist only of non-alphanumeric characters are not allowed either. Example: "!^#" .

Tags in tag clouds do not reflect access rights. The tags shown in tag clouds do not reflect the access rights that users have on the tagged resources. Resources are filtered by access rights only after the user clicks a tag. This has the following consequences:


How can I avoid closing the widget when clicking on listed resource links?

Rightclick the line to view and select Open in New Tab. The widget will remain open, and we can proceed with the other links in the same way.


Type-ahead support requires at least 3 characters

When a user types a tag, the user needs to type at least 3 characters for the type ahead support feature to work.


Parent: Tagging and rating
Related: Search for tagged content
Federating tags
Design and setting up a portal site
Set service configuration properties
Delete orphaned data
How tagging and rating works in the portal
The tagging and rating user interface
Tagging and rating for static pages
Allow our own custom content to be tagged and rated
Configuration reference
Security for tagging and rating
Use xmlaccess.sh to administer tags and ratings
Administration of tag federation
CP Configuration Service for tagging and rating
How tagging and rating works in the portal
Allow our own custom content to be tagged and rated
Parameter reference for the tag and rating widgets