Expire content based on two levels. - global/local
Requirement:
-------
A way to schedule content itself and not just the layouts.
User story:
-------
I have a layout playing on displays. I don't want to change the layout.
I want to run content from "date", to "date". The way to to that now is to either have the content in a different layout and schedule it or to manually do additions and removals in the layout region.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Solution:
-------
-------
We can have a two more levels of content scheduling.
Global Content Expire: When you define a media item you set a global expire (applicable for the library items).
For example: I want to display a poster for an event. I dont want that poster to be available after the event's date. So I set an expire on the content itself. Even if I use this content in different layouts, after the content expire date, it will not be shown in any of the layouts it was added to.
Local Content Expire: When you add the item to a layout region, you can set the expire on it (Applicable for any media item).
For Example: I want the media in a particular layout region to expire on a particular date before the actual event (i.e. global content expire date).
-------
-------
