Hints and tips for tagging and rating
Learn about some hints and tips that apply to tagging and rating.
Hints and tips for developers and portal administrators
Tag and rate only supports the Page Builder theme.The portal supports tagging and rating only with the Page Builder theme. Therefore, if you 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:
USERThe user can view tags and ratings that other users have applied.
PRIVILEGED USERThe user can also apply private tags and ratings.
CONTRIBUTORThe user can also apply public tags and ratings
MANAGERThe user can also modify tags and ratings that other users have applied.
Users can only work with tagging and rating according to their access rights on portal resources.Examples:
- Users can only tag and rate portal resources that they can access.
- When users click a tag in the tag cloud, they can only view resources that they can access.
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.You can only pre-tag only portal resources, such as pages and portlets. You cannot pre-tag custom content or Web Content Manager content.
Tags in a virtual portal can be seen only in that virtual portal.If the portal contains virtual portals, the tags 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 cleanlinessThe portal implementation of tagging prevents tagspace littering, that is the inclusion of tags that do not contribute to categorizing content. This manifests mostly in the following two issues:
- Redundant tags resulting from similar names or spelling variants, for example, web20 and Web 2.0. The portal reduces such duplicate tags by a syntactical type ahead feature.
- Tags pointing to resources that have been deleted. You can use the portal administrative cleanup tool SLChecker to check for invalid links from tags to resources that do not exist any more and for tags that someone applied who is not a portal user any more.
Staging and migrating tagspacesYou 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 by using xmlaccess.sh. For details refer to the topic about Migrating tagspaces.
Only public tags are staged and migrated.Users can create private and public tags. Private tags are stored in the customization database, public tags are stored in the community database. Only content of the community DB is staged and migrated.
Tagging custom content requires UI developmentIf you want users to be able to tag and rate custom content, you have to write code that allows finding this content by using the public APIs. You also have to add the resources that you want 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 Allowing own custom content to be tagged and rated and the section about Designing a portal site.
Tag filteringYou can apply tag filters to suppress words that you do not want to be used as tags in the portal. 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 own filters.
SQL server URI length limit for custom resourcesFor 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 you 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 WSRPThe 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 tagsBy 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. You can configure these maximum values by 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.
- For community tags: com.ibm.wps.cp.tagging.dialog.maxCommunityTags
- For personal tags: com.ibm.wps.cp.tagging.dialog.maxPersonalTags .
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.
Hints and 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 rightsThe 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:
Users might see tags without underlying resourcesUsers might see tags applied to resources to which the users have no access. As a result, if they click a tag that has been only applied to resources to which they have no access, they view an empty resource list.
Tag size does not represent frequency of the tag on resources that a user can access.When a user views a tag cloud, tag sizes in the tag cloud represent how often the tag has been applied within the portal by all users, not how often the tag has been applied to resources that the user can access.
How can I avoid closing the widget when clicking on listed resource links?Rightclick the link that you want to view and select Open in New Tab. The widget will remain open, and you can proceed with the other links in the same way.
Type-ahead support requires at least 3 charactersWhen 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
Search for tagged content
Design and set up a portal site
Related tasks
Set service configuration properties
How tagging and rating works in the portal
The tagging and rating user interface
Tag and rate for static pages
Allow own custom content to be tagged and rated
Configuration reference
Security for tagging and rating
Use xmlaccess.sh to administer tags and ratings
CP Configuration Service for tagging and rating
Parameter reference for the tag and rating widgets