Split Brodcast data model to content-based Episode and time-based Broadcast
The current Broadcast model mingles content-based episode as well as time-based broadcast aspects. Split in in two models provides
- better separation (eliminating null-value bloated rerun instances)
- preparing content-based episodes without having yet assigned a broadcast
- sending a broadcasts via multiple publication channels
-
rename Broadcast to Episode model -
create ContentChannel model (following BFR-API) -
create new Broadcast model (m:n through model between ContentChannel and Epside) -
data migration, create Broadcast instances from Episodes, delete rerun Episodes -
move firstrun property from Episode to Broadcast -
clean Episode instances: remove time-based fields that are now in Broadcast -
update queries with respect to new Episode/Broadcast separation