Relationships & Hierarchies

Origin Studio models relationships between Records.

Use relationships to build hierarchies and packaging structures.

Parent / child hierarchies

The main hierarchies are:

• Series → Season → Episode

• Series → Season → Episode → EpisodeEdit

• Movie → MovieEdit

A Season can only belong to one Series. An Episode can only belong to one Season. An EpisodeEdit can only belong to one Episode. A MovieEdit can only belong to one Movie.

Origin Studio's hierarchy model is aligned to common EIDR patterns.

When you import from Origin Nexus, Origin Studio can pull required parents to prevent orphaned Records.

See Record Management.

Edits

MovieEdits and EpisodeEdits are child Records that represent specific versions or variations of their parent Movie or Episode.

• MovieEdit: represents a specific cut or version of a Movie (e.g. Director's Cut, Extended, Restored).

• EpisodeEdit: represents a specific cut or version of an Episode (e.g. Censored, Alternate Ending, Regionalized).

Edit Records inherit metadata from their parent and support the same permissions, workflows, and field configurations as other Work Types.

Edits cannot be moved or reassigned to different parents and cannot contain their own child Records.

Compilations

Compilations are containers.

They can include:

• Movies

• Series

• Seasons

• Episodes

• Other Compilations

Use Compilations for box sets, franchises, or content families.

See Compilations management.

Metadata inheritance

Some metadata can be copied from parent to child Records.

This is rule-based and user-initiated. Admins control which fields can participate.

See Inheritance.