We use cookies (just for analytics) on this website. If you continue we will assume you are happy with it. ok

BeBanjo

Back to index

The data model explained

The data available in your BigQuery dataset is structured as a 4NF relational model. There’s one table per entity of Movida / Metadata and Sequence. Each table contains one row per instance of the entity present in the system, and the fields of each row contain the attributes of each of those entities.

Usually, tables and fields are named the same way as they appear in Movida’s and Sequence’s UI (e.g., titles, series, title_name, brand_external_id…). Exceptions to this general rule are described in the sections below.

Finally, additional fields in each table are used to reference related instances of other entities by their IDs (e.g., brand_id, series_id, title_id…)

In the PDF file linked below, you’ll find an E/R diagram showing all the tables (i.e., entities) available in your Reporter’s dataset and their relationships. The following sections of this document describe each table in detail.

Reporter E/R Diagram

Assets

The assets table contains one row per asset existing in your Sequence account. An asset (a.k.a. material) is a digital or physical material (e.g., a tape or a digital file) that is required to complete a job in Sequence.

  • jobs: Every asset is part of a job. The assets.job_id field references the job each asset belongs to.

Audio tracks

The audio_tracks table contains one row per audio track in your Movida’s catalog. An audio track represents one of the potentially multiple streams of sound available in a rendition.

  • renditions: Every audio track is part of a rendition. The audio_tracks.rendition_id field references the rendition each audio track belongs to.

Brand credits

The brand_credits table contains one row per credit of a brand in your Movida’s catalog. A credit represents the participation of a contributor in the production of a piece of content, in this case, a brand.

  • contributors: Every brand credit refers to a contributor that participated in the brand. The brand_credits.contributor_id field references the contributor each credit refers to.
  • brands: Every brand credit refers to a brand where the contributor participated. The brand_credits.brand_id field references the brand each credit refers to.

Brands

The brands table contains one row per brand in your Movida’s catalog. A brand represents a show or TV program, and it’s composed of an ordered set of series (seasons).

  • licensors: A brand can have a licensor associated with it. The brands.licensor_id field references the licensor of each brand (if any).
  • brand_credits: A brand can have multiple credits. The brand_credits.brand_id field references the brand each credit refers to.
  • brands_metadata: A brand can have custom metadata values. The brands_metadata.brand_id field references the brand each set of metadata values applies to.
  • brands_metadata_multiple: A brand can have custom “multiple” metadata values. The brands_metadata_multiple.brand_id field references the brand that each metadata value applies to.
  • series: A brand can have multiple series. The series.brand_id field references the brand each series belongs to.

Brands metadata

The brands_metadata table contains one row per brand in your Movida’s catalog with the values for each of the custom brand metadata keys configured in your account except for multiple metadata keys; those can be found in the brands_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the brand metadata template of your account.

  • brands: The brands_metadata.brand_id field references the brand that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Brands metadata (multiple)

The brands_metadata_multiple table contains one row per value of each multiple metadata key of a brand. This table is the counterpart of brand_metadata: while that table stores metadata keys with single values in one single row per brand, this table stores metadata keys with multiple values in multiple rows per brand.

The brand_metadata_key field specifies the name of the metadata key, while the brand_metadata_value stores the value of that key.

  • brands: The brands_metadata_multiple.brand_id field references the brand that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the brand_metadata field).

Collection credits

The collection_credits table contains one row per credit of a collection in your Movida’s catalog. A credit represents the participation of a contributor in the production of a piece of content, in this case, a collection.

  • contributors: Every collection credit refers to a contributor that participated in the collection. The collection_credits.contributor_id field references the contributor each credit refers to.
  • collections: Every collection credit refers to a collection where the contributor participated. The collection_credits.collection_id field references the collection each credit refers to.

Collection entries

The collection_entries table contains one row per entry of a collection in your Movida’s catalog. A collection entry specifies the position of a title in a collection.

  • collections: Every collection entry is part of a collection. The collection_entries.collection_id field references the collection each entry belongs to.
  • titles: Every collection entry refers to a title that is part of the collection. The collection_entries.title_id field references the title of the entry.

Collections

The collections table contains one row per collection present in your Movida’s catalog. A collection is a user-defined selection of titles in a specific order. A collection can contain any title present in your catalog.

  • collection_entries: A collection can have multiple collection entries. The collection_entries.collection_id field references the collection each entry belongs to.
  • collection_credits: A collection can have multiple credits. The collection_credits.collection_id field references the collection each credit refers to.
  • collections_metadata: A collection can have custom metadata values. The collections_metadata.collection_id field references the collection each set of metadata values applies to.
  • collections_metadata_multiple: A collection can have custom “multiple” metadata values. The collections_metadata_multiple.collection_id field references the collection that each metadata value applies to.

