5 - BCID autogenerated in CDMF

Owned by Kemal Atayev
Last updated: Nov 19, 2019

Check 5 shows how often are content ID’s from the Census autogenerated within the CDMF file.


If metadata for a given Content ID which is recorded in different viewing files or other metadata files is not submitted via XML, it will be autogenerated. There are 4 different sources of autogenerated records:

  • Non-linear assets (BCIDS) were not present in CDMF.
    • This means that Content ID is submitted as non-linear asset but was not submitted via XML.
    • Metadata in CDMF will be default, including duration of 3600 seconds.
    • These records will have no valid title, so it is not possible to determine which programme they are referring to
  • TX logs Content IDs (BCIDS) were not present in CDMF.
    • Content IDs populated in TX logs but not submitted via XML
    • Metadata in CDMF will contain only Title and duration based on TX log
  • Census Content IDs (BCIDS) were not present in CDMF.
    • Viewing for given BCID is recorded in Census from Player tags
    • Metadata in CDMF will be default with duration set to mode of tag durations
    • These records will have no title, so it is not possible to determine which programme they are referring to
  • VMRG Content IDs (BCIDS) were not present in CDMF. VMRG is a software module which processes online streaming data from Virtual meter (panel).
    • Viewing is recorded in Panel, but metadata is not submitted via XML
    • Metadata in CDMF will be default, including duration of 3600 seconds
    • These records will have no valid title, so it is not possible to determine which programme they are referring to.


Recommendations and consequences of non-compliance


Recommendations

To minimize percentage of autogenerated content it is important to submit metadata via XML, preferably before or on the day when content becomes available (OD or linear broadcast).


Consequences of non-compliance

Autogenerated content will have different implications on Dovetail reporting:

  • As broadcast – autogenerated OD content (or submitted OD content without correct Parent BCID) will NOT be reported in TechEdge/4-screen dashboard
  • As viewed – autogenerated OD content would be reported, but incorrectly:
    • Due to incorrect duration, the audiences will not be correct
    • In the case of third-party content – due to missing OOBGID/OOBCID information it could be reported under Player owner, instead of the actual content owner


If a Player owner does not submit records for third party content, we can have following situations:

  • For OD viewing in Census, record will be autogenerated based on Content ID (BCID) and Broadcaster group ID. We will not be able to determine if content is own or third party, so it will be treated as own due to missing OOGID and OOBCID information
    • These cases will be part of Census autogenerated records for Player owner
  • For live viewing that was matched to a third party TX log – it is not possible to autogenerate a record in CDMF where player owner’s group id is BGID and third party Content ID is OOBCID:
    • At the time of autogeneration, matching with linear programme schedule did not happen yet, so we couldn’t know if it is own content or third party
    • This viewing would not be calibrated in Dovetail


Note:

It is not possible to autogenerate records containing OOBCID and OOGID as this information is not available. These third party records for which there is no XML submission from player owner (with OOBCID and OOGID) will be part of Check 3 and these records can be identified with their content ID as ‘NOT AVAILABLE’.


Playtime in this report is driven by content viewed in Census where BCID’s are autogenerated.


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

Non-linear asset

Count/percentage of records (or playtime) autogenerated based on non-linear asset

Census Report

Count/percentage of records (or playtime) autogenerated based on Census report

TX logs

Count/percentage of records (or playtime) autogenerated based on TX logs

VMRG

Count/percentage of records (or playtime) autogenerated based on VMRG

Submitted via XML

Count/percentage of records (or playtime) which were not autogenerated

Total

Total count


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

Red Colour

  • Non-linear asset – percentage by record count
  • Census Report – percentage by record count
  • TX log – percentage by record count
  • VMRG – percentage by record count
  • Non-linear asset – viewed playtime
  • Census Report – viewed playtime
  • TX log – viewed playtime
  • VMRG – viewed playtime
  • Non-linear asset – calibrated playtime
  • Census Report – calibrated playtime
  • TX log – calibrated playtime
  • VMRG – calibrated playtime

Green Colour

  • Submitted via XML – percentage by record count
  • Submitted via XML – viewed playtime
  • Submitted via XML – calibrated playtime


Red columns require attention, the goal is to minimize auto generated content in CDMF.


Detail report will only contain records that were autogenerated. Records submitted via XML will not be included in detail report.


Data in detail report will be sorted based on Autogenerated source in following order:

  1. Census report
  2. TX log
  3. Non-linear asset
  4. VMRG