Glossary
The glossary contains a list of Connect specific terms.
Batch
Definition
An object that is used to organize one or more Jobs in Connect. A batch allows for Jobs to be configured and delivered in bulk.
A Batch is assigned to a single Platform, but can contain Jobs that are using different Package Templates as long as they belong to the same Platform.
Example
A Batch called Hulu April 2022 is created using the Hulu Platform.
In this Batch, multiple Titles are added, which in turn creates multiple Jobs. The Jobs can now be configured from the 'Hulu April 2022' Batch. They can be run, cancelled, or delivered in bulk.
Related
job platform package template title
Bucket
Definition
As per the AWS documentation, a bucket is a container for objects stored in Amazon S3. An S3 Bucket will be linked with Connect at an Organization settings level.
Example
If the object named photos/puppy.jpg is stored in the DOC-EXAMPLE-BUCKET bucket in the US West (Oregon) Region, then it is addressable using the URL https://DOC-EXAMPLE-BUCKET.s3.us-west-2.amazonaws.com/photos/puppy.jpg.
Related
DeepAnalysis
Definition
Deep analysis is a feature that uses proprietary and 3rd party techniques and tools to scan and analyze video files in order to detect and identify differences and similarities between them. This can include changes in the visual content of the video, such as changes in the colors, shapes, or movements of objects.
The goal of the deep analysis feature is to provide a detailed and accurate understanding of the differences between video files. This can be used to deduplicate content and reduce storage footprint.
Deliverable
Definition
A Media item that has been generated through a Job workflow, inside a Package, regardless if it resulted from a copy or a transcode process or if it was generated from Connect directly.
In certain workflows, Sources or Deliverables will be deliberately ignored or chosen, depending on the situation.
Example
A Job with the Gone With The Wind title is created, generating the Gone_With_The_Wind_4k.mp4 deliverable from the Gone With The Wind source.
The source is tagged with the Video tag, and after transcoding is finished, the deliverable is tagged with the same one.
When a Metadata Template is generated in this Job and the file is referenced by the Video tag, the deliverable will be chosen by default.
Related
Job
Definition
A job is an object that handles the delivery of a Title to a Platform in Connect. A job always has a Title and a Package Template assigned to it.
Jobs run using the Package Template to create the Package deliverables and will run a delivery to the endpoint that is configured on the Platform.
Example
A Job with the Gone With The Wind title is created, using the Hulu non-episodic Package Template, which is configured to deliver to the Hulu platform.
The job generates the following deliverables:
- a metadata .xml
- a ProRes video file
- 3 audio tracks for mono, stereo and 5:1
- a
en-uscaption.
The deliverables are then delivered to Hulu based on the configuration of the Hulu Platform.
Related
package platform template title
Ingest
Definition
The process that a Media item goes through in order to be fully indexed in the Connect system.
The Ingest steps can differ based on an Organization’s configuration, but a Media item will be successfully ingested only if it is accessible on S3.
Another by-product of the Ingest process is the generation of the Probe results.
Example
An S3 event is fired and picked up by Connect, that the GoneWithTheWind.mp4 video file has been added to the S3 bucket.
This will trigger an Ingest process, which will go through the following steps:
- Ensure that the file is accessible by Connect from S3.
- Probe the media item.
- If the option is turned on in the Organization settings:
- generate a preview cache
- extract captions from the video file
- extract audio tracks from the video file
- generate thumbnails.
Related
MediaWarp
Definition
The Ateliere Connect proprietary transcoding solution used in manual or automatic processes.
Example
The Extract captions and Extract audio tracks functionalities in Connect that work on Ingest are using MediaWarp for the extraction process.
Related
Media Item
Definition
A Media Item is a file that has been registered in the Connect database, the most common case being that the file is added to S3 and the S3 event is ingested by Connect.
The Media Item will follow an ingest process, which can or can not be successful.
A Media item will have technical metadata (Ingest → Probe process) and descriptive metadata (as part of the Metadata schema) assigned to it.
Example
A media item called GoneWithTheWind.mp4 reaches S3, is successfully ingested and manually assigned metadata values as per a metadata schema.
The resulting media item will contain:
- A JSON with the Probe results as technical metadata
- Several metadata fields, as per the configured schema (Original file name - String, DRM - Boolean).
Related
Metadata Field
Definition
A metadata field is a key-value pairing that can be configured by an organization admin at a definition level.
Once defined, Titles, Media Items and Virtual Assets can use the metadata fields to store different types of values, such as strings, dates, arrays, tags, media items, etc.
Example
The Episode Title entity type has four metadata fields set up:
Name- stringDescription- stringCast & Crew- string arrayRelease Date- date
Related
metadata schema title media item virtual asset
Metadata Hierarchy
Definition
The parent-child relations that can be created between multiple Title entity types. A parent entity type can have multiple child entity types assigned to it. A child entity can have a single parent entity assigned.
A metadata hierarchy is useful especially with the Template syntax available in Connect.
Example
The most common hierarchy is: Show → Season → Episode hierarchy.
Additionally, we can create multiple smaller hierarchies using the same entity types as parents Show → Show Trailer or Season → Season Trailer or Episode → Episode Trailer.
Related
template title metadata schema
Metadata Schema
Definition
The metadata schema is a collection of organization-defined Title, Media Item and Virtual Asset entity types. It includes the configuration of:
- metadata hierarchy
- metadata fields
The schema is propagated to individual instances of a Title, Media Item or Virtual Asset when creating one of the same entity type.
Example
The Ateliere Connect organization has a metadata schema that includes:
- 4 Title entity types:
Movie,Show,SeasonandEpisode. Each entity type has multiple metadata fields configured. For example:Episodecan haveName,Description,Cast & Crew,Release Date. - A hierarchy:
Show→Season→Episode.
When a user creates a new Episode, they can fill in the metadata fields listed above, and they can assign another Title of the Season entity type as its parent.
Related
metadata hierarchy metadata field title media item virtual asset
Organization
Definition
An organization is the top-most layer of the Connect platform. This is where all other Connect entities are stored and configured. For example, Titles, Media items, Jobs, Batches.
Example
The Ateliere Demo organization has a content library and a set of platforms with settings that are stored to showcase the capabilities of Connect.
Related
Package
Definition
A package is a collection of deliverable Media items that has been generated through a Job. If generated through this process, a Package will always be assigned to a Title.
Example
Delivering the Gone With The Wind Title to Hulu will generate a Package, based on the naming convention defined in the organization settings. For example, Gone With the Wind | April 2023 Hulu PCG 1.
The Package can be accessed from the Title level, with more information about how the Package was generated and what it contains.
Related
Platform
Definition
A platform is a collection of settings associated with a certain delivery endpoint (cable, streaming service, etc.).
Generally, a Platform contains:
- several settings related to the delivery endpoint
- one or more associated
Package Templates.
Example
A Hulu Platform is created to service deliveries to Hulu. To achieve this, the Platform will be configured with:
- the delivery details: if the delivery is done through a feed or if it’s done through copying the deliverables, the location of where the files will be delivered, for copy deliveries, and the credentials to perform the copy action, for copy deliveries.
- several Package Templates, for: episodic content, non-episodic content, trailers and marketing materials.
Related
Probe
Definition
The process where technical metadata is extracted from a Media item on Ingest, either by using ffprobe or mediainfo.
After the process is finished, the technical metadata is stored in the Connect database and associated with the media item.
Example
GoneWithTheWind.mp4 goes through the Ingest process.
After Connect makes sure it has access to the file on S3, the media item is probed with one of the services (ffprobe or mediainfo). If the first service is not successful, the other one can be used.
Information around resolution, tracks, color spaces etc. is then extracted as a JSON file and added to the Connect database.
Related
Profile
Definition
Settings or configurations that affect Connect services or 3rd party integrations that alter a media item to a certain extent.
Profiles are available for the following items:
- Bug
- Timed Text
- Workbench TT
- MediaWarp
- QC
- Transcoder
Example
Connect is integrated with Hybrik, allowing the transcoding of media items.
In order to enhance transcoding capabilities, Connect stores Hybrik transcoding Profiles that are JSON files enhanced with technical and descriptive metadata from Connect. As such, when transcoding a media item through a Hybrik Transcoding Profile, information from the media item itself can be used to dynamically alter the way in which Hybrik will process the file.
Related
Provider
Definition
A set of individual settings that can be configured for a 3rd party integration, such as an integration with a transcoding or watermarking service.
Example
A Hybrik transcoding Provider will be created and configured so Connect can process files using the 3rd party service.
The information encompasses connection details, API keys, output location etc.
Source
Definition
A source is a media item that has been registered in Connect and is found in a location in S3 that is designated for Source-type files, as specified on the Organization settings.
Example
The GoneWithTheWind.mp4 file that comes in S3 and goes through the Ingest process will be added in Connect as a Source Media item.
Related
Suborganization
Definition
A suborganization is an Organization that has a parent Organization assigned to it.
There is no other effect to this, other than a visual one. Users will not inherit access to the Suborganization from the Organization.
Example
An Ateliere Connect FR suborganization is created and assigned as a child of the Ateliere Connect organization in order to do product demos for FR based clients.
Related
Tag
Definition
A tag is an organization-defined value which can be used to identify media when attached to a certain media item or track.
A media item can have multiple tags assigned to it.
Example
GoneWithTheWind.mp4 media item hast two tracks: a video track and an audio track.
An organization administrator will create two tags: a Video and Audio.
The main media item will be tagged with Video, while the audio track will be tagged with Audio.
Related
Template
Definition
A template is a data model configuration which, when used in a Job workflow, can take information from Connect (media items, metadata, etc.) and output it in a specific format.
The most important templates in Connect are Package and Metadata Templates.
Example
A Package Template can be configured in Connect in order to service deliveries to the Hulu Platform.
Hulu will have a set of requirements in terms of what files need to be delivered, their format, and the XML data format.
As such, the Package Template will contain:
- a Copy (the file will be copied as is) deliverable for the captions
- a Transcode (the file will be transcoded beforehand) deliverable for the video file
- a Metadata XML deliverable, generated using a Metadata Template.
Related
Title
Definition
A title is a way of organizing multiple media items and metadata in a single entity, for it to be processed through multiple workflows in Connect.
Titles can be defined based on a metadata schema.
Example
An organization operator has created the Gone With The Wind title. They can attach multiple media items to it: a video file and multiple timed text files.
They also have to fill in multiple metadata fields, as defined in the metadata schema:
- Cast & Crew
- Release Year
- Description
Related
media item metadata schema metadata field
Virtual Asset
Definition
A virtual asset is a placeholder for a Media item that does not exist in Connect yet. It can have metadata assigned to it for further identification and it can also be assigned a Media item at a later time, if/when it reaches Connect.
Example
On the Gone With The Wind title, there is a master film that is stored in a physical location at this time.
For library management purposes, a Virtual asset is created in Connect that references the master film which is created.
Metadata is assigned to it in order to identify where it can be located:
Storage location- Dream Bld., HollywoodRack- 55Column- 1Row- 3
If the video is then digitalized and ingested in Connect, the resulting Media item can be assigned to the Virtual asset.
Related
Virtual Folder
Definition
A folder that is purely used for content organization inside a Title. It is called 'virtual' because S3 does not support a folder style structure. As such, it is something that only exists from a visual perspective.
A Virtual folder can have other Virtual folders or Media items assigned to it.
Example
Under the Gone With The Wind title, there will be two folders: one containing the theatrical release and another containing the director’s cut. Under each folder, media items that belong to each version can be moved.