Home

 

Configure the flag as inappropriate feature

Edit configuration property settings in the contentreview-config.xml file to configure the flag as inappropriate feature for Blogs to specify categories and designate reviewers. Restart the Blogs application to see the changes.


Before you configure this feature, follow the steps in the topic Specifying an administrator e-mail address for Blogs to designate an administrator e-mail address for sending automatic notifications. This is a required step.

To edit configuration files, use wsadmin. See Start the wsadmin client for details.

You can configure the Blogs feature that allows users to flag a blog entry as having inappropriate content by specifying categories for what type of content to flag, and to specify designated reviewers who can take action on flagged content. Blogs is configured with two default categories: Legal issue and Human resources issue. You can edit those categories, add new ones, or remove all categories. The file is also configured with placeholders for the email addresses or login names of designated reviewers. Change those to actual email addresses or login names for users who can review flagged content. Changes are made when you save the file, check it in, and restart the Blogs application; no server restart is required.

  1. From the AppSrv0#/bin where Blogs is installed, open a command window and start the wsadmin command line tool as described in the topic, Starting wsadmin.

  2. Start the Blogs script interpreter by entering the following command:

    • Single server: 

        execfile("blogsAdmin.py")

  3. Cluster: 

      execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/blogsAdmin.py")

  4. To check out the contentreview-config.xml file to a temp working directory... 

      BlogsCheckOIConfigService.checkOutContentConfig("<temp-dir>", "<cell-name>")

    where <temp-dir> is the is the temporary working to which the configuration XML and XSD files are copied. The files are kept in this working while you make changes to them. And wherecell_name is the name of the WebSphere Application Server cell hosting Blogs. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care.

  5. From the temporary to which you just checked out the Lotus Connections configuration files, open the contentreview-config.xml file in a text editor.

  6. To add designated reviewers who can review and act on flagged entries, replace the placeholder email names in the following section with the email addresses of designated reviewers. Provide an email address for each reviewer and make sure they have Administrator access to the Blogs application. Note that there are different reviewers for each category. If your deployment does not support email addresses, you can enter login names instead. Remove whichever identifier you do not need. 

      <reviewer> 
    <email>reviewer1@acme.com</email> 
</reviewer> 
<reviewer> 
    <email>reviewer2@acme.com</email> 
</reviewer> 
<reviewer> 
    <userid>userid1</userid> 
</reviewer> 
<reviewer> 
    <userid>userid2</userid> 
</reviewer>

  7. To add a category, add a new <content-category> element with a unique id and descriptions in the desired languages. Tip: The fastest way to add a content category is to copy an existing <content-category> element, paste it into the file and edit the ID and descriptions in the required languages. For example, to add a content category for "Offensive Language" add the following: 

      <content-category>
    <id>003</id>
    <description xml:lang="en">Offensive Language</description>
    <description xml:lang="fr">French equivalent</description>
    <description xml:lang="it">Italian equivalent</description>
    <reviewer> 
        <email>reviewer1@acme.com</email> 
    </reviewer> 
    <reviewer> 
        <email>reviewer2@acme.com</email> 
    </reviewer> 
    <reviewer> 
        <userid>userid1</userid> 
    </reviewer> 
    <reviewer> 
        <userid>userid2</userid> 
    </reviewer> 
</content-category>

    Note that the new ID is “003”. This must be unique. As this example shows, you can also add language statements and provide translated strings for category names.

  8. Save your changes to the contentreview-config.xml file.

  9. Check the file back in, using the command: 

      BlogsCheckOIConfigService.checkInContentConfig(<temp-dir>,"<cell-name>")

    During the check-in process validation is done to ensure no xml syntax errors are in the file.

  10. Restart the Blogs application to see the changes.


Administer Blogs using the wsadmin Client

 

Related tasks

Start wsadmin

Specify an administrator e-mail address for Blogs notifications

Manage flagged content

+

Search Tips   |   Advanced Search