How to locate and download Change Logs in OM

When working on revisions to subtitling or scripting configurations (for example from a P1 version to P2 or later passes in Theatrical projects, or from a Lock to Final version in episodics), it is important for reasons of internal consistency to know how to assess whether other configurations for the same version of the proxy have already been completed, and how to find and download a Change Log for completed configurations, so that the same changes can be implemented during work on the user's current configuration, when applicable.

Diligence in this process will help ensure that our files do not contain discrepant content when delivered to downstream teams or to the client.

The order in which our configurations are completed is in constant flux and often variable on a client-by-client and even project-by-project basis, so users will first of all need to be familiar with assessing whether other configurations for the same pass have already been completed before the one they are working on.

This can be achieved by using the Reports view in OM and checking the 'Workflow State' of the jobs for the same version of the proxy.

In the example below, by searching for a specific title and language and scrolling through the various configurations, we can assess that the Spotting Lists for the Final DCP version of the three Reels at the top of the list have been already been completed, as the Workflow State reads as 'Job Complete'.

If we are working on a different configuration for those same reels, during the same pass, we need to ensure that our changes are consistent with those made in the already completed files.

This is achieved by consulting Change Logs.

IMPORTANT! The process to download Change Logs for scripting configurations and subtitling configurations is slightly different, due to a different change tracking logic between the two types of configurations in OM. Please follow the correct process for your specific case by referring to the correct workflow between the two outlined below.

How to find and download Change Logs for completed SCRIPTING configurations (Dialogue Lists and Spotting Lists)

Once we have identified the already completed scripting configurations that are relevant to our pass in the Reports view results (in the example below, a series of Dialogue List reels completed for the Final-V2 pass), we will need to access the Language Asset History by clicking on the link next to the specific job for which we intend to locate a Change Log.

This will open a full Asset History of all task deliveries for the job in question, including date of delivery, name of the editor who completed the task and further details.

The good news when working with scripting Change Logs is that these are cumulative at each pass, so we will only need to pull one from the system for each pass - the one from the latest relevant version of the file.

This will be the most recent one on the list that contains the name of our current version under "Asset Version" (in the example below, "Final- V2") and lists "Production QC Linear (Content QC)" under 'Type.'

Once we have identified the most recent relevant completed version of the task, we need to access it in Ce6 by clicking on the eye symbol on the far left of the asset version. This will open a "view only" version of the task.

From within the view only task, we will need to navigate to 'Report' -> 'Edits/QC Codes' -> 'Full Report'

This will open a window containing all changes made in the configuration during this pass. We will click on "Download Report" and this will download the Change Log to our computer.

How to find and download Change Logs for completed SUBTITLING configurations

When it comes to downloading Change Logs for subtitling configurations, the main difference from the process described above for scripting configurations is that the Change Logs are not cumulative. This poses an additional challenge for us when searching for the correct Change Logs to pull and consult, as it means that the tracked changes "reset" whenever the job is rerun for an update, and for this reason changes made in previous asset versions are not visible in later change logs.

Here is how we must proceed currently to ensure we have visibility on all relevant changes.

Once we have identified the already completed subtitling configurations that are relevant to our pass in the Reports view results (in the example below, a series of template FULL reels completed for the Final-V2 DCP pass), we will need to access the Language Asset History by clicking on the link next to the job for which we intend to locate Change Logs.

This will open a full Asset History of all task deliveries for the job in question, including date of delivery, name of the editor who completed the task and further details.

We will now need to pull the Change Logs for EACH version delivered through a CQC step for the latest pass. In our example, these will be the ones that contain the correct name of our current version under "Asset Version" (in the example in question, "Final- V2 DCP") and list "Production QC Linear (Content QC)" under 'Type.' In our example, these will be the two highlighted in green in the image below.

We can entirely ignore the versions with much older names and dates in the version type (in the example, the ones underlined in red, which are much older and still called PChina).

IMPORTANT! For subtitling version ups, and especially so on Theatrical projects, the turnaround between two versions can be very tight, meaning that often a new version of certain configurations is prepared in rapid succession from the previous one, and before any further configurations are made. When looking to find Change Logs that are relevant to our current configuration, we should also check in the asset history the dates when versions were made.

For example, in our example from above, if we look at the dates, we can see that only 3 days elapsed between the delivery of the "Final V2" and the "Final V2 DCP" versions of the file.

This makes it highly unlikely that the changes from Final V2 will have had time to make it to any later configurations, so for safety we should also add that version to the list of Change Logs we will be pulling and consulting.

Now that we know which versions we are interested in, we will need to access each of these in turn, by clicking on the eye symbol on the far left of the asset version. This will open a "view only" version of the task.

From within the view only task, we will need to navigate to 'Report' -> 'Edits/QC Codes' -> 'Full Report'

This will open a window containing all changes made in the configuration during this pass. We will click on "Download Report" and this will download the report to our computer.

We will now need to repeat the process for each of the asset versions we identified as relevant to our work in the Asset History, by clicking on the eye symbol next to each one and going through the workflow outlined above to download each Change Log.

Consulting the Change Logs

The Change Logs we download will be Excel documents with the words "qc_report" at the start of the filename.

When we open the file, the relevant report will be in the second tab of the Excel sheet, under "QC Report."

All changes from the asset version in question will be highlighted within the report in green and red, as seen below.

We must also make sure to scroll all the way to the right in the report, as the columns further to the right include changes made to speaker IDs, positioning and annotations - all of which we would want to keep consistent across configurations.

Now we have all the relevant Change Logs, we can implement all applicable changes in our current configuration.