Cisco Cisco StadiumVision Mobile Streamer
© 2011 Cisco Systems, Inc. All rights reserved.
24 of 26
Proof of Play Enhancements
The proof of play CSV report file names have been changed. The previous "generic" report is
renamed "detailed" report. The previous "kore" report is renamed "summary" report. The
downloadable CSV reports have names in the format of xxxx_detailed_report.csv and
xxxx_summary_report.csv.
renamed "detailed" report. The previous "kore" report is renamed "summary" report. The
downloadable CSV reports have names in the format of xxxx_detailed_report.csv and
xxxx_summary_report.csv.
Raw Proof of Play Data
The raw proof of play data gathered from DMPs is no longer stored in the database; it is stored in the
/var/sv/pofp/raw directory. The processed data is still stored in the /var/sv/pofp/data directory. You
should generate a proof of play report within six weeks after the event.
/var/sv/pofp/raw directory. The processed data is still stored in the /var/sv/pofp/data directory. You
should generate a proof of play report within six weeks after the event.
Since proof of play data is saved to a file rather than the database, the Dashboard Proof of Play
Database service monitor reports the database as not available. This is normal behavior.
Database service monitor reports the database as not available. This is normal behavior.
Proof of Play Default Settings
In Release 2.3, the default setting for proof of play is set to ‘NO’ rather than ‘YES’ as in previous
versions. It is critical for the operator to confirm that proof of play is set to ‘YES’ for events that
require proof of play.
versions. It is critical for the operator to confirm that proof of play is set to ‘YES’ for events that
require proof of play.
Important! There is no way to recover proof of play data if the script is started with proof
of play set to ‘NO’.
of play set to ‘NO’.
Proof of Play Behavior for Support for Replacing Content
If you replace content while an event script is running, the Summary CSV report will reflect the
replaced content along with any associated content tags rather than the original content. For
example, if you replace a content file named ad1.jpg that has a content tag Ford with a content file
named ad2.jpg that has a content tag Honda, the Summary CSV will show ad2.jpg in place of
ad1.jpg, and the content tag column will show Honda in place of Ford.
replaced content along with any associated content tags rather than the original content. For
example, if you replace a content file named ad1.jpg that has a content tag Ford with a content file
named ad2.jpg that has a content tag Honda, the Summary CSV will show ad2.jpg in place of
ad1.jpg, and the content tag column will show Honda in place of Ford.
See the
Proof of Play Support for Video Playlists
In Release 2.3, proof of play supports video playlists. The name of the video playlist item will be
shown on the proof of play report which can be different from the actual file name if the content was
named differently.
shown on the proof of play report which can be different from the actual file name if the content was
named differently.
Known Issues
•
Proof of play data may be cut off early when the event script ends.
•
In Release 2.3, the script ends with an instruction to the DMP to reload the flash template. Any
proof of play data still in the DMP flash template buffer will not be collected. As a workaround,
create an event state that does not require proof of play at the end of the event script.
proof of play data still in the DMP flash template buffer will not be collected. As a workaround,
create an event state that does not require proof of play at the end of the event script.