Skip to content

support use case: 1 EditorialObject with 1 or more MediaResource(s) #497

@wivaku

Description

@wivaku

Scenario A (available in EBUCorePlus): an EditorialObject that is related to another EditorialObject (e.g. regular movie and the director's cut), each EditorialObject has a MediaResource with Essences. It makes sense to have different EditorialObjects as the metadata is different, e.g. different description, year of production.

Scenario B (currently not available): for our project we also have the use case where 1 EditorialObject can have multiple MediaResources (=group of Essences), and each MediaResource has multiple Essences (e.g. a master file and transcoded versions).

Example:

  • 1 EditorialObject: e.g. "episode 4", a single object (with 1 house ID)
  • multiple MediaResources: e.g. one with and one without a station ident (different durations)

When Programme123 is published on a lineair channel the MediaResource with ident is used, when the same EditorialObject is published online the MediaResource without the ident is used.

The alternative is not preferred: 1 EditorialObject (with 1 MediaResource) which has relationship with other EditorialObject (with 1 MediaResource).

The consequences:

  • MediaResource should get duration property
  • all duration / timecode related properties and relations should (also) be available for MediaResources. This includes: Subtitles, Captions, Actions, parental guidance, etc.
  • for a Segment/Scene: no change is needed, as this can point directly to a specific MediaResource/Essence

It is an editorial decision to determine which use case is more applicable for the two use cases. E.g. for PG-13 vs R-rated version decide if scenario A or B is preferred. The schema can allow both and leave it to the user.

  • e.g. explicitly separate them on EditorialObject level: Programme123 (R-rated) is scheduled in the evening and Programme456 (PG-13) is scheduled for the rerun in the morning
  • e.g. implicitly separate them, when Programme123 is scheduled in the evening the R-rated MediaResource can be used, if it is scheduled in the morning the PG-13 version is to be used

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions