-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep items in script long term #84
Comments
i think the issue here is that different items have different "expiry" dates and that SOME of them are known in advance. For example weather reports with things like flash flood warnings actually do have a (known at the time of issue) expiry date. Other things, like "bridge is out" need to stay in the broadcast until the bridge is fixed - which is unknown, but certainly longer than 3 days. What makes it really frustrating to program is that, for some areas, we simply haven't found any "new" news, so that items "5 days old" are the "newest" thing we have. So perhaps something like this generate script with items 3 days old or newer, unless the ONLY items are older than 3 days, then include all items within a week of the last reported item. |
From @MeghanUX: If you ALLOW future dates, then the broadcasters can keep setting dates in the future - for items they want to "stick around". I think that's brilliant! |
I think we do allow future |
@ArtOfCode- status completed? |
Yup. |
Broadcast would like a feature where items can stay in the script regardless of date settings. I think we should use
originated_at = NULL
and just always put those in the script.The text was updated successfully, but these errors were encountered: