The Kaltura platform provides publishers with lots of great features and abilities. In this post and the next we will dive into some of the moderation features.
A KalturaBaseEntry object includes moderation status which indicates whether the entry needs to be examined by an administrator or was already decided as an approved or rejected content. An Entry that awaits on the moderation queue is not yet available for public use, thus prevents unauthorized content from being automatically published on your site.
The default behavior of every Kaltura account is that every uploaded entry is automatically marked as approved which means it does not have to go through any moderation process. This default behavior was set because most publishing work-flows are editorial in nature, where only authorized people can ingest content.
The default behavior can be changed (per account, through the Admin Console) so that every uploaded entry will be marked as pending moderation. Then entries are not accessible to users without proper permissions. Only a moderator (user with moderation permissions) will need to approve or reject the entry.
An entry that was rejected will not be playable by users without moderation permissions.
The ‘moderate’ tab in the KMC (under the ‘content’ tab) allows publishers to see the ‘moderation queue’ where all entries marked as pending are waiting to be approved or rejected. Here content moderators can change moderation status (approve/reject).
Editorial vs. Crowd Sourcing
Sites may define their moderation policy according to their targeted audience, age groups and type of content on the site. It is a frequent demand to allow even a UGC (User Generated Content – Content that was uploaded by end-users who are not moderators or admins of the site) to be automatically approved and published, yet allow other end-users of the site to notify the site admins if a certain content should be removed, for example, if the content is hurtful, not appropriate or violating rights.
In Kaltura, entries can be “flagged” for review by calling the BaseEntry.flag API call. Then content managers can see a list of entries that were marked as flagged and determine if that content should be approved or rejected. This functionality is also implemented as a KDP plug-in available from the Player Studio.
The Flagging capability is available to any publisher account, regardless of its moderation policy set in the Admin Console.
Got Moderation Setup, Now What?
The moderation queue in the KMC ‘moderate’ tab is one way to review and approve or reject content. Yet often, the KMC tab may not be enough, if your site receive more than hundred uploads each day, you may want to consider other approaches such as mobile apps to monitor and moderate everywhere without being next to computer, using crowd-sourcing tools like Mechanical Turk or leveraging automatic filtering services.
Tune in for the next post in the series where we’ll share an application for mobile moderation.