Collections metadata

The collections_metadata table contains one row per collection in your Movida’s catalog with the values for each of the custom collection metadata keys configured in your account except for multiple metadata keys; those can be found in the collections_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the collection metadata template of your account.

  • collections: The collections_metadata.collection_id field references the collection that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Collections metadata (multiple)

The collections_metadata_multiple table contains one row per value of each multiple metadata key of a collection. This table is the counterpart of collection_metadata: while that table stores metadata keys with single values in one single row per collection, this table stores metadata keys with multiple values in multiple rows per collection.

The collection_metadata_key field specifies the name of the metadata key, while the collection_metadata_value stores the value of that key.

  • collections: The collections_metadata_multiple.collection_id field references the collection that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the collection_metadata field).

Contributors

The contributors table contains one row per contributor present in your Movida’s catalog. A contributor is a person that participated in the production of content in your catalog (brand, series, titles…)

  • brand_credits: A contributor can appear in the credits of multiple brands. The brand_credits.contributor_id field references the contributor each credit refers to.
  • contributors_metadata: A contributor can have custom metadata values. The contributors_metadata.contributor_id field references the contributor each set of metadata values applies to.
  • contributors_metadata_multiple: A contributor can have custom “multiple” metadata values. The contributors_metadata_multiple.contributor_id field references the contributor that each metadata value applies to.

Contributors metadata

The contributors_metadata table contains one row per contributor in your Movida’s catalog with the values for each of the custom contributor metadata keys configured in your account except for multiple metadata keys; those can be found in the contributors_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the contributor metadata template of your account.

  • contributors: The contributors_metadata.contributor_id field references the contributor that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Contributors metadata (multiple)

The contributors_metadata_multiple table contains one row per value of each multiple metadata key of a contributor. This table is the counterpart of contributor_metadata: while that table stores metadata keys with single values in one single row per contributor, this table stores metadata keys with multiple values in multiple rows per contributor.

The contributor_metadata_key field specifies the name of the metadata key, while the contributor_metadata_value stores the value of that key.

  • contributors: The contributors_metadata_multiple.contributor_id field references the contributor that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the contributor_metadata field).

Jobs

The jobs table contains one row per job present in your Sequence account. A job represents a workflow, a set of tasks to be done over a set of assets.

  • work_areas: Every job is part of a work area. The jobs.work_area_id field references the work area each job belongs to.
  • schedule_entries: A job can be created from Movida and get associated to one particular schedule entry. The jobs.schedule_entry_id field references the schedule entry related to each job (if any).
  • assets: A job can have multiple assets that are part of it. The assets.job_id field references the job each asset belongs to.
  • tasks: A job can have multiple tasks that are part of it. The tasks.job_id field references the job each asset belongs to.
  • notes: A job can have multiple notes attached to it. The notes.job_id field references the job each note is part of.
  • problems: A problem can have multiple problems reported in it. The problems.job_id field references the job each problem is part of.

Licensors

The licensors table contains one row per licensor present in your Movida account. A licensor is an entity (company, organization, department…) that licenses content in your Movida’s catalog (brands, series, titles…).

  • brands: A licensor can license multiple brands in your Movida’s catalog. The brands.licensor_id field references the licensor of each brand (if any).
  • titles: A licensor can license multiple titles in your Movida’s catalog. The titles.licensor_id field references the licensor of each title (if any).

Notes

The notes table contains one row per note attached to any job in your Sequence account. A note is a written message left by a user in a job.

  • jobs: A note will always be attached to a job. The notes.job_id field references the job each note is part of.

Platform requirements

The platform_requirements table contains one row per platform requirement configured in your Movida account. A platform requirement is a high-level attribute of a platform, such as the business model or the territory.

  • platforms: A requirement will always refer to a platform. The platform_requirements.platform_id field references the platform each requirement applies to.

Platforms

The platforms table contains one row per platform present in your Movida account. A platform is a named schedule, a target for scheduling and publishing actions in Movida. A platform usually is related to an external VOD platform (e.g., Youtube, iTunes) or downstream system to which Movida publish schedules and metadata to.

  • schedule_entries: A platform can be referenced from multiple schedule entries. The schedule_entries.platform_id field references the platform where the content is scheduled.

Problems

The problems table contains one row per problem reported in any job in your Sequence account. A problem is a written message describing an issue found while processing a job.

  • jobs: A problem will always be attached to a job. The problems.job_id field references the job each problem is part of.

Renditions

