Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Parent BCID field in CDMF should be used to link different versions of own content*. This check is focused on count of records in CDMF file having valid Parent BCIDs for the content IDs reported in Webdb2 i.e. ONE file.


It is possible that some content does not have multiple versions and Parent BCID is not required. It is not possible to know this in advance for a piece of content. Number of populated Parent BCID is relative to a Broadcaster and same percentage of blank Parent BCIDs does necessarily mean same for every Broadcaster.


To minimize the false reporting of blank Parent BCID’s, we are assuming that linear content does not require one (as linear BCID should be the Parent to other versions), hence Parent BCID will be looked at ONLY if: BCID is not matched to TX log, i.e. it is not linear BCID, AND (OOGID is blank OR OOGID=BGID), i.e. it is not third party content:

  • Blank Parent BCID - How many BCIDs which are not matched to TX log have a blank Parent BCID –
    • please note that having low or a high percentage of blank Parent BCID’s should be taken with reserve. We can only assume that BCID that is not matched to TX log is non-linear version, however it can still happen that some of those BCID’s are linear, but they were not yet broadcast, or Content ID was not populated in TX logs for them
  • Parent BCID matched only in CDMF - How many parent BCIDs have matching entry in CDMF, but not in TX log.
  • Parent BCID matched only in TX log - How many parent BCIDs have matching entry in TX log but not in CDMF.
  • Parent BCID matched both in CDMF and TX log – How many parent BCIDs are matched to both CDMF and TX log.
  • Not matched to anything – Parent BCIDs which are provided via XML but do not have master record in CDMF, and are not matched to TX log


Recommendations and consequences of non-compliance


Recommendations

If same piece of content has multiple versions – multiple BCIDs in CDMF – it is recommended to use linear version BCID as a Parent BCID in XML submission. This will ensure that all on demand viewing can be linked to linear transmission and reported in Dovetail ‘as broadcast’ mode. This should be coupled with timely TX log submission with Content ID’s populated.


Consequences of non-compliance

A correctly populated parent ID ensures that a programme has all its viewing attributed to it from all the various versions of it that exist. Otherwise the playtimes that are technically for one programme are broken up among multiple content IDs.


Playtime in this check is driven by viewed Content IDs from Census – for Broadcasters own content that was not identified as linear.


Output Columns


Column name

Description

Player

Player name

Content owner

Player owner or 3rd Party broadcaster name

Activity**

Live or On Demand – **only applicable for playtime version

Blank Parent BCID

Count/percentage of records (or playtime) where Parent BCID is blank

Parent BCID matched only to CDMF

Count/percentage of records (or playtime) where Parent BCID is only matched to CDMF

Parent BCID matched only to TX log

Count/percentage of records (or playtime) where Parent BCID is only matched to TX log

Parent BCID matched to both CDMF and TX log

Count/percentage of records (or playtime) where Parent BCID is present as master record in CDMF and matched to TX log

Not matched to anything

Count/percentage of records (or playtime) where Parent BCID is provided but it is not present as standalone record in CDMF or matched to TX log

Total

Total count

In summary reports, columns will be colour coded as follows:

Red Colour

  • Blank Parent BCID– percentage by record count
  • Not matched to anything – percentage by record count
  • Blank Parent BCID – viewed playtime
  • Not matched to anything – viewed playtime
  • Blank Parent BCID – calibrated playtime
  • Not matched to anything – calibrated playtime

Amber Colour

  • Parent BCID matched only to CDMF – percentage by record count
  • Parent BCID matched only to TX log – percentage by record count
  • Parent BCID matched only to CDMF – viewed playtime
  • Parent BCID matched only to TX log – viewed playtime
  • Parent BCID matched only to CDMF – calibrated playtime
  • Parent BCID matched only to TX log – calibrated playtime

Green Colour

  • Parent BCID matched to both CDMF and TX log – percentage by record count
  • Parent BCID matched to both CDMF and TX log – viewed playtime
  • Parent BCID matched to both CDMF and TX log – calibrated playtime

Red columns require attention; however, each Broadcaster should estimate which percentage of blank Parent BCIDs is expected.


Amber columns for this check also require attention, as this indicates that Parent BCID should be present, but metadata related to it is incomplete.


Detail report only contains records where Parent BCID is blank, not matched to anything, matched only to CDMF or only to TX logs. Records where OOBCID is matched to both CDMF and TX log will not be present in detail report.


Data in detail report will be sorted based on Parent BCID status in following order:

  1. Blank Parent BCID
  2. Parent BCID matched only to CDMF
  3. Parent BCID matched only to TX log




* Examples of different versions:

  • Different edits.
  • If OD BCID is different from the linear BCID (from TX logs).
  • Sign language and audio description versions.
  • No labels