Timezone nitpicking, that's new ;)
As most of the policy changes around this were probably my fault anyway, let me recap to the best of my knowledge:
- If a web channel serves more than one distinct market (e.g., Netflix, Amazon) by having exclusive releases in different countries with different time zones, the web channel is set to global and airtimes cannot be set because they simply don't fit the existing data structure and any workarounds would create a huge mess
- If a web channel operates in a single market (that can very well be 'global'), it is assigned a home country and airtimes can be set according to that timezone
- BUT airtimes for these web channels should only be set if they are specifically announced (some of them have very reliable scheduling, though)
dpratt wrote:
Maybe if we kept track of the release times in the past then we'd know more what to expect in the future.
- Last but not least I see no problem with recording verified airtimes for past episodes - that's what I actually just did with Stargate Origins
One suggestion:
tnt wrote:
If the web channel announcing the exact time of the release (e.g. CBSAA and Star Trek: Discovery), the airtime should be entered according to the policy: If the show's network exists in multiple timezones, the earliest timezone should be used.
Almost. The airtime needs to be entered for the time zone that is set for the Network or Web Channel.
While you can probably define this earliest time zone for countries or networks, users can't actually see it in the UI, which can lead to confusion.
Would it be possible to add the time zone to the UI labels for the corresponding fields, like this? Would probably help avoid mistakes.
Default Airtime (America/New York)
Airtime (Canada/Atlantic)