The renditions table contains one row per version rendition present in your Movida catalog. A rendition is a video representation of a version in a particular format, resolution, frame rate…

  • versions: A rendition is the representation of a particular version. The renditions.version_id field references the version each rendition is related to.
  • audio_tracks: A rendition can have multiple audio tracks that are part of it. The audio_tracks.rendition_id field references the rendition each audio track belongs to.
  • subtitles: A rendition can have multiple subtitles that are part of it. The subtitles.rendition_id field references the rendition each audio track belongs to.

Right windows

The right_windows table contains one row per right window existing in your Movida account. A right window is a period of time in which a title is allowed to be scheduled in a platform according to the recorded rights information in Movida.

  • titles: A right window always refers to a title. The right_windows.title_id field references the title each rights window applies to.
  • platforms: A right window always refers to a platform. The right_windows.platform_id field references the platform where the title is allowed by each right window.

Schedule entries

The schedule_entries table contains one row per entry existing in your Movida’s schedule. A schedule entry is a period of time in which a title is scheduled to be exhibited in a platform.

  • titles: A schedule entry always refers to a title. The schedule_entries.title_id field references the title each schedule entry applies to.
  • platforms: A schedule entry always refers to a platform. The schedule_entries.platform_id field references the platform where the content is scheduled.
  • versions: A schedule entry can optionally specify which one of the title’s versions is scheduled. The schedule_entries.version_id field references the scheduled version.
  • collections: A schedule entry can optionally a collection as part of which the title is scheduled. The schedule_entries.collection_id field references the collection of the scheduling.
  • schedule_entries_metadata: A schedule entry can have custom metadata values. The schedule_entries_metadata.schedule_entry_id field references the schedule entry each set of metadata values applies to.
  • schedule_entries_metadata_multiple: A schedule entry can have custom “multiple” metadata values. The schedule_entries_metadata_multiple.schedule_entry_id field references the schedule entry that each metadata value applies to.

Schedule entries metadata

The schedule_entries_metadata table contains one row per schedule entry in your Movida’s catalog with the values for each of the custom schedule entry metadata keys configured in your account except for multiple metadata keys; those can be found in the schedule_entries_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the schedule entry metadata template of your account.

  • schedule_entries: The schedule_entries_metadata.schedule entry_id field references the schedule entry that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Schedule entries metadata (multiple)

The schedule_entries_metadata_multiple table contains one row per value of each multiple metadata key of a schedule entry. This table is the counterpart of schedule_entry_metadata: while that table stores metadata keys with single values in one single row per schedule entry, this table stores metadata keys with multiple values in multiple rows per schedule entry.

The schedule_entry_metadata_key field specifies the name of the metadata key, while the schedule_entry_metadata_value stores the value of that key.

  • schedule_entries: The schedule_entries_metadata_multiple.schedule entry_id field references the schedule entry that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the schedule_entry_metadata field).

Segments

The segments table contains one row per segment of a version in your Movida’s catalog. A segment is one of the potentially multiple parts into which a version is divided.

  • versions: A segment is always part of a version. The segments.version_id field references the version each segment belongs to.

Series

The series table contains one row per series present in your Movida’s catalog. A series is a set of ordered episodes of a single season of a TV program or show.

  • brands: A series can be part of a brand. The series.brand_id field references the brand each series belongs to (if any).
  • series_credits: A series can have multiple credits. The series_credits.series_id field references the series each credit refers to.
  • series_metadata: A series can have custom metadata values. The series_metadata.series_id field references the series each set of metadata values applies to.
  • series_metadata_multiple: A series can have custom “multiple” metadata values. The series_metadata_multiple.series_id field references the series that each metadata value applies to.
  • titles: A series can have multiple episodes. The title.series_id field references the series each episode belongs to.

Series credits

The series_credits table contains one row per credit of a series in your Movida’s catalog. A credit represents the participation of a contributor in the production of a piece of content, in this case, a series.

  • contributors: Every series credit refers to a contributor that participated in the series. The series_credits.contributor_id field references the contributor each credit refers to.
  • series: Every series credit refers to a series where the contributor participated. The series_credits.series_id field references the series each credit refers to.

Series metadata

The series_metadata table contains one row per series in your Movida’s catalog with the values for each of the custom series metadata keys configured in your account except for multiple metadata keys; those can be found in the series_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the series metadata template of your account.

  • series: The series_metadata.series_id field references the series that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Series metadata (multiple)

The series_metadata_multiple table contains one row per value of each multiple metadata key of a series. This table is the counterpart of series_metadata: while that table stores metadata keys with single values in one single row per series, this table stores metadata keys with multiple values in multiple rows per series.

The series_metadata_key field specifies the name of the metadata key, while the series_metadata_value stores the value of that key.

  • series: The series_metadata_multiple.series_id field references the series that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the series_metadata field).

Subtitles

The subtitles table contains one row per subtitle in your Movida’s catalog. A subtitle represents one of the potentially multiple streams of captions transcribing the dialogue or narrative of a rendition in a particular language.

  • renditions: Every subtitle is part of a rendition. The subtitles.rendition_id field references the rendition each subtitle belongs to.

Tasks

The tasks table contains one row per task existing in your Sequence account. A task is a piece of work that needs to be completed as part of the job in Sequence.

  • jobs: Every task is part of a job. The assets.job_id field references the job each task belongs to.

Title credits

The title_credits table contains one row per credit of a title in your Movida’s catalog. A credit represents the participation of a contributor in the production of a piece of content, in this case, a title.

  • contributors: Every title credit refers to a contributor that participated in the title. The title_credits.contributor_id field references the contributor each credit refers to.
  • titles: Every title credit refers to a title where the contributor participated. The title_credits.title_id field references the title each credit refers to.

Titles

The titles table contains one row per title present in your Movida’s catalog. A title is an individual piece of content: a feature film, a series episode or any other audiovisual clip (open, promo, trailer, bumper…).

  • licensors: A title can have a licensor associated with it. The brands.licensor_id field references the licensor of each title (if any).
  • series: A title that is an episode is always part of a series. The title.series_id field references the series each episode belongs to.
  • title_credits: A title can have multiple credits. The title_credits.title_id field references the title each credit refers to.
  • titles_metadata: A title can have custom metadata values. The titles_metadata.title_id field references the title each set of metadata values applies to.
  • titles_metadata_multiple: A title can have custom “multiple” metadata values. The titles_metadata_multiple.title_id field references the title that each metadata value applies to.
  • rights_windows: A title can have multiple right windows. The right_windows.title_id field references the title that each rights window applies to.
  • schedule_entries: A title can have multiple schedule entries. The schedule_entries.title_id field references the title that each schedule entry applies to.
  • versions: A title can have multiple versions of it. The versions.title_id field references the title each version belongs to.

Titles metadata

The titles_metadata table contains one row per title in your Movida’s catalog with the values for each of the custom title metadata keys configured in your account except for multiple metadata keys; those can be found in the titles_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the title metadata template of your account.

  • titles: The titles_metadata.title_id field references the title that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Titles metadata (multiple)

The titles_metadata_multiple table contains one row per value of each multiple metadata key of a title. This table is the counterpart of title_metadata: while that table stores metadata keys with single values in one single row per title, this table stores metadata keys with multiple values in multiple rows per title.

The title_metadata_key field specifies the name of the metadata key, while the title_metadata_value stores the value of that key.

  • titles: The titles_metadata_multiple.title_id field references the title that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the title_metadata field).

Versions

The versions table contains one row per title version present in your Movida’s catalog. A version is a particular variation of a title (e.g., with or without strong language).

Please note that versions are called assets in Movida UI at the moment.

  • title: A version is always related to a title. The versions.title_id field references the title each version belongs to.
  • versions_metadata: A version can have custom metadata values. The versions_metadata.version_id field references the version each set of metadata values applies to.
  • versions_metadata_multiple: A version can have custom “multiple” metadata values. The versions_metadata_multiple.version_id field references the version that each metadata value applies to.
  • renditions: A version can be represented in multiple video renditions. The renditions.version_id field references the version each rendition is related to.
  • schedule_entries: A version can be part of multiple schedule entries. The schedule_entries.version_id field references the scheduled version.

Versions metadata

The versions_metadata table contains one row per version in your Movida’s catalog with the values for each of the custom version metadata keys configured in your account except for multiple metadata keys; those can be found in the versions_metadata_multiple table.

The schema of this table is dynamic as it contains one field per key configured in the version metadata template of your account.

  • versions: The versions_metadata.version_id field references the version that the metadata applies to. Note that there’s a 1:1 relationship with this table.

Versions metadata (multiple)

The versions_metadata_multiple table contains one row per value of each multiple metadata key of a version. This table is the counterpart of version_metadata: while that table stores metadata keys with single values in one single row per version, this table stores metadata keys with multiple values in multiple rows per version.

The version_metadata_key field specifies the name of the metadata key, while the version_metadata_value stores the value of that key.

  • versions: The versions_metadata_multiple.version_id field references the version that the metadata applies to. Note that there’s a 1:N relationship with this table (as opposed to the 1:1 relationship of the version_metadata field).

Work areas

The work_areas table contains one row per work area configured in your Sequence account. A work area is a separated space that allows creating and processing jobs in Sequence.

  • jobs: A work area can have multiple jobs as part of it. The jobs.work_area_id field references the work area each job belongs to.

Last updated September 19th, 2017.