We use cookies (just for analytics) on this website. If you continue we will assume you are happy with it. ok

BeBanjo

Back to release notes

Runtime and duration in milliseconds in Reporter

Release date: March 10th, 2017 (Revision 1), print this page

We’ve improved several tables in Reporter to make it easier to produce aggregated reports. This note describes this change in full, and as usual you can contact support or your Technical Account Manager for further clarification.

In Movida a version (aka asset), rendition, and segment all have a runtime in the format HH:MM:SS.SSS, and metadata keys can have a type of duration in the format HH:MM:SS.

To save you from having to perform tricksy conversions when trying to aggregate these runtimes or durations their values are now also stored in milliseconds (as integers).

The new columns for each table are:

  • versions
    • version_runtime_in_ms
  • renditions
    • rendition_runtime_in_ms
  • segments
    • segment_runtime_in_ms
  • *_metadata
    • #{duration_field_name}_in_ms

About the metadata thing, imagine you have a titles metadata key named Estimated Duration that has a type of duration. That would be contained in the titles_metadata table in a column named estimated_duration. Now you’d also find a column named estimated_duration_in_ms with a value populated by Reporter.

References

  • reporter#94 Durations in ms