What is the Content Localization Portal?
Request Status and Current Step
Overview
This document serves as a guide to the Content Localization Portal Dubbing Request Management. The CLP is a work in progress. Updates will be added.
What is the Content Localization Portal?
The Content Localization Portal (CLP) is a project management application designed to house apps and pieces of the dubbing process in one toolset. The vision is to provide accurate information, which is organized in a digestible manner, generating actionable tasks for all users.
In other words…the CLP is a Netflix tool for dubbing requests (dialogue lists, pivot language dialogue lists, as-recorded dub scripts, and audio descriptions scripts) management.
🗒️ NOTE:
- Linguists should not have access to the CLP
- The CLP is a work in progress. Updates will be documented here.
Access
- To access the CLP, users must have the dub portal user role in Starship.
- To access the Authoring tool, linguists must have a dialogue list author and/or dialogue list proofreader role in Starship.
How does the CLP work?
There are 5 Parts to the Content Localization Portal:
- Projects
- Schedule
- Show Guide
- Request Management
- Communication
This document will focus on request management in the tool.
My Projects
Upon going to https://contentloc.netflixstudios.com/, the user will be directed to the “My Projects” page of the Content Localization Portal. This is the user’s homepage that houses all “followed” projects.
Image 1 My Projects
Requests Page
The user may navigate to the requests page by selecting a project from My Projects page. Once in the project, select the hamburger menu on the navigation bar on the left-hand side of the page to access the Requests page.
Image 2 Requests Icon
The Requests page allows the user to assign requests including dialogue lists, pivot language dialogue lists, audio descriptions, and as-recorded dub scripts to authors and proofreaders. It also provides visibility to the current status of the requests.
Request Columns
Requests have 8 attributes. The following section outlines each column with its description.
Image 3 Columns
| Column Header | Descriptions |
|
A. Title |
|
|
B. Episode |
Episode Number |
|
C. Type |
Asset type |
|
D. Original Language |
Source language |
|
E. Target Language |
Translation language |
|
F. Latest Cut |
Latest video proxy. New proxies will appear below the current in orange font |
|
G. Status |
Workflow status |
|
H. Current Step |
Current stage in the workflow |
|
I. Due Date |
The date request is due |
Customize
Users may customize columns by
- Sorting alphabetically or numerically by the selected column
- Locking (or freezing) columns to the start or end of the page
Image 4 Lock Start
- Autoresizing columns to fit
- Adding or removing columns
Image 5 Remove Type and Original Language columns
Users may also reorder columns by selecting and dragging them to the desired location.
Image 6 Reordering status and locked cut
Filtering Requests
Filtering requests allow the user to narrow down search results to find a certain request(s). Users can filter by language, asset type, request ID, and episode number.
Image 7 Filtering by target language and episode
Saved Filters
Users may save filters and use them across projects. To do so, follow the instructions below:
- Select desired filter settings.
- Select "Saved Filters."
- Name the filter and select "Save New Filter."
Image 8 Saving a Dialogue List filter
Request Workflow at a Glance
To understand a request’s workflow, the user can compare it to a relay race.
First, the user must assign the runners: author and proofer. Then, the author must script the task. Once they’ve completed their task, they pass it to the proofer who double-checks their work. And then the race is complete! If there are QC errors, however, the cycle repeats until there are no more errors.
Image 9 Workflow Overview
Request Status and Current Step
A request goes through different statuses at each stage of the workflow. This assists in tracking deliveries.
Image 10 Request is In Progress while the Author is fixing the script
A description of each status and current step of an As Recorded Dub Script in the CLP:
Happy Path: When the request is accepted.
| Stage | Status | Current Step |
| Once a dubbing request has been created it will wait for a proxy to become available. For the first pass (transcription/translation), this can be any proxy type (LOCKED CUT, SERVICING MASTER, IMF). For the second pass (conformance), it will wait until a final proxy is available (SERVICING MASTER, IMF). | Waiting for Proxy | Assignment |
| The task is not ready depending on the current stage or the proxy not being available. | Not Ready | Assignment |
| The task is ready for authoring or proofing because the script and proxy are locked. | Ready | Assignment |
| As Recorded Dub Script delivered to Backlot | Dub Script Delivered | QC in Progress |
| As Recorded Dub Script processed in Backlot | Delivered | Translation Delivered |
| Asset QC in Progress | Dub Script Delivered | QC in Progress |
| Successful delivery | Complete | QC Passed |
Redelivery Path: Request requires redelivery.
| Stage | Status | Current Step |
| Asset QC Failed | Dub Script Delivered | QC Failed |
| A new request replaces the old one | Ready | Assignment for QC Fixes |
| Author Assigned | Ready | Author for QC Fixes |
| Authoring in progress in the Authoring tool (for fixing QC issues) | In Progress | Author for QC Fixes |
| Authoring completed (for fixing QC issues) | Complete | Author for QC Fixes |
| Proofing request ready | Ready | Proofread for QC Fixes |
| Proofing in progress in authoring tool (for fixing QC issues) | In Progress | Proofread for QC Fixes |
| Proofing completed (for fixing QC issues) | Complete | Proofread for QC Fixes |
| Delivery completed | Delivered | Deliver for QC Fixes |
| As recorded Dubscript delivered to Backlot | Dub Script Delivered | QC in Progress |
| Asset QC passed | Complete | QC Passed |
Requests Management
There are several options to manage requests. Once a user selects the 3 dot menu next to a request, a drop-down appears with a list of options.
🗒️ NOTE: Options are subject to status.
Image 11 Single request menu
To manage bulk requests, select the checkboxes. A bar will appear at the bottom left of the page with all available options, subject to status.
Image 12 Bulk requests
The following section outlines all request options.
Edit Assignment
Users may assign, unassign, and reassign authors and proofreaders.
To do so, the users will type the names of the authors and proofers and select them from the dropdown. The dropdown lists users who were onboarded in Starship. Anyone with the dialogue list author role shows up in the main transcriber and anyone with the dialogue list proofreader role shows up in the Transcription proofer.
🗒️ NOTE: In order to save, users must assign an author and proofer.
Image 13 Assigning the author and proofer
Details
A window pane opens, revealing details of the request, including the current step, vendor, author and proofer, source request, and history.
Image 14 Details Panel
Open in
Users may open the requests in 2 tools:
- Open in Authoring: This redirects the user to a read-only view of the script in the Authoring tool.
- Open in Source Management: This redirects the user to the source request in Backlot.
Revert to Authoring
This moves a request back from the PROOFREAD step to the AUTHOR step. This usually happens when an author selects "Complete" too soon.
When to use it: A linguist accidentally clicked COMPLETE on the AUTHOR step
Support
The support dropdown has 2 options: Walkthroughs and Resources and What's New.
Image 15 Support
Learning resources are housed in the Support drop-down under “Walkthroughs and Resources” for the tool including online courses and documentation. A panel will open on the bottom right-hand side with these resources.
Image 16 Walkthroughs and Resources
In-app notifications with tool updates and feature rollouts will be displayed in “What’s New.” A red bubble next to the drop-down indicates a new feature or enhancement has been rolled out. Selecting “What’s New” opens a panel on the left-hand side with all tool notifications.
Image 17 What’s New panel
Help
For support with technical issues in the tool, select “Help” to submit a ticket. Please note, that our Netflix team supports multiple tools across the business.
Image 18 Help ticket example
Please include
- A summary of the issue, steps taken before the issue appeared, and a description of any troubleshooting steps already taken.
- Urgency context, i.e. deadlines. For example, is this delaying or blocking any workflows?
- Any relevant Data. For example, filtered URLs, MID, Request ID, Package ID, Task type, Target language, etc.