Configure the tagging feature

Edit settings in the profiles-policy.xml file to configure the tagging feature.

The tagging feature allows users to assign meaningful keywords to their own profile and other users' profiles, making it easier to find people with a particular interest or expertise. We can control whether users can tag themselves and others by enabling or disabling the tagging feature for specific profile types. We can also configure access control settings for this feature according to profile type.

• When tagging is disabled, the tags widget is not automatically hidden in the user interface. To hide the widget, delete or comment out the relevant widget entry in the widget-config.xml file. See Manage widgets in Profiles.

• When tagging is disabled for a given user type, the user's existing tags are still searchable; there is no mechanism available for controlling access to the tags from a reading and viewing perspective. If we choose to display the tags widget but you disable tagging for a particular user type, it might cause confusion for the users when search results include tags for a particular profile, but the tags do not display in that profile.

To enable or disable tagging by profile type:

1. Check out the profiles-policy.xml file:
   cd app_server_root/profiles/Dmgr01/bin
   ./ wsadmin.sh -lang jython
   execfile("profilesAdmin.py")
   ProfilesConfigService.checkOutPolicyConfig("</tmp>", "cell_name")

   To get cell name...

   print AdminControl.getCell()

2. Open the profiles-policy.xml file using a text editor, from the temporary directory to which it was checked out.

   Edit the following properties for the tagging feature as needed.

   profile.tag

   Controls user access to add tags to their profile.

   Access levels for this property can be defined using one of the following scopes:

   • none. No one can tag the profile of users with the specified profile type.

   • self. Users with the specified profile type can tag their own profiles. Administrators can also tag the profiles of users with the specified profile type.

   • colleagues_not_self. Only people who belong to the network of the user with the specified profile type, and who have the person role, can tag the user's profile. Users with the specified profile type cannot tag their own profiles.

     If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.

   • colleagues_and_self. People who belong to the network of the user with the specified profile type, and who have the person role, can tag the user's profile. Users with the specified profile type can tag their own profiles.

     If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.

   • person_not_self. Users with the person J2EE role can tag the profile of users with the specified profile type. Users with the specified profile type cannot tag their own profiles.

     If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.

   • person_and_self. Users with the person J2EE role can tag the profile of users with the specified profile type. Users with the specified profile type can also tag their own profiles.

     If resourceOwner is specified on the access check, the resource owner constraint must also be met, unless the user has the self role.

   For example:

   <feature name="profile.tag">
     <profileType type="default" enabled="true">
      <acl name="profile.tag.add" scope="person_and_self" /> 
     </profileType>
     <profileType type="contractor" enabled="true">
      <acl name="profile.tag.add" scope="colleagues_and_self" /> 
     </profileType>
     <profileType type="visitor" enabled="false">
      <acl name="profile.tag.add" scope="none" /> 
     </profileType>
   </feature>

   This code sample enables tagging for users with the default profile type. Users with the person J2EE role can tag users of the default profile type, and default users can tag their own profiles. Tagging is also enabled for users with the contractor profile type. People in the profile owner's network who have the person role can add tags to profiles of the contractor type, and contractor users can tag their own profiles. Tagging is disabled for users with the visitor profile type.

3. Save the changes and check the profiles-policy.xml file back in :
   ProfilesConfigService.checkInPolicyConfig()

4. To exit the wsadmin client, type exit at the prompt.

5. Stop and restart the Profiles server.

Parent topic:
Configure profile features

Related:

Manage widgets in Profiles