Define content start and stop date and time fields.

Registered by JohnGrunder

This blueprint has been superseded. See the newer blueprint "Reusable Content-Streams with schedulable media items" for updated plans.

Suggestion: Xibo is a great tool, but the following enhancement would make it more friendly to maintain on an ongoing basis.

Each content item uploaded should contain a start and stop date field, along with a start time and stop time field, to allow pre-loading of content to be included with each layout/schedule. Otherwise content such as event flyers must be added and removed manually, to avoid "outdated" content from remaining on the displays. Including start and stop date and time fields onto the content database record would greatly enhance the maintainability of Xibo displays at institutions that have limited employees to keep track of constantly changing content, such as event flyers.

1. Add start and stop date and time fields to each content record, so that content items such as event flyers, etc. could be preloaded prior to an event, and then automatically unloaded after the event is finished (display client would simply ignore content that did not meet the date reqirents, so content could be downloaded to client, then included or excluded even if not connected to the server. If the stop date is reached, the client could simply delete the content item (the content item also would not be redownloaded if the stop date were reached, but the item would download even if the start date was not yet reached---see Active field below).

(Events as in company picknic or upcoming seminar, etc).

2. Add and Active checkbox field for each content record, so that content items could be kept in a region, but "turned off and on" if need be. This would be effective if the start and stop dates were not filled in (content begins imeadiately and has no stop date) but you wanted to upload and keep an emergency or annual anouncement (Happy Holidays, Don't Forget to Do Your Taxes, etc.). This might control whether or not the content item is downloaded to the display client each time.

Start and stop dates are different from durations, which define the amount of time that the content stays active before the next content in a region takes over.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
Proposed for 1.1
Implementation:
Unknown
Milestone target:
None
Completed by
Alex Harrington

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.