Asset pipeline

A video asset is a title or episode on its way to subscribers. The Content Operator records it with a number, a name, the owner responsible, the organization it belongs to and the subscription plan it will be offered under. From there the asset moves through Uploaded, Processing, Reviewed and Published, and later Retired when it is withdrawn.

Processing is where most problems surface. The operator starts processing for one specific revision of the asset. The real outcome from your transcoding service is recorded on the asset, along with when processing started and when it finished, the duration in minutes and any playback errors seen in testing. A run with numbered steps keeps the detail of what happened. Every status change is written to the asset’s history with the revision, the person and the reason.

• Upload and own. Each asset has one owner from the start. The owner answers for its files, evidence and processing.
• Process one revision. Processing is started for the current revision. If the files change, the revision changes, and the new revision is processed and reviewed on its own.
• Publish after review. Only a revision approved by an independent reviewer is published. Retiring an asset keeps its history and playback records.

Agree how asset numbers are formed, for example series code plus episode. Agree which subscription plan each content type belongs to. Agree the transcode outcomes your service reports, such as complete, partial or failed, and use the same words every time. Decide who owns assets by default, and who takes over when an owner leaves. Agree which evidence must be attached before processing starts, such as rights clearance and caption files.

A documentary episode is uploaded as revision 1 and owned by a content operator in the Europe organization. She starts processing. The transcoding service reports the 4K rendition failed while the HD renditions completed. The outcome is recorded on the asset, the run shows the failed step, and the asset does not reach review with a missing rendition.

The editor sends a corrected master. The asset moves to revision 2 and is processed again. This time every rendition completes, the run succeeds and the revision goes to the reviewer. Once the reviewer approves revision 2, the operator publishes it. The history shows both revisions, the failed attempt and who published the final one.

• Asset Pipeline Board — Assets grouped by Uploaded, Processing, Reviewed and Published, with owner, revision and transcode outcome on each card.
• My Assets — The signed-in operator’s own assets with processing dates and status.
• Published Assets — Live titles with duration, watched minutes, playback errors and plan.

• Upload to publication: Take an asset from upload through processing and review to publication.
• Correction and supersession: Correct a processed revision without losing its history.

Review the data model before importing your catalog.