Overview of concepts involved

As a quick introduction to the many new concepts involved, we’ll take a look at two screenshots.

We start from a screenshot of a Delivery Workspace:

In the screenshot above, we see the Delivery Workspace called "Through the Glass Darkly" with subtitle "Season 2", it is a Production, with type equal to "DELIVERY".

In the left sidebar, under the title 'Collections', we see the editorial structure of the workspace. In this case, it contains a single Editorial Object of type Notebook called "Through the Glass Darkly" representing the season. This in turn contains several Editorial Object of type Draft representing the different episodes.

In the main area, we see a listing of 64 DeliveryRequests. Some of them are linked to one of the episodes, others are linked to the season Editorial Object.

Many of these DeliveryRequests look very similar. For example, the topmost 6 start with "Audio Promo". That is because they request the same thing, but for a different episode. These DeliveryRequests share a common DeliveryRequestTemplate. Usually, the entire Delivery Workspace follows a predefined template which indicates which DeliveryRequests should be created for the various Editorial Object. Learn more about Delivery Request Templating.

Opening (clicking) a Delivery Request will open a dialog looking like this:

In the title of the dialog, we see it represents the single DeliveryRequest requesting the "Video / Broadcast" for Episode 1.

In the right Versions sidebar, we see two versions. In the API, a version is called a DeliveryRequestSubmission. The first has been rejected. The second one is open.

In the main area, we see that the DeliveryRequest has been configured to request both file(s), plus some additional information (Spoken Languages, Duration, Timecodes).

The main area shows the active DeliveryRequestSubmission and the data that has been provided on it. It currently contains a single file (DeliveryRequestSubmissionAttachedAnnotation). It’s form fields have been filled in.