Files
OTSSignsTheme/manual/en/scheduling_priority_display_order.html
Matt Batchelder bbe8c1860c pre-img swap
2026-03-23 21:09:27 -04:00

172 lines
9.9 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 class="active"><a href="scheduling_priority_display_order.html">Ordering and Priority</a></p>
</li>
<li>
<p><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="using_priority_and_display_order">Using Priority and Display Order <a href="#using_priority_and_display_order" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>OTS Signs Command Center has a number of scheduling tools to allow for the simple creation of schedules across one or more Displays/Display groups. These tools allow users to define the order of scheduled items to tailor how content should be shown as well as flagging high-priority Events to display those at the top of schedule lists.</p>
<h2 id="priority">Priority <a href="#priority" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Priority pushes important content to the front of any existing schedules and overrides all other non priority events of the same Event Type (Layouts/Campaigns/Video/Images and Playlists) on the schedule.</p>
<p>Schedules with a higher priority take precedence over those with lower priorities, with 0 considered the lowest.</p>
<p>For example, you might have an important announcement with information about a fire alarm test which needs to be the only thing to show on Displays at a specific time. Assigning the highest Priority to this Event would ensure that it is the only content to be shown.</p>
<p>On reaching the end time of the priority event, the normal schedule will resume on displays.</p>
<h2 id="display_order">Display Order <a href="#display_order" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Use Display Order to determine the play order of multiple Events which have been scheduled to show at the same time.</p>
<p>Ordering is a simple numerical sort, lowest to highest numbers, Events marked with a 1 will be played before any Events marked with a 2 for example.</p>
<p>Leaving the Display Order field blank will default to the order that the Event was first added.</p>
<blockquote class="tip"><p><strong>NOTE:</strong> To ensure Layouts play in a defined order we recommend adding and ordering them into a Layout List Campaign. The Display Order can then be used to determine the order in which entire Campaigns should play.</p>
<p>If Layout List Campaigns have the same Display Order set or this field is left blank, Layouts assigned to the Layout List Campaign will play according to the <strong>Play List order</strong> set.</p>
</blockquote>
<h3>Maximum Plays per Hour</h3>
<p>There is an additional setting when scheduling Events to limit the number of times the Event should be shown per hour on Displays. You may have a promotional Image which should only be shown once an hour for example.</p>
<ul>
<li>Set a number here or leave as 0 for unlimited plays.</li>
</ul>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="scheduling_layout_list_campaign.html">Setting a Play List order for a Campaign</a></p>
<p><a href="getting_started_showing_a_playlist.html">Showing a sequence of content in a Playlist</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>What is considered the same Event Type for Priority?</strong></em></p>
<p>Layouts/Campaigns/Images/Videos and Playlists will be treated as the same Event Type when taking Priorities into consideration.</p>
<p><em><strong>What would happen if I ticked the Run at CMS time checkbox for an event?</strong></em></p>
<p>With this ticked, the Event time would be determined by the CMS time rather than using the local Display time for the selected Displays.</p>
<p>Scenario:</p>
<ul>
<li>CMS Time = GMT</li>
<li>Display 1 = GMT</li>
<li>Display 2 = GMT -4</li>
</ul>
<p>If an event was scheduled to start at 11:00hrs, content would start to show on these Displays at 11:00hrs according to their time zones. These two Displays will not show the same content at the same time as Display 2 is 4 hours behind Display 1.</p>
<p>If Run at CMS time was ticked, Display 1 will start to show at 11:00hrs, as it is on the same time zone as the CMS. Display 2 will start to show content at 07:00hrs as it is 4 hours behind the CMS time zone.</p>
</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>