Compliance is the application for final approval of master content, usually operated by broadcasters or other media outlets. The application enables users to review the content and verify it complies with the local broadcasting regulatory.
It is a comprehensive collaboration tool that lets you decide whether the material is acceptable for airing or not. Mediabank Compliance will include the user's comments and forward them using 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. The original asset is quality controlled to comply with the broadcaster's technical specifications in the process.
Looking at the screenshot below, users 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 on the right side. Finally, at the top, you find the Header module.
Since the different module functions are similar to all Mediabank applications, they are written in separate articles found in the knowledge base.
- Search module
- Saved searches
- Advanced search
- Asset module
- Title module
- Player module
- 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 by choosing 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. First, the W3 is a log view of the asset's history.
Users can reveal details like:
- When it was uploaded.
- Who changed its status and when.
- Who commented what, and when.
Your local admin can also configure this log view to reflect your work role.
When reference documentation is needed, the users can use the log view to retrieve the decisions made during the compliance process.
The Status & Action module
The Compliance and Review & Approval applications share the basic ideas in the review and approval process. However, while Review & Approval focuses on rejection or approval, Compliance uses additional rules in the process.
The Compliance application can reject the media content, but the nature of rejection could reflect visual or sound elements and not the content itself. For example, a user may reject the media file but accept the subtitling or the media content as long as it confirms the Ofcom rules applied.
Compliance can adjust additional rules in the compliance process to reflect any broadcaster's approval processes.
The "human" process in Compliance is straightforward. The controller watches the media content, writes comments, changes status, adds the Ofcom rules, and presses the Submit button. That's it.
However, the comments can reflect on the media content in general terms. But sometimes, the comments are related to specific scenes.
How can the producer/project manager understand the specific comments in the one-hour-long media file?
The controller can use the Navigation and Annotations module to add more detail and quality to the compliance process 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 (Components) (7).