Compliance, the application for final approval of master content, usually operated by broadcasters or any other media outlets. The application enables a user to review the content and verify it complies with the local broadcasting regulatory.
It is an extensive collaboration tool that lets you decide whether the material is acceptable for airing or not. Comments made in this application will be included in an automated email subscription to notify selected recipients of your choice/decision. By approving a Master, the content is automatically transferred to the master play-out. In the process, the original asset is quality controlled to comply with the broadcaster's technical specifications.
Looking at the screenshot below you will find it also complies with the architecture of the other Mediabank applications. It contains the Search and Asset module on the left side, the Title, Player, Navigation and Status module in the center and Meta modules to the right side. At the top, you find the Header module. Since the different module functions are similar to all of the Mediabank applications, they are described in separate articles also found in the knowledge base.
- Search module
- Asset module
- Title module
- Player module - User guide: Using the Mediaplayer 360 and Navigation module
- Navigation module - User guide: Using the Mediaplayer 360 and Navigation module
- Status & Action modules
- Meta module
This article describes Compliance specific features such as:
- Workspaces 1, 2 & 3
- Status module
- Action module
The different workspaces
The above illustration show workspace 2 (W2). You have the choice to select a larger view of the content you are reviewing. Choose W1 to optimize the size of the player window and reduce the appearance of the meta-module.
The W1 and W2 are directed towards your visual perception and preferences only. Both workspaces are identical in functions.
Workspace 3 differs from the other two. The W3 is a log view of the asset's history. When was it uploaded, changed status by who and when, who commented what and when from where (cellular/workstation) and many other details you find interesting. This log view can also be configured by your local admin to reflect your work role.
The log view can be used as reference documentation of the approve/reject process and the decision made.
The Status & Action module
The Compliance and Review & Approval applications share the basic ideas in the review and approval process. While Review & Approval focus on reject or approve, Compliance uses additional rules in the process.
The media content can be rejected but the nature of rejection could reflect visual or sound elements and not the content it selves. You can reject the media file but accept the subtitling.
Or, you can accept the media content as long as it confirms with the Ofcom rules that you apply. The additional rules in your compliance process can be adjusted to reflect any broadcaster's own approval processes.
The "human" process in Compliance is very simple. You watch the media content, write your comments, change status, add the Ofcom rules and simply press the Submit button. That's it.
However, you have commented on the media content in general terms. Maybe you have commented specific scenes but it is not easy for the producer/project manager to understand in detail what and wherein the one-hour-long media file you specific mention.
To add more detail and quality to the compliance process, you can use the Navigation and Annotations module to select scenes with accuracy down to the frame level, leaving no room for failure.
Read more in related articles about the use of the navigation/annotation module (5) and the Meta module (7).