198 lines
10 KiB
HTML
198 lines
10 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<title>OTS Signs Command Center Documentation</title>
|
||
<meta name="viewport" content="width=device-width">
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
||
|
||
<!-- favicon -->
|
||
<link href="../img/favicon.ico" rel="shortcut icon"/>
|
||
|
||
<!-- Bootstrap -->
|
||
<link href="../vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet" media="screen">
|
||
|
||
<!-- Stylesheets -->
|
||
<link href="../manual.css" rel="stylesheet" media="screen">
|
||
|
||
<!-- META -->
|
||
<meta name="keywords" content="digital signage, signage, narrow-casting, ots-signs, open source, agpl, documentation" />
|
||
<meta name="description" content="OTS Signs Command Center is an open source digital signage solution. It supports all main media types and can be interfaced to other sources of data using CSV, Databases or RSS." />
|
||
</head>
|
||
<body data-toc="scheduling">
|
||
<!-- Copyright 2020 Xibo Signage Ltd. Part of the Xibo Open Source Digital Signage Solution. Released under the AGPLv3 or later. -->
|
||
<nav id="top-nav" class="navbar navbar-inverse navbar-fixed-top" role="navigation">
|
||
<div class="container">
|
||
<div class="navbar-header">
|
||
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#ss-navbar">
|
||
<span class="sr-only">Toggle navigation</span>
|
||
<span class="icon-bar"></span>
|
||
<span class="icon-bar"></span>
|
||
<span class="icon-bar"></span>
|
||
</button>
|
||
<a href="#" class="navbar-brand">OTS Signs Command Center Documentation</a>
|
||
</div>
|
||
|
||
<div class="collapse navbar-collapse" id="ss-navbar">
|
||
<ul class="nav navbar-nav">
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</nav>
|
||
|
||
<div class="ss_body container">
|
||
<div class="row">
|
||
<div class="col-md-3">
|
||
<ul id="side-nav" class="nav nav-pills nav-stacked">
|
||
<li><a href="index.html" data-toc-name="getting_started">Getting Started</a></li><li><a href="layouts_editor.html" data-toc-name="layouts">Layouts</a></li><li><a href="media_library.html" data-toc-name="media">Media</a></li><li><a href="media_modules.html" data-toc-name="widgets">Modules</a></li><li><a href="scheduling_events.html" data-toc-name="scheduling">Scheduling</a></li><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
|
||
<html><body><ul>
|
||
<li>
|
||
<p><a href="simple_scheduling.html">Simple Scheduling</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_repeats.html">Using Repeats</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_priority_display_order.html">Ordering and Priority</a></p>
|
||
</li>
|
||
<li>
|
||
<p class="active"><a href="scheduling_events.html">Scheduling</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_layout_list.html">Layout List Campaign</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_ad_campaigns.html">Ad Campaigns</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_overlays.html">Schedule Overlays</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_geolocation.html">Geo Scheduling</a></p>
|
||
</li>
|
||
<li>
|
||
<p><a href="scheduling_dayparting.html">Dayparting</a></p>
|
||
</li>
|
||
</ul>
|
||
</body></html>
|
||
<li><a href="displays.html" data-toc-name="displays">Displays</a></li><li><a href="users_administration.html" data-toc-name="users">Users</a></li><li><a href="configure_cms_settings.html" data-toc-name="configure">Configuration and Organisation</a></li><li><a href="troubleshooting.html" data-toc-name="troubleshooting">Troubleshooting</a></li>
|
||
</ul>
|
||
</div>
|
||
<div class="col-md-9" role="main">
|
||
<h1 id="scheduling">Scheduling <a href="#scheduling" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
|
||
<p>Schedules are created from the <strong>Schedule</strong> page of the main CMS menu and include the following Event Types:</p>
|
||
<h3>Command</h3>
|
||
<p>Select a <a href="displays_command_functionality.html">Command</a> to be executed by the Player at a specific point in time.</p>
|
||
<blockquote class="tip"><p>Command Events do not require a <code>toDt</code>.</p>
|
||
<p>Display Order and Priority are irrelevant when it comes to executing Commands, but may be set in the CMS for organisational purposes.</p>
|
||
</blockquote>
|
||
<h3>Overlay Layout</h3>
|
||
<p>Layouts that have been designed as an <a href="scheduling_overlays.html">Overlay Layout</a> will be scheduled at the same time as existing Layouts to create an overlay of content when displayed.</p>
|
||
<h3>Interrupt Layout</h3>
|
||
<p>An Interrupt Layout will schedule a selected Layout to play <strong>in-between</strong> other Layouts in the ‘usual schedule’.</p>
|
||
<p>OTS Signs Command Center will work out when it will be played using how many <strong>seconds per hour</strong> or as a <strong>Percentage</strong> entered on the schedule.</p>
|
||
<blockquote class="tip"><p>This can be useful if you have Announcements that need to be shown for a particular amount of time within the usual schedule!</p>
|
||
</blockquote>
|
||
<ul>
|
||
<li>Select <strong>Interrupt Layout</strong> as the Event Type from the drop down menu when adding an Event.</li>
|
||
<li>Complete the form fields to create the schedule.</li>
|
||
</ul>
|
||
<h4>Share of Voice</h4>
|
||
<p>Enter the amount of time the Layout should be shown in seconds per hour or as a percentage (0 - 100%) of the events duration (the difference between the from date and the to date) that the <strong>Interrupt Layout</strong> should occupy the usual schedule.</p>
|
||
<blockquote class="tip"><p><strong>Please note:</strong> If your ‘main’ Layout has a long duration, the Interrupt Layout may show in a block in order to satisfy the SoV criteria entered!</p>
|
||
</blockquote>
|
||
<h3>Action</h3>
|
||
<p><strong>Scheduled Actions</strong> listen for a Trigger Code coming in on a webhook to Navigate to a Layout or to run a Command.</p>
|
||
<ul>
|
||
<li>
|
||
<strong>Navigate to Layout</strong> - enter the code identifier for the Layout the Player should navigate to when triggered. This code is created when adding a new Layout or from editing an existing from the Layouts grid.</li>
|
||
<li>
|
||
<strong>Command</strong> - select the Command to run.</li>
|
||
</ul>
|
||
<h2 id="synchronised_events">Synchronised Events <a href="#synchronised_events" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
|
||
<blockquote class="tip"><p>Synchronised Events are used in conjunction with <a href="displays_sync_groups.html">Sync Groups</a> to show mirrored or a video wall configuration across 2 or more Displays.</p>
|
||
<p>Ensure you have created and configured a <strong>Sync Group</strong> prior to scheduling!</p>
|
||
</blockquote>
|
||
<p>Click on the <strong>Add Synchronised Event</strong> button at the top of the schedule grid to open the <strong>Add Synchronised Event</strong> form.</p>
|
||
<p>Select a <a href="displays_sync_groups.html">Sync Group</a> from the drop down menu.</p>
|
||
<ul>
|
||
<li>Use the <strong>Layout</strong> drop down to select which content should be shown on each Display within the group.</li>
|
||
</ul>
|
||
<blockquote class="tip"><p>When selecting different content to show in a wall configuration on Displays, the total duration will be enforced by the content on the Lead Display.</p>
|
||
<p>The Lead Display will issue instructions to change the sequence based on its assigned content. Please bear in mind that other Displays within the group could fall out of sync if their content is not similar in design (same number of items, durations etc).</p>
|
||
</blockquote>
|
||
<ul>
|
||
<li>Select <strong>Mirror</strong> to automatically set the same item on each Display within the group automatically.</li>
|
||
</ul>
|
||
<blockquote class="tip"><p>Sync <a href="media_playlists.html">Playlists</a> on different Layouts by using a <strong>Content Synchronisation Key</strong>!</p>
|
||
</blockquote>
|
||
<h3>Dayparts</h3>
|
||
<ul>
|
||
<li>Events are scheduled using <strong>Dayparting</strong> information:
|
||
<ul>
|
||
<li>Select <strong>Custom</strong> to enter your own start and end times. Use the <strong>Relative time</strong> checkbox to input the Hours and Minutes when creating a Scheduled Event (not available for Synchronised Events).</li>
|
||
<li>Select <strong>Always</strong> to have the content always scheduled on the selected Display.</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
<blockquote class="tip"><p>Create your own defined <a href="scheduling_dayparting.html">Dayparts</a> to select for even easier scheduling!</p>
|
||
</blockquote>
|
||
<ul>
|
||
<li>Use the drop down to select what needs to be scheduled from the list.</li>
|
||
</ul>
|
||
|
||
</div>
|
||
</div>
|
||
</div> <!-- container-->
|
||
<footer class="ss_footer" role="contentinfo">
|
||
<div class="container">
|
||
<div class="pull-right">
|
||
<img class="img-responsive logo" src="../img/logo.png" alt="OTS Signs Command Center" />
|
||
</div>
|
||
|
||
<p class="ss_back_to_top">Back to Top</p>
|
||
|
||
<p class="ss_footer_links">Currently v4</p>
|
||
|
||
<p class="ss_languages"><a href="../en/index.html">en</a></p>
|
||
</div>
|
||
</footer>
|
||
|
||
<!-- JavaScript -->
|
||
<script src="../vendor/jquery/jquery.min.js"></script>
|
||
<script src="../vendor/bootstrap/js/bootstrap.min.js"></script>
|
||
<script type="text/javascript">
|
||
$(document).ready(function() {
|
||
$(".ss-sidebar .list-group li").addClass("list-group-item");
|
||
$(".ss_body img").addClass("img-thumbnail");
|
||
$(".ss_body table").addClass("table");
|
||
|
||
// Set the selected page based on the TOC name
|
||
// Mark the appropriate top nav element as the selected page
|
||
$("#top-nav a").each(function() {
|
||
if ($(this).data().tocName == $("body").data().toc)
|
||
$(this).parent().addClass("active");
|
||
});
|
||
|
||
$(".ss_back_to_top").click(function() {
|
||
$('html, body').animate({scrollTop : 0},800);
|
||
});
|
||
|
||
if (inIframe()) {
|
||
console.log("In Frame");
|
||
$("#top-nav").css("display", "none");
|
||
$(".ss-sidebar").parent().css("display", "none");
|
||
}
|
||
});
|
||
|
||
function inIframe () {
|
||
try {
|
||
return window.self !== window.top;
|
||
} catch (e) {
|
||
return true;
|
||
}
|
||
}
|
||
</script>
|
||
</body>
|
||
</html>
|