Managing content moderation and flagged content
Edit configuration property settings in the contentreview-config.xml file to enable moderation and to specify what moderators should receive email notification when content requires moderation. Restart your applications to see the changes.
Before you begin
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client for details.
Configure IBM® Connections using scripts accessed with the wsadmin client. These scripts use the connectionsConfig object available in WebSphere® Application Server wsadmin client to interact with the IBM Connections configuration file, which is named contentreview-config.xml.
The properties in the contentreview-config.xml file cannot be edited using the updateConfig command nor displayed using the showConfig command. Instead, you must check out the configuration file using the checkOutContentConfig command, and then edit the property values by opening the checked out property file from the temporary directory using a text editor. After editing the property file, save the file in Unicode format and check the file back in using the checkInContentConfig command and restart the application servers to see the changes.
About this task
- If ownerModerate=true in contentreview-config.xml, a blog, forum, or community owner can moderate content for a blog, forum, or community they own. In addition, content an owner creates is published directly, without requiring moderation.
- If ownerModerate=false in contentreview-config.xml, only users assigned the J2EE moderator role in the WebSphere Application Server console can manage content on the site. For information on assigning users to the moderator role, see the topic Roles.
You can also configure the flag inappropriate content feature to specify categories for what type of content to flag, and to specify designated reviewers who will receive email notifications when content is flagged. There are two default categories for inappropriate content: Legal issue and Human resources issue. You can edit those categories, add new ones, or remove all categories. Configure automatic quarantine if you want flagged content automatically removed from Files, Blogs, Ideation Blogs, or Forums after an item is flagged a specified number of times. The file is also configured with placeholders for the email addresses of designated reviewers. Change those to actual email addresses for users assigned the moderator role who can review flagged content.
To change moderation configuration settings, complete the following steps:
Procedure
Configuring moderation for communities
Before you begin
Owners can control what content is added by members (pre-moderation) and remove anything that might be considered inappropriate in your organization (post-moderation). You can configure IBM Connections using scripts accessed with the wsadmin client. These scripts use the connectionsConfig object available in WebSphere Application Server wsadmin client to interact with the IBM Connections configuration file, which is named contentreview-config.xml.
The properties in the contentreview-config.xml file cannot be edited using the updateConfig command nor displayed using the showConfig command. Instead, you must check out the configuration file using the checkOutContentReviewConfig command, and then edit the property values by opening the checked out property file from the temporary directory using a text editor. After editing the property file, save the file in Unicode format and check the file back in using the checkInContentReviewConfig command and restart the application servers to see the changes.
About this task
Administrators configure the following section of the contentreview-config.xml file to set community moderation:
<commModerationConfiguration>
<preModeration>
<forceForAllCommunities enabled=boolean value of true or false />
<enabledByCreation enabled="true" />
</preModeration>
<postModeration>
<forceForAllCommunities enabled=boolean value of true or false />
<enabledByCreation enabled="true" />
</postModeration>
</commModerationConfiguration>
<service id="blogs">
<contentApproval enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
</contentApproval>
<contentFlagging enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
<service id="files">
<contentApproval enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
</contentApproval>
<contentFlagging enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
<service id="forums">
<contentApproval enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
</contentApproval>
<contentFlagging enabled=boolean value of true or false>
<ownerModerate enabled=boolean value of true or false/>
- preModeration
- Community owners must approve all content before it can be posted.
- postModeration
- Viewers can flag content.
- forceForAllCommunities
- Set to "true" to require moderation for communities. By default this attribute is set to "false". When the setting is set to false, moderation is not automatically required for a community, but moderation API command and filters still work. Moderators can still perform moderation tasks.
- enabledByCreation
- Setting determines if the moderation check boxes in the Start Community form should be checked when a user clicks Start a Community.
- contentApproval
- Set to "true" to require moderation for the specified application. By default this attribute is set to "false". When the setting is set to false, moderation is not automatically enforced for an application, but moderation API command and filters still work. Moderators can still perform moderation tasks.
- contentFlagging
- Set to "true" to require moderation for
flagged content. By default this attribute is set to "false".
When the setting is set to false, the user cannot flag content from
the user interface or using an API command. Blogs Moderation API
and filters still work. Moderators can still perform moderation tasks.
Files and Forums API commands returns errors.Note: If you upgraded IBM Connections from release 2.5 to release 3.0 or higher, the default for Blogs is "true" for compatibility reasons.
- ownerModerate
- Must be set to "true" to specify that community owners can moderate the content in communities that they own, otherwise it is set to "false". If contentFlagging or contentApproval for a service is set to false, then ownerModerate must be set to false.
Procedure
To change community moderation configuration settings, complete the following steps: