OTSSigns/OTSSignsTheme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pre-img swap

Browse Source
This commit is contained in:
Matt Batchelder
2026-03-23 21:09:27 -04:00
parent 87474b05a9
commit bbe8c1860c
395 changed files with 29643 additions and 712 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
manual/en/check_fr.py Normal file
View File

@@ -0,0 +1,28 @@
import os
import re
os.chdir('/Users/matt/dev/OTSSignsTheme/manual/en')
files = [
'layouts_editor.html', 'layouts_editor_design_changes.html',
'layouts_editor_editing_tools.html', 'layouts_editor_global_elements.html',
'layouts_editor_library_search.html', 'layouts_editor_using_templates.html',
'layouts_interactive_actions.html', 'scheduling_repeats.html',
'scheduling_layout_list.html', 'scheduling_priority_display_order.html',
'users_administration.html', 'users_groups.html',
'configure_folders.html', 'configure_tags.html',
'getting_started_showing_a_playlist.html', 'getting_started_showing_a_playlist_v4.html',
'getting_started_showing_a_video.html', 'getting_started_showing_a_video_v4.html',
'getting_started_showing_an_image.html', 'getting_started_showing_an_image_v4.html',
]
for fn in files:
with open(fn) as f:
content = f.read()
idx = content.find('further_reading')
if idx == -1:
continue
fr_block = content[idx:idx+600]
print(f'=== {fn} ===')
print(fr_block[:400])
print()

274
manual/en/configure_cms_settings.html Normal file
View File

@@ -0,0 +1,274 @@
<!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="configure">
<!-- 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><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><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html><body><ul>
<li>
<p class="active"><a href="configure_cms_settings.html">Configure CMS Settings</a></p>
</li>
<li>
<p><a href="configure_tags.html">Tags</a></p>
</li>
<li>
<p><a href="configure_folders.html">Folders</a></p>
</li>
<li>
<p><a href="configure_transitions.html">Transitions</a></p>
</li>
</ul>
</body></html>
<li><a href="troubleshooting.html" data-toc-name="troubleshooting">Troubleshooting</a></li>
</ul>
</div>
<div class="col-md-9" role="main">
<h1 id="cms_administrator_settings">CMS Administrator Settings <a href="#cms_administrator_settings" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Like any complex application, the OTS Signs Command Center CMS comes with a number of configurable options. These are located from the <strong>Settings</strong> page under the <strong>Administration</strong> section of the main CMS menu.</p>
<p>Settings are split into related category tabs:</p>
<p><img src="img/v4_tour_cms_settings_admin.png" alt="CMS Settings" /></p>
<h2 id="configuration">Configuration <a href="#configuration" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>From this tab view the <strong>CMS Secret Key</strong> which is used to authenticate Players with the CMS and apply a <strong>Theme</strong> to pages (if applicable) as well as setting the default positioning for the <a href="tour_cms_navigation.html">Navigation Menu</a>.</p>
<h2 id="defaults">Defaults <a href="#defaults" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Use this tab to apply defaults to all <a href="media_library.html">Media</a> files and set default <a href="configure_transitions.html">Transitions</a>.</p>
<p>You can also set Layouts to <strong>automatically Publish</strong> 30 minutes after the last recorded edit by enabling the checkbox for this setting.</p>
<h3>Resizing Images</h3>
<p>Default thresholds and limits can be specified which are then considered in the event an image should be resized. This could be when uploading an image or an image being downloaded by a Widget - NASA RSS in a Ticker Widget for example.</p>
<ul>
<li>
<h4>Resize Threshold</h4>
</li>
</ul>
<p>Set a maximum threshold (based on the longest side) that should be considered for resizing an image.</p>
<blockquote class="tip"><p>If you set a Resize Threshold of 1920 and you upload/download an image which is 800, this image would not need resizing. If you uploaded/downloaded an image which was 2400, this would then be resized to 1920.</p>
</blockquote>
<ul>
<li>
<h4>Resize Limit</h4>
</li>
</ul>
<p>Set a limit (based on the longest side) for uploaded/downloaded images. Images that exceed this limit will not be processed and should be replaced with another image that is within the limit.</p>
<p>This setting will determine whether the image file is too large to be processed.</p>
<ul>
<li>
<h4>DataSet maximum number of Rows</h4>
</li>
</ul>
<p>Set the maximum permitted number of rows a User can create in a DataSet.</p>
<h2 id="<strong>displays</strong>"><strong>Displays</strong> <a href="#<strong>displays</strong>" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Set defaults for <strong>Latitude</strong> and <strong>Longitude</strong> for all Geo aware previews throughout the CMS.</p>
<h3>Default Layout</h3>
<p>The Default Layout set here will be automatically assigned to all Displays to be shown when no other content is scheduled or if there is an issue which prevents a scheduled Event from being shown.</p>
<p>This global Default Layout can be overridden for individual Displays by selecting an alternative <a href="displays.html#content-default-layout">Default Layout</a> to be used.</p>
<h3>Proof of Play Default Settings</h3>
<p>Set the <strong>Aggregation level</strong> of collection of <a href="displays_metrics.html">Proof of Play</a> statistics to be applied to all <strong>Layouts</strong> / <strong>Media</strong> and <strong>Widget items</strong> as default.</p>
<ul>
<li>
<strong>Individual</strong> - statistics are recorded at the start and finish of each item individually and sent back to the CMS at each collection interval.</li>
<li>
<strong>Hourly</strong> - records each item once, and includes the total number of times played and the length of time played during the hour and is sent back to the CMS on the next collection interval after the hour period has expired.</li>
<li>
<strong>Daily</strong> - records each item once, and includes the total number of times played and the length of time played during the day and is sent back to the CMS on the next collection interval after the day has expired.</li>
</ul>
<blockquote class="tip"><p>Players aggregate ‘completed records’ only, with collection made at the end of the Widgets duration so if a Widget has a duration of 3 hours, the stat will be recorded once the Widget has expired!</p>
</blockquote>
<ul>
<li>Use this box to <strong>enable the collection</strong> of Proof of Play statistics to all <strong>Displays</strong> as default.</li>
</ul>
<blockquote class="tip"><p>This can be toggled on/off by editing <a href="displays_settings.html#content-editing-profiles">Display Setting Profiles</a>.</p>
</blockquote>
<ul>
<li>Tick the box to set the default to on for the collection of Proof of Play statistics for all newly added <strong>Layouts</strong>.</li>
</ul>
<blockquote class="tip"><p>Collection can be disabled by unticking the box on the <strong>Add/Edit</strong> Layout form.</p>
</blockquote>
<p>Use the settings to enable the collection of Proof of Play statistics to apply to all <strong>Media</strong>, <strong>Playlist</strong> and <strong>Widgets</strong> (Off/On/Inherit).</p>
<blockquote class="tip"><p>It is intended to have <strong>Widget</strong> always set to Inherit so that Layout and Media options control the collection!</p>
</blockquote>
<h2 id="general">General <a href="#general" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>View/set the address for the <strong>User Manual</strong> and tick to send <strong>anonymous statistics</strong> to help improve the software.</p>
<h3>Tidy Library (Global)</h3>
<p>The Library can be <em>tidied</em> by a Super Administrator or User so that it is kept clean and small.
<strong>Actions cannot be reversed so this must be used with caution.</strong></p>
<blockquote class="tip"><p>This might be of particular interest if the CMS is installed on a web server that has quotas or if Users have been assigned their own quotas.</p>
</blockquote>
<p>Administrators can initiate a system-wide Library tidy operation by clicking the <strong>Tidy Library</strong> button in the right hand corner of the Settings page:</p>
<p><img src="img/v4_tour_cms_settings_tidy_library.png" alt="Settings Tidy Library" /></p>
<p>As this functionality is system-wide and therefore operates on <strong>ALL</strong> User files, confirmation is required to remove unused and old revisions.</p>
<p>This option is more comprehensive and removes:</p>
<ul>
<li>Temporary files</li>
<li>Orphaned files</li>
<li>Thumbnails</li>
<li>Media revisions that aren’t used anywhere</li>
<li>Media that isn’t used anywhere (on any Layouts / Display Groups / Displays)</li>
<li>Generic files uploaded to the CMS</li>
</ul>
<h4>Orphaned files</h4>
<p>Orphaned files are a rare occurrence where a file stored on disk in the Library folder is not deleted when the Media item is deleted from the Library. This means that the file exists but the CMS doesn’t know anything about it.</p>
<h3>Tidy from User Library</h3>
<p>Allow a User to tidy files from the <a href="media_library.html#content-tidy-library">Library</a> page by using the checkbox to <strong>Enable Library Tidy</strong>.</p>
<h2 id="maintenance">Maintenance <a href="#maintenance" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>From here <strong>Enable Maintenance</strong> and <strong>Email Alerts</strong> to be sent and set the maximum retention ages for <strong>Logs</strong> and <strong>Statistics</strong>.</p>
<h2 id="network">Network <a href="#network" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>From the Network tab complete an <strong>Admin email address</strong> for the overall CMS administrator. All email notifications generated by the CMS will be sent to this address.</p>
<p>Ensure that the <strong>Sending email address</strong> and <strong>name</strong> is completed prior to setting up any further email notifications throughout the CMS.</p>
<h2 id="sharing">Sharing <a href="#sharing" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Use the dropdown to change how Widget colour appears in Playlists for Users.</p>
<ul>
<li>
<strong>Media Colouring</strong> will use the colours from the <strong>theme</strong> for each Widget.</li>
<li>
<strong>Sharing Colouring</strong> will show the Widget colour based on <strong>User access</strong> from <strong>Sharing</strong> options. (Green = editable)</li>
</ul>
<p>From here you can set if Users should have the ability to schedule to Displays when Share options are set to View for the User as well as being able to set whether Users should be able to see the names of Layouts in schedules that have not been shared with them.</p>
<p>Tick to allow Users to save their content into the top level <a href="configure_folders.html">Root Folder</a> or disable to force Users to select a Folder to save to.</p>
<h2 id="regional">Regional <a href="#regional" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>From this tab set the <strong>Language</strong> and default <strong>Timezone</strong> and <strong>Date Format</strong> to use across the CMS.</p>
<blockquote class="tip"><p>Select the nearest major city in your timezone!</p>
</blockquote>
<p>Use the checkbox to detect the <strong>browser language</strong> to use for the CMS and select which type of <strong>Calendar</strong> should be used.</p>
<h2 id="troubleshooting">Troubleshooting <a href="#troubleshooting" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>This tab is used to to set Log Levels which are useful for capturing php errors and environment issues.</p>
<h2 id="users">Users <a href="#users" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Select the System User and set the Default User Group and User Type when onboarding new Users.</p>
<blockquote class="tip"><p>We recommend that the <strong>Default User Type</strong> is set to <strong>User</strong>!</p>
</blockquote>
<h3>Password Policy</h3>
<p>Enter any valid regular expression in the <strong>Password Policy Regular Expression</strong> field so all password change requests and newly created passwords are tested against this.</p>
<blockquote class="tip"><p>A text description will be shown to Users when their passwords do not meet the required policy as a prompt!</p>
</blockquote>
<h3>Password Reminder</h3>
<p>Enable to provide a <strong>Forgotten your Password</strong> reset link for <strong>Users</strong> at login so they can easily regain access to the CMS.</p>
<blockquote class="tip"><p>Ensure that a valid <strong>Sending email address</strong> has been entered on the <strong>Network</strong> tab before enabling this functionality!</p>
</blockquote>
<p>The User will be shown a link which once clicked will send a <strong>Password Reset Notification</strong> to their email address as recorded on their User Profile.</p>
<blockquote class="tip"><p><strong>Users</strong> can also change their own passwords, once logged into the CMS, from their <strong>User Profile</strong>.</p>
</blockquote>
<h2 id="two_factor_authentication">Two Factor Authentication <a href="#two_factor_authentication" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="index.html">Two Factor Authentication</a> can be set by a User for added security once logged in.</p>
<p>Once configured, a User would need to enter the code sent via email or as displayed in the Google Authenticator app to complete login to gain access to the CMS.</p>
<blockquote class="tip"><p>Ensure that an Email address has been provided by the user to receive the generated email!</p>
</blockquote>
<p>Set a valid <strong>Sending email address</strong> has been entered on the <strong>Network</strong> tab and a name has been entered in the <strong>Two Factor Issuer</strong> field to make it clear on the Google Authenticator app and email when authenticated codes are generated for login to the CMS.</p>
<p>Reset Two Factor Authentication for Users from their User Profile.</p>
<h2 id="applications">Applications <a href="#applications" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>OTS Signs Command Center contains an API that allows 3rd party applications to connect and consume its data.</p>
<p>Applications are added and configured from <strong>Applications</strong> under the <strong>Administration</strong> section of the main CMS menu.</p>
<blockquote class="tip"><p>Before using an Application, each User must authorise the application to act on their behalf within the CMS.
Users can view authorised Applications from the My Applications section of their <strong>User Profile</strong>.</p>
</blockquote>
<p>At the current time the CMS does not provide individual Users with a method of revoking access to an application. Only an Administrator can remove an application completely.</p>
<h2 id="fonts">Fonts <a href="#fonts" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>OTS Signs Command Center comes with a set of standard fonts which can be set on many Widgets:</p>
<ul>
<li>Aileron Heavy Regular (Aileron-Heavy.otf)</li>
<li>Aileron Regular (Aileron-Regular.otf)</li>
<li>Dancing Script Regular (DancingScript-Regular.ttf)</li>
<li>Railway Regular (Railway.ttf)</li>
<li>Linear Regular (linear-by-braydon-fuller.otf)</li>
</ul>
<p>Manage from the <strong>Fonts</strong> page under the <strong>Administration</strong> section of the main CMS menu.</p>
<ul>
<li>Use the row menu to view a Fonts <strong>Details</strong> and see an example of the font style:</li>
</ul>
<p><img src="img/v4_tour_settings_fonts.png" alt="Font Details" /></p>
<p>Additional fonts can be added by clicking the <strong>Upload Font</strong> button and using the file uploader tool.</p>
<blockquote class="tip"><p>If the new font does not show in the text editor after upload, try clearing the browser cache!</p>
</blockquote>
</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>

200
manual/en/configure_folders.html Normal file
View File

@@ -0,0 +1,200 @@
<!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="configure">
<!-- 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><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><!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="configure_cms_settings.html">Configure CMS Settings</a></p>
</li>
<li>
<p><a href="configure_tags.html">Tags</a></p>
</li>
<li>
<p class="active"><a href="configure_folders.html">Folders</a></p>
</li>
<li>
<p><a href="configure_transitions.html">Transitions</a></p>
</li>
</ul>
</body></html>
<li><a href="troubleshooting.html" data-toc-name="troubleshooting">Troubleshooting</a></li>
</ul>
</div>
<div class="col-md-9" role="main">
<h1 id="folders">Folders <a href="#folders" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Folders are used throughout the CMS and provide a great way to organise and easily locate user items within the CMS. Additionally Folders can have view, edit, delete sharing options applied which will apply to all items saved to the Folder, making it an efficient way to control User/User Group permissions for User items.</p>
<p>Administrators are encouraged to assign User Groups to their Users, and then use Folder Share options to give these Users appropriate access to each other’s content. Folders can be assigned to new Users from the on-boarding wizard to ensure that they are up and running from the start.</p>
<p>Folders are managed from the Administration section of the main CMS menu where administrators can see detailed information including who the Folder has been shared with and a breakdown of its contents.</p>
<h3>Creating Folders</h3>
<p>Only administrators can create <strong>Folders</strong> under the <strong>Root Folder</strong>.</p>
<ul>
<li>
<p>Right click the <strong>Root Folder</strong> and select <strong>Create</strong> to add a new Folder to the tree.</p>
</li>
<li>
<p>Further options are available from the context menu by right clicking a Folder.</p>
</li>
<li>
<p>Configure View, Edit and Delete <strong>Share</strong> options to apply to Users/User Groups for individual Folders.</p>
</li>
</ul>
<p>Once set, all items contained or moved to that Folder will inherit the applied options.</p>
<blockquote class="tip"><p>Only Administrators can set Share options for Folders.
All elements of an item that need to be shared should also be moved to the Folder. This includes Media files contained on Layouts, and Layouts within Campaigns, as an example, if Users also require access to those.</p>
</blockquote>
<p>Users can be granted access via the <strong>Feature</strong> functionality, to create sub-folders under parent folders they have been given access to.</p>
<p>Sub-Folders added to a Folder will inherit any applied Share options from the Main Folder.</p>
<h3>Home Folder</h3>
<p>Assign a Home Folder to existing Users:</p>
<ul>
<li>Go to <strong>Users</strong> under the <strong>Administration</strong> section of the main CMS menu.</li>
<li>Use the row menu and select <strong>Set Home Folder</strong>.</li>
<li>Select a Folder to use, or right click to create a new Folder.</li>
</ul>
<blockquote class="tip"><p>If you want Group Administrator to have the ability to set Home Folder for Users, ensure that they have the appropriate <strong>Feature</strong> enabled!</p>
</blockquote>
<p>If a Folder is not selected, new content will automatically save into a Users default Home Folder location.</p>
<h3>Force Saving to a Folder</h3>
<p>Administrators can prevent Users from saving into the Root Folder and instead force them to select a Folder before saving by disabling the user of the Root Folder as a default:</p>
<ul>
<li>
<p>Navigate to <strong>Settings</strong> under the <strong>Administration</strong> section of the main CMS menu.</p>
</li>
<li>
<p>Click on the <strong>Sharing</strong> tab.</p>
</li>
<li>
<p>Untick <strong>Allow saving in the root folder</strong> option.</p>
</li>
<li>
<p>Click the <strong>Save</strong> button at the bottom.</p>
</li>
</ul>
<p>Once configured a User <em><strong>must</strong></em> select a named Folder.</p>
<h3>Move Folder</h3>
<p>Folders can be moved to another Folder location and added as a Sub-Folder using the <strong>Move Folder</strong> option from the context menu for a Folder.</p>
<p>The Folder and any contained sub-folders will be moved as a new sub-folder within the new Folder location maintaining the original Folder structure.</p>
<p>Moving a Folder that does not have any Share options set, will inherit any applied <strong>Share</strong> options of the destination Folder.</p>
<p>You can also select the <strong>Merge</strong> option to add the original Folder contents to the selected location, with the original Folder being deleted from the Folder tree.</p>
<h2 id="folder_management">Folder Management <a href="#folder_management" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Administrators can view, create and manage all Folders of the CMS from the Folders page under the Administration section of the main CMS menu.</p>
<p>This management page will show the Folders that have been shared with Users as well as folder contents. When viewing sub-folders from here, only the directly assigned share options will be shown, inherited options will not be shown.</p>
<p>As only empty folders can be removed, move, merge or delete contents before removing the folder.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="configure_tags.html">Managing Tags</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>Where can I find the Feature set for Folders to configure for Users/User Groups?</strong></em></p>
<p>Features are applied to a User/User Group by using the row menu for a selected User/User Group.</p>
<p><em><strong>What steps should I take take to allow Users the ability to Create their own Folders?</strong></em></p>
<ol>
<li>Enable <strong>Allow users to create Sub-Folders….</strong> from the Content tab of the <strong>Folders Feature</strong> set.</li>
<li>Enable <strong>View</strong> from the <strong>Share options</strong> for the parent folders(s) that can have sub-folders created under them by the User/User Group.</li>
</ol>
<p><em><strong>What steps should I take to allow Users access to rename Folders within the menu?</strong></em></p>
<ol>
<li>Enable <strong>Rename and Delete existing folders</strong> from the Content tab on the <strong>Folders Feature</strong> set.</li>
<li>Enable <strong>Edit</strong> from the <strong>Share options</strong> for the folder(s) that can be renamed by the User/User Group.</li>
</ol>
<p><em><strong>What steps should I take to allow Users access to delete Folders from the menu?</strong></em></p>
<ol>
<li>Enable <strong>Rename and Delete existing Folders</strong> from the Content tab on the <strong>Folders Feature</strong> set.</li>
<li>Enable <strong>Delete</strong> from the <strong>Share options</strong> for the folder(s) that can be removed by the User/User Group</li>
</ol>
</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>

152
manual/en/configure_tags.html Normal file
View File

@@ -0,0 +1,152 @@
<!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="configure">
<!-- 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><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><!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="configure_cms_settings.html">Configure CMS Settings</a></p>
</li>
<li>
<p class="active"><a href="configure_tags.html">Tags</a></p>
</li>
<li>
<p><a href="configure_folders.html">Folders</a></p>
</li>
<li>
<p><a href="configure_transitions.html">Transitions</a></p>
</li>
</ul>
</body></html>
<li><a href="troubleshooting.html" data-toc-name="troubleshooting">Troubleshooting</a></li>
</ul>
</div>
<div class="col-md-9" role="main">
<h1 id="tags">Tags <a href="#tags" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Tags are used throughout the CMS in order to easily organise and categorise items to make it easier for Users to locate and use. Tags act as keywords or labels which when assigned to items enhances the search functionality for Users.</p>
<p>Tags can be created by Users from various forms throughout the CMS, as well as created and managed by Administrators from the Tags page under the Administration section of the main CMS menu.</p>
<p>Create and assign <strong>Tags</strong> to items throughout the CMS using the Tag field on forms. As text is entered, an auto-complete helper will show possible matches to make it easier for Users to see what Tags are already available to select from:</p>
<ul>
<li>Select a <strong>Tag</strong> from the list or create a new one by directly typing in the Tag field.</li>
</ul>
<p>Tags can also be be created by Administrators from the <strong>Tags</strong> page under the <strong>Administration</strong> section of the main CMS menu.</p>
<ul>
<li>Click the <strong>Add Tag</strong> button and give it a <strong>Name</strong>.</li>
</ul>
<p>Tags can optionally have Tag Values associated with them. For example, you could have a Reception Tag, with reception areas across multiple sites. These could be differentiated using Values by creating a comma separated string of numbers, 1,2,3.</p>
<p>The <strong>Required Value</strong> checkbox is used to ensure that a User <em><strong>must</strong></em> select a Value in order to successfully assign the Tag to the item.</p>
<p>Once enabled, when the Tag is selected by Users, any associated Values will be shown for selection. A warning message will be shown to Users who do not select a Value to prompt them to do so.</p>
<p>Users can also add associated Values to Tags using the <strong>Tag Value</strong> field in forms.</p>
<p>Administrators can view all <strong>System Tags</strong> from the Tag management page and view Usage reports using the row menu for each individual Tag.</p>
<p>Use the <strong>With Selected</strong> option at the bottom of the grid to <strong>Delete</strong> Tags in bulk.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="configure_folders.html">Managing Folders</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em>Can I use filter options to exclude Tags from searches?</em></p>
<ul>
<li>Enter <code>-Tag</code> to exclude the tag from search results.</li>
<li>Enter <code>-|Value</code> to exclude the value from search results.</li>
<li>Enter <code>-Tag|Value</code> to exclude both tag and value from search results.</li>
</ul>
<p>You can have a comma separated mix of all the above!</p>
<ul>
<li>If you want to show all items that have <strong>not</strong> got a tag then enter <code>--no-tag</code>
</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>

141
manual/en/configure_transitions.html Normal file
View File

@@ -0,0 +1,141 @@
<!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="configure">
<!-- 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><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><!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="configure_cms_settings.html">Configure CMS Settings</a></p>
</li>
<li>
<p><a href="configure_tags.html">Tags</a></p>
</li>
<li>
<p><a href="configure_folders.html">Folders</a></p>
</li>
<li>
<p class="active"><a href="configure_transitions.html">Transitions</a></p>
</li>
</ul>
</body></html>
<li><a href="troubleshooting.html" data-toc-name="troubleshooting">Troubleshooting</a></li>
</ul>
</div>
<div class="col-md-9" role="main">
<h1 id="transition_management">Transition Management <a href="#transition_management" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Transitions are managed from the <strong>Transitions</strong> page under the <strong>Administration</strong> section of the main CMS menu. Configure which Transitions should be available to Users for assignment to Media items:</p>
<p><img src="img/v4_tour_transitions_grid.png" alt="Transitions Grid" /></p>
<ul>
<li>
<strong>Fade In</strong> - Increase Opacity from 0 to 100.</li>
<li>
<strong>Fade Out</strong> - Decrease Opacity from 100 to 0.</li>
<li>
<strong>Fly</strong> - Fly in or out on a compass point.</li>
</ul>
<h2 id="transition_defaults">Transition Defaults <a href="#transition_defaults" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Default Transitions can be easily enabled for all Widgets added to a Layout by ticking the <strong>Automatically apply Transitions?</strong> box from the Layout property panel:</p>
<p><img src="img/v4_tour_transitions_layout.png" alt="Transitions Layout" /></p>
<h2 id="playlist_transitions">Playlist Transitions <a href="#playlist_transitions" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>These are the Transitions between <strong>Media items</strong> on a <a href="media_playlists.html">Playlist</a> and are set as <strong>In</strong> and <strong>Out</strong> transitions.</p>
<blockquote class="tip"><p>The Transition form adapts depending on the Transition selected and the options available for that transition. In most cases it is necessary to select a duration for the Transition in Milliseconds and in the case of Fly, a direction must also be selected.</p>
</blockquote>
<h2 id="playlist_exit_transition">Playlist Exit Transition <a href="#playlist_exit_transition" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>A Playlist Exit Transition happens when the last Media Item to be displayed on a <a href="media_playlists.html">Playlist</a> is shown and allows for a different Exit Transition to be set.</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>

160
manual/en/contact_support.html Normal file
View File

@@ -0,0 +1,160 @@
<!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="contact_support">
<!-- 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><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><li><a href="contact_support.html" data-toc-name="contact_support">Contact Support</a></li>
</ul>
</div>
<div class="col-md-9" role="main">
<h1 id="contact_support">Contact Support <a href="#contact_support" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>We're here to help! If you have questions or need assistance with OTS Signs Command Center, please don't hesitate to reach out to our support team. We're committed to providing prompt and professional support to ensure your digital signage system runs smoothly.</p>
<h2 id="support_options">Support Options <a href="#support_options" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<h3 id="create_support_ticket">Create a Support Ticket</h3>
<p>For technical issues, feature requests, or general inquiries, we recommend creating a support ticket through our portal. This allows us to track your request and provide you with timely updates.</p>
<p><a href="https://portal.oribi-tech.com/new-ticket" class="btn btn-primary" target="_blank">Create a New Support Ticket</a></p>
<h3 id="email_support">Email Support</h3>
<p>You can also reach our support team directly via email at <a href="mailto:support@ots-signs.com">support@ots-signs.com</a>. Please include any relevant details about your issue, such as:</p>
<ul>
<li>A description of the problem or question</li>
<li>Steps you've taken to try to resolve the issue</li>
<li>Your OTS Signs Command Center version number</li>
<li>Information about your system setup (number of displays, display types, etc.)</li>
<li>Any error messages you've encountered</li>
</ul>
<h2 id="support_resources">Support Resources <a href="#support_resources" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Before contacting support, you may find answers to your questions in our documentation:</p>
<ul>
<li><a href="troubleshooting.html">Troubleshooting Guide</a> - Common issues and solutions</li>
<li><a href="index.html">User Manual</a> - Comprehensive documentation and user guides</li>
<li><a href="getting_started_showing_a_video.html">Getting Started</a> - Quick start guides for new users</li>
</ul>
<h2 id="what_to_expect">What to Expect <a href="#what_to_expect" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>When you contact our support team, you can expect:</p>
<ul>
<li><strong>Professional Service:</strong> Our experienced support specialists are knowledgeable about OTS Signs Command Center</li>
<li><strong>Prompt Response:</strong> We aim to acknowledge all support requests within 24 business hours</li>
<li><strong>Dedicated Assistance:</strong> Your support ticket is tracked from submission to resolution</li>
<li><strong>Quality Solutions:</strong> We work with you to diagnose and resolve issues efficiently</li>
</ul>
<h2 id="tips_for_faster_resolution">Tips for Faster Resolution <a href="#tips_for_faster_resolution" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>To help us assist you more quickly, please provide:</p>
<ul>
<li>Clear and detailed descriptions of the problem</li>
<li>Steps to reproduce the issue, if applicable</li>
<li>Screenshots or error messages that illustrate the problem</li>
<li>Your system configuration details</li>
<li>Any troubleshooting steps you've already attempted</li>
</ul>
<h2 id="other_resources">Additional Resources <a href="#other_resources" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>For additional information and resources:</p>
<ul>
<li>Review the <a href="troubleshooting.html">Troubleshooting Guide</a> for solutions to common problems</li>
<li>Explore the <a href="configure_cms_settings.html">Configuration and Organisation</a> section for system setup guidance</li>
<li>Check the <a href="displays.html">Displays</a> documentation for device management assistance</li>
</ul>
<p><strong>Thank you for choosing OTS Signs Command Center! We're excited to help you succeed with your digital signage deployment.</strong></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>

173
manual/en/displays.html Normal file
View File

@@ -0,0 +1,173 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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 class="active">
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="what_is_a_display?">What is a Display? <a href="#what_is_a_display?" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>OTS Signs Command Center helps you display content on your screens; whether you have existing content or need to create your own, to show on 1 screen or a 100.000, OTS Signs Command Center makes it easy!</p>
<p>OTS Signs Command Center uses the concept of Displays which are managed from the CMS to control when and how content is shown as well as provide device management tools for Users.</p>
<p>A <strong>Display</strong> is an essential part of digital signage as is it bridges the communication between the <strong>CMS</strong> software (Content Management System) and <strong>Media Player App</strong>.</p>
<p>The <strong>Player App</strong> is installed onto a <strong>Media Player</strong>, which can be a separate physical hardware device attached to a screen or an integrated Media Player found in supported System on Chip (SoC) professional signage monitors. A hardware key is generated on installing the Player App which creates a unique <strong>Display</strong> record in the CMS.</p>
<p>Once installed, the Player App must be <strong>Connected</strong> to the CMS by using a <strong>Code</strong> or by providing a <strong>CMS Key</strong>. Once connected a <strong>Display</strong> will be registered awaiting <strong>Authorisation</strong> in the CMS before it will become a managed device and start displaying content from the CMS.</p>
<h2 id="creating_a_display">Creating a Display <a href="#creating_a_display" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ol>
<li>
<strong>Download</strong> the Player App</li>
<li>
<strong>Install</strong> to the Player device. Some supported (SoC) System on Chip models will already have the Player App installed.</li>
<li>
<strong>Connect</strong> the Player App to the CMS.</li>
<li>
<strong>Authorise</strong> the Display using the row menu from the <strong>Displays</strong> page in the CMS.</li>
</ol>
<p>The Display will regularly connect to the CMS to check for any updated <a href="scheduling_events.html">schedule</a> information or any new content to download. The Displays grid will update to show the status, indicate if the Display has logged in recently, show the date and time stamp of when the Display was last accessed etc, to help you manage your network.</p>
<blockquote class="tip"><p>Any updates will be downloaded and saved to the Player App. This means that if a connection issue were to arise between the Display and CMS, the Display would continue to show scheduled content offline until the connection was restored.</p>
</blockquote>
<p>Manage <strong>Displays</strong> from the CMS and use the range of device management tools to effectively control your network. You can organise Displays into <a href="displays_groups.html">Display Groups</a>, apply configuration using <a href="displays_settings.html">Display Setting Profiles</a>, and monitor performance with <a href="displays_metrics.html">Reporting</a>.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="displays_configuration.html">Display Configuration</a></p>
<p><a href="displays_groups.html">Create Display Groups</a></p>
<p><a href="displays_settings.html">Apply settings using Display Profiles</a></p>
<p><a href="displays_sync_groups.html">Sync Groups</a></p>
<p><a href="displays_metrics.html">Reporting &amp; Metrics</a></p>
<h2 id="see_also">See Also <a href="#see_also" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li><a href="scheduling_events.html">Scheduling Events</a> — schedule content to show on your Displays</li>
<li><a href="layouts_editor.html">Layout Editor</a> — create the content your Displays will show</li>
<li><a href="media_library.html">Media Library</a> — manage media files used in your content</li>
<li><a href="troubleshooting.html">Troubleshooting</a> — resolve common Display connection issues</li>
</ul>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>Which Players can connect to the CMS using code?</strong></em></p>
<p>All Players, at the latest version support connecting via a code, with the exception of the Linux Player.</p>
<p><em><strong>Can I easily transfer a Display to another CMS?</strong></em></p>
<p>First you need to ensure that you have Two Factor Authentication set up, from the User Profile to use Transfer to another CMS setting from a Display row menu. Multiple Displays can be transferred using the With Selected option at the bottom of the Displays grid.</p>
<p><em><strong>Do the Player and CMS versions have to match?</strong></em></p>
<p>Our recommendation is that your CMS and Players should be of the same major version for the best results.</p>
<p><em><strong>What does it mean to Assign Files / Assign Layouts?</strong></em></p>
<p>Library files and Layouts can be directly assigned to a Display so that they are always available in the local library of the Player. This is useful for pre-loading a Layout ahead of time when the Layout will be used for some API integration to trigger a change for example. Content will still need to be scheduled to show on Displays.</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>

293
manual/en/displays_command_functionality.html Normal file
View File

@@ -0,0 +1,293 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li class="active">
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="command_functionality">Command Functionality <a href="#command_functionality" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>The Command Functionality in OTS Signs Command Center is used to configure a set of Commands for a User to select to execute via <strong>XMR</strong>, in a <strong>Schedule</strong> or include in a <strong>Layout</strong>.</p>
<blockquote class="tip"><p>Commands can have Command Strings to apply to all Players or have a different Command String per Player which is particularly useful if your network is mixed / connected to different Displays or have slightly different Player hardware.</p>
</blockquote>
<p>A <strong>Command record</strong> is created which allows for a “generic command” to be created which can be used across <strong>Display Profiles</strong>, <strong>Scheduled Events</strong> and the <strong>Shell Command Widget</strong>.</p>
<blockquote class="tip"><p>Commands provide easy access to functionality for RS232, Android Intents and Philips SoC (system on chip)!</p>
</blockquote>
<h2 id="command_management">Command Management <a href="#command_management" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Commands are created and managed from <strong>Commands</strong> under the <strong>Displays</strong> section of the main CMS menu:</p>
<p><img src="img/v4_displays_commands.png" alt="Display Commands" /></p>
<p>Use the row menu for a Command to Edit, Delete and set <a href="users_features_and_sharing.html#content-share">Share</a> options.</p>
<h3>Add Command</h3>
<p>Click on the <strong>Add Command</strong> button and complete the relevant form fields:</p>
<p><img src="img/v4_displays_commands_add_command.png" alt="add_command" /></p>
<p>Use the <strong>Command</strong> drop down menu to select from one of the following options to configure:</p>
<h4>Free Text</h4>
<p>Type in a Command String</p>
<blockquote class="tip"><p>The Command String represents the final executed Command and can be a direct call to the shell or can have a <strong>helper</strong> specified, see “Helpers” section below.</p>
</blockquote>
<h4>Philips Android</h4>
<p>The following commands can be used to control LED’s located on the sides of some commercial Phillips Displays:</p>
<pre><code>tpv_led|off
tpv_led|red
tpv_led|green
tpv_led|blue
tpv_led|white
</code></pre>
<p>From Android v2 R215, integration has been added to power on/off the screen backlight by using the following commands:</p>
<pre><code>tpv|backlighton
tpv|backlightoff
</code></pre>
<blockquote class="tip"><p>The below commands can be used for one specific Android 4 model only; 2016 model <a href="https://www.philips.co.uk/p-p/10BDL3051T_00/signage-solutions-multi-touch-display">10BDL3051T</a></p>
<pre><code>tpv|screenoff
tpv|screenon
</code></pre>
<p><code>screenoff</code> will turn the screen off and put in a lower power state which can then be turned back on with <code>screenon</code>.</p>
<p>For all other models, please use <code>backlighton/off</code> as <code>screenoff</code> will power completely off resulting in the need for an on site restart!</p>
</blockquote>
<p>Mute/unmute commands have also been added from v2 R215:</p>
<pre><code>tpv|mute
tpv|unmute
</code></pre>
<p><strong>Please note:</strong> <code>backlighton/off</code> doesn’t mute audio, so if you have audio playing you will will also want to schedule the above <code>mute/unmute</code> commands at the same time.</p>
<h4>RS232</h4>
<p>RS232 commands can be executed on Players by using the <code>rs232</code> prefix in the Command String. The format of the command is <code>rs232|&lt;connection string&gt;|&lt;command&gt;</code>.</p>
<p>The connection string should be provided in the following format on Windows:</p>
<pre><code>&lt;COM#&gt;,&lt;Baud Rate&gt;,&lt;Data Bits&gt;,&lt;Parity|None,Odd,Even,Mark,Space&gt;,&lt;StopBits|None,One,Two,OnePointFive&gt;,&lt;Handshake|None,XOnXOff,RequestToSend,RequestToSendXOnXOff&gt;,&lt;HexSupport|0,1,default 0&gt;
</code></pre>
<p><strong>Please note:</strong> If you need to send your Command in HEX format, you should specify the byte string in the Command String, for example: <code>7E 00 00 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 FF</code> , this will be converted to a byte stream by the player. You will need to set the <code>HexSupport</code> element of the connection string to <code>1</code>.</p>
<p>The connection string should be provided in the following format on Android:</p>
<pre><code>&lt;DeviceName&gt;,&lt;Baud Rate&gt;,&lt;Data Bits&gt;,&lt;Parity&gt;,&lt;StopBits&gt;,&lt;FlowControl&gt;
</code></pre>
<p>Each setting is represented by a corresponding number:</p>
<pre><code>DATA_BITS_5 = 5;
DATA_BITS_6 = 6;
DATA_BITS_7 = 7;
DATA_BITS_8 = 8;
PARITY_NONE = 0;
PARITY_ODD = 1;
PARITY_EVEN = 2;
PARITY_MARK = 3;
PARITY_SPACE = 4;
STOP_BITS_1 = 1;
STOP_BITS_15 = 3;
STOP_BITS_2 = 2;
FLOW_CONTROL_OFF = 0;
FLOW_CONTROL_RTS_CTS = 1;
FLOW_CONTROL_DSR_DTR = 2;
FLOW_CONTROL_XON_XOFF = 3;
</code></pre>
<p>The Command itself is a string which gets sent over RS232 using the connection details.</p>
<h4>Android Intent</h4>
<p>Android Display Profiles can use the <code>intent</code> helper to specify an intent that should be called when the Command executes. The format of the Command is <code>intent|&lt;type|activity,service,broadcast&gt;|&lt;activity&gt;|[&lt;extras&gt;]</code> .</p>
<p><code>[&lt;extras&gt;]</code> is an optional parameter available from <strong>Android v2 R206</strong> used to provide additional data to the Intent. This must be a JSON formatted string containing an array with at least one object. The object format is below and must be on one line.</p>
<pre><code class="language-json">{
&quot;name&quot;: &quot;&lt;extra name&gt;&quot;,
&quot;type&quot;: &quot;&lt;type|string,int,bool,intArray&gt;&quot;,
&quot;value&quot;: &lt;the value of the above type&gt;
}
</code></pre>
<p>For example, on some devices you can program the firmware to set on/off times.</p>
<pre><code>[{
&quot;name&quot;: &quot;timeon&quot;,
&quot;type&quot;: &quot;intArray&quot;,
&quot;value&quot;: [2018, 7, 28, 8, 40]
}, {
&quot;name&quot;: &quot;timeoff&quot;,
&quot;type&quot;: &quot;intArray&quot;,
&quot;value&quot;: [2018, 7, 28, 21, 40]
}]
</code></pre>
<p>This would be set on the command as:</p>
<pre><code>intent|broadcast|activity|[{ &quot;name&quot;: &quot;timeon&quot;, &quot;type&quot;: &quot;intArray&quot;, &quot;value&quot;: [2018, 7, 28, 8, 40] }, { &quot;name&quot;: &quot;timeoff&quot;, &quot;type&quot;: &quot;intArray&quot;, &quot;value&quot;: [2018, 7, 28, 21, 40] }]
</code></pre>
<blockquote class="tip"><p>Commands containing an intent helper are ignored in the Windows Player!</p>
</blockquote>
<h3>Helpers</h3>
<p><strong>Command Helpers</strong> are prefixes that can be added to the Command String in order to take a more advanced action. Commands without a prefix are executed in the shell of the operating system which runs the Player. <code>cmd.exe</code> on Windows and <code>shell</code> on Android.</p>
<h3>Validation</h3>
<p>The <strong>Validation String</strong> is used as a comparison to the <strong>Command</strong> output and if it matches then the Command is considered a success. The Validation String must be an exact match.</p>
<p>This could be useful for a network of mixed Windows and Android Players with a command called ‘Reboot’. The Command String for ‘Reboot’ on Windows being <code>shutdown /r /t 0</code>, and on Android, it is <code>reboot</code>.</p>
<blockquote class="tip"><p>The same can also be useful with a non-mixed network - imagine a network of Windows players with different monitors connected over HDMI/RS232. A single Command called ‘Monitor On’ can be created with the different brands of monitor represented by different Display Settings Profiles, each can have a different Command String to turn the monitor on/off.</p>
</blockquote>
<h3>Available on</h3>
<p>Select which type of Display the Command will be available on, leave blank to apply the Command to all types of Display.</p>
<blockquote class="tip"><p><strong>Command</strong> and <strong>Validation</strong> strings can be overridden by editing a <a href="displays_settings.html#setting_on_the_display">Display Profile</a> and using the <strong>Command</strong> tab!</p>
</blockquote>
<h2 id="send_command_xmr">Send Command XMR <a href="#send_command_xmr" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Execute Commands via <strong>XMR</strong> from Displays/Display Groups using the row menu:</p>
<h2 id="scheduling_commands">Scheduling Commands <a href="#scheduling_commands" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><strong>Schedule Commands</strong> so that they are executed at a specific time</p>
<ul>
<li>
<p>Click on <strong>Schedule</strong> from the main CMS menu.</p>
</li>
<li>
<p>Select <a href="scheduling_events.html#content-add-event">Add Event</a> from the top of the Schedule grid.</p>
</li>
<li>
<p>From the Event Type drop down select <strong>Command</strong>.</p>
</li>
<li>
<p>Complete the form fields and select the <strong>Command</strong> to use and <strong>Start Time</strong>.</p>
</li>
</ul>
<blockquote class="tip"><p>Scheduled commands are executed once on the Player and only require a <strong>Start</strong> date and time. The Command can be executed up to 10 seconds after the time selected.</p>
</blockquote>
<h2 id="shell_commands">Shell Commands <a href="#shell_commands" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Use the <a href="media_module_shellcommand.html">Shell Command Widget</a> to run external Commands based on the Layouts activity.</p>
<p>Shell Commands with a Command as their source act in the same fashion as normal shell commands. The Command is executed when the Widget is shown on the Layout.</p>
<p>A Shell Command can also be a Command String with options for all Players provided. This allows Users to add Commands ‘ad-hoc’ for one-time use.</p>
<blockquote class="tip"><p>We recommend that Administrators create predefined commands when possible!</p>
</blockquote>
<h2 id="monitor_on/off">Monitor ON/OFF <a href="#monitor_on/off" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<h3>HDMI-CEC</h3>
<p>HDMI-CEC is a bus that is implemented on nearly all new large-screen TVs that have HDMI connectors. This bus (which is physically connected within normal HDMI cables) supports control signals that can perform power-on, power off, volume adjusts, selection of video source and many of the features that are accessible via the TV’s remote control. It can also control most other hardware on the HDMI bus.</p>
<p>OTS Signs Command Center doesn’t provide a direct interface to HDMI-CEC as there are many different manufacturer specifications, however, it is possible to control HDMI-CEC via a batch file.</p>
<h3>Serial/RS232</h3>
<p>Industry grade monitors often have a serial interface for turning the monitor panel on and off. OTS Signs Command Center can use the RS232 Command helper to send these Commands to the monitor - usually in HEX mode.</p>
<p>The following monitors and Commands have been tested:</p>
<h4>NEC E464</h4>
<ul>
<li>Power On - <code>rs232|COM1,9600,8,None,One,None,1|01 30 41 30 41 30 43 02 43 32 30 33 44 36 30 30 30 31 03 73 0d</code>
</li>
<li>Power Off - <code>rs232|COM1,9600,8,None,One,None,1|01 30 41 30 41 30 43 02 43 32 30 33 44 36 30 30 30 34 03 76 0d</code>
</li>
</ul>
<h4>Sharp LC-42D69U</h4>
<ul>
<li>Power On - <code>rs232|COM1,9600,8,None,One,None,1|50 4F 57 52 31 20 20 20 0D</code>
</li>
<li>Power Off - <code>rs232|COM1,9600,8,None,One,None,1|50 4F 57 52 00 20 20 20 0D</code>
</li>
</ul>
<h4>LG 55LK520</h4>
<ul>
<li>Power On - <code>rs232|COM1,9600,8,None,One,None,1|6B 61 20 30 30 20 30 31 0D</code>
</li>
<li>Power Off - <code>rs232|COM1,9600,8,None,One,None,1|6B 61 20 30 30 20 30 30 0D</code>
</li>
</ul>
<blockquote class="tip"><p>It should be noted that other models of each brand should also use the same Commands.</p>
</blockquote>
</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>

173
manual/en/displays_configuration.html Normal file
View File

@@ -0,0 +1,173 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li class="active">
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="configuration_of_displays">Configuration of Displays <a href="#configuration_of_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Once Displays have been connected, they are configured and managed from the <strong>Displays</strong> page inside the CMS.</p>
<p>In order to start showing content, <strong>Displays</strong> must be <strong>Authorised</strong> with the CMS. Check the Displays grid to make sure the right Displays are showing as <strong>Authorised</strong>, as a first step.</p>
<ul>
<li>Give the <strong>Display</strong> a friendly name for easier identification within the CMS by using the <strong>Edit</strong> option from the row menu.</li>
</ul>
<p>Now is a great time to assign your Display a <strong>Default Layout</strong>. The Default Layout is shown when there is nothing else <a href="scheduling_events.html">scheduled</a>.</p>
<ul>
<li>Scroll down the form to select a <a href="layouts_editor.html">Layout</a> to use as the default. This Layout will be shown when there is no content scheduled or an issue arises that prevents scheduled content from showing on your Display.</li>
</ul>
<blockquote class="tip"><p>When creating your own Default Layouts, keep in mind that designs should be kept simple, avoiding any complex media and web content!</p>
</blockquote>
<ul>
<li>
<p>Click on the <strong>Details</strong> tab to provide further information about your Display.</p>
</li>
<li>
<p>Setting the <strong>Latitude</strong> and <strong>Longitude</strong> of the Display, will show its location on the map view.</p>
</li>
</ul>
<p>The <strong>Displays</strong> map can be viewed by clicking the icon next to the <strong>Folders</strong> toggle from the Displays grid:</p>
<p><img src="img/display_configuration_map_view_icon.png" alt="Display Map Icon" /></p>
<ul>
<li>Set <strong>Timezones</strong> to ensure that content is shown at the right time for your Display location.</li>
</ul>
<p>Each Display is assigned a default profile which will automatically apply its settings to all Displays of the same type. For example, you edit the Collect Interval for your Android Display Profile. Once saved, the new collection time will be applied to all Displays assigned this as a Display Profile.</p>
<p><a href="displays_settings.html">Display Setting Profiles</a> can be customised for automatic management and configuration of your Display Network.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="displays.html">What is a Display?</a></p>
<p><a href="displays_groups.html">Using Display Groups</a></p>
<p><a href="displays_settings.html">Apply settings using Display Profiles</a></p>
<h2 id="see_also">See Also <a href="#see_also" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li><a href="scheduling_events.html">Scheduling Events</a> — schedule content to Displays once configured</li>
<li><a href="displays_groups.html">Display Groups</a> — organise Displays into groups for easier management</li>
<li><a href="displays_metrics.html">Reporting</a> — monitor Display activity and uptime</li>
<li><a href="troubleshooting.html#display_connection_issues">Troubleshooting Display Connections</a> — resolve connection problems</li>
</ul>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>What happens if I have no content scheduled, and my default layout has an issue with downloading it’s content?</strong></em></p>
<p>The splash screen will be shown until the issue with the default layout is resolved or content is scheduled to show on the Display.</p>
<p><em><strong>What does the Cloud Icon in the Status column of the Display Grid indicate?</strong></em></p>
<p>The Cloud Icon shows that the Player has not logged in and content is waiting to be downloaded. A Cross indicates that the Player is yet to complete the download and a Tick shows the Player is up to date.</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>

175
manual/en/displays_groups.html Normal file
View File

@@ -0,0 +1,175 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li class="active">
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="display_groups">Display Groups <a href="#display_groups" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Group together specific <strong>Displays</strong> to allow content and schedules to span multiple Displays with just one configured <strong>Event</strong>, saving time and reducing errors. Grouping Displays makes it easier to manage an expanding network. Simply add newly connected <strong>Displays</strong> to an existing <strong>Display Group</strong> to inherit schedules and to quickly start showing content.</p>
<p>Group Displays by industry or location to make it easier to update and target content which differs by areas or purpose.</p>
<p>Display Groups can contain a mix of singular <strong>Displays</strong> as well as other <strong>Display Groups</strong> to allow you to easily target the right Displays to show your content.</p>
<p>For example, you could have Displays located within stores over different levels, intended to reach differing audiences so could have Display Groups that contain:</p>
<ul>
<li>All Displays in store A</li>
<li>All Displays in store B</li>
<li>All Displays that are street facing</li>
<li>All Displays on level 1</li>
<li>All Displays on level 2</li>
<li>All internal Displays</li>
<li>All external Displays</li>
</ul>
<p><strong>Create Display Groups</strong> and automatically assign <strong>Displays</strong> with matching criteria <strong>dynamically</strong> or <strong>manually</strong> selecting Display membership.</p>
<ul>
<li>Click on Add Display Group from the Display Groups grid.</li>
</ul>
<h2 id="dynamic_groups">Dynamic Groups <a href="#dynamic_groups" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>To assign members dynamically, tick the <strong>Dynamic Group</strong> checkbox.</p>
<ul>
<li>Set the <strong>filter criteria</strong> to use in the format of regular comma separated expressions or simple string comparisons.</li>
<li>Prefix expressions with a <code>-</code> to exclude from filters. For example, all Displays containing <code>a</code> but not <code>b</code> in the name would be <code>a, -b</code>
</li>
<li>
<strong>Criteria Tags</strong> can also be filtered using additional OR/AND filters for Displays with multiple Tags assigned.</li>
</ul>
<h2 id="manual_groups">Manual Groups <a href="#manual_groups" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>To assign members manually, leave the checkbox unticked and click to Save the form:</p>
<ul>
<li>Use the row menu for the new Display Group record and select <strong>Members</strong> using the checkbox for each Display.</li>
</ul>
<p>The Relationship Tree shows the ancestors and descendants. Parent Display Groups, shown above the selected Group will pass their schedule down to the Displays groups underneath.</p>
<h2 id="nested_groups">Nested Groups <a href="#nested_groups" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Display Groups can be nested to simplify scheduling to allow sub-groups to inherit permissions from a parent group.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="displays_configuration.html">Configuring Displays</a></p>
<p><a href="displays_sync_groups.html">Sync Groups</a></p>
<p><a href="displays_settings.html">Display Profile Settings</a></p>
<h2 id="see_also">See Also <a href="#see_also" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li><a href="scheduling_events.html">Scheduling Events</a> — schedule content to Display Groups</li>
<li><a href="displays.html">Displays</a> — connect and authorise individual Displays</li>
<li><a href="configure_tags.html">Tags</a> — use Tags to build dynamic Display Group criteria</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>

146
manual/en/displays_metrics.html Normal file
View File

@@ -0,0 +1,146 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li class="active">
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="reporting">Reporting <a href="#reporting" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>OTS Signs Command Center has a variety of reports to help users assess network health and uptime and Display statistics. Proof of Play data offers further insights into content performance shown across your Display network to reveal trends to enable stakeholders to refine <a href="scheduling_events.html">content scheduling</a> and placement for improved targeting and audience engagement.</p>
<p>Reports can be viewed in real time, emailed as a PDF to users and saved for future reference as well as scheduled to run on a Daily, Weekly, Monthly or Yearly basis.</p>
<p>Available metrics can be found by selecting <strong>All Reports</strong> under the <strong>Reporting</strong> section of the main CMS menu.</p>
<p>Similar Reports are grouped together to make it easier to find the data you need, which are presented as Charts as well as Tabular data so you can easily identify patterns and trends.</p>
<h2 id="see_also">See Also <a href="#see_also" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li><a href="displays.html">Displays</a> — manage and monitor your Display network</li>
<li><a href="scheduling_events.html">Scheduling</a> — schedule content to Displays</li>
<li><a href="configure_cms_settings.html">CMS Settings</a> — configure reporting defaults in CMS settings</li>
</ul>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>Can I remove the logo shown on exported reports?</strong></em></p>
<p>Go to Settings under the Administration section of the main CMS menu and select the General tab to control whether the logo should be shown.</p>
<p><em><strong>Can I set a collection of proof of play stats by default for Displays?</strong></em></p>
<p>From Settings under the Administration section of the main CMS menu, select Displays to enable Stats/Layout Stat Collection and Aggregation Level default for Displays.</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>

144
manual/en/displays_settings.html Normal file
View File

@@ -0,0 +1,144 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li class="active">
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li>
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="display_settings">Display Settings <a href="#display_settings" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Each Display has settings which can be configured individually. Settings can vary depending on the platform/media player type, using <strong>Display Setting Profiles</strong> you can easily apply different settings to <strong>Displays</strong> of the same platform or type.</p>
<p>Once connected to the CMS, each <strong>Display</strong> is assigned a default <strong>Display Profile</strong> to apply settings to Displays of the corresponding type.</p>
<p>Profiles can be customised or new ones added to suit Display requirements. For ease use the row menu and <strong>Copy</strong> an existing <strong>Profile</strong> to quickly create new Profiles with the required settings.</p>
<p>Use Display Profiles to provide your <strong>Licence Pool Code</strong> to all of your Displays centrally for easier licensing which is less prone to error than entering codes manually per device.</p>
<p>Create Display Profiles to cater for Landscape and Portrait <strong>orientations</strong> or to apply different <strong>operating hours</strong> or a Display Profile for devices that require <strong>multiple decoders</strong> enabled for example.</p>
<p>If individual Displays require different settings from those set in a Display Profile, override settings by editing the Display from the Displays grid.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="displays_configuration">Configure Displays</a></p>
<p><a href="scheduling_dayparting">Define Operating Hours using Dayparts</a></p>
<p><a href="displays_groups">Using Display Groups</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>I have a Display that should use an alternative Profile from the set default?</strong></em></p>
<p>Override individual Displays from the Displays grid. Click to Edit and use the Settings tab to select an alternative Settings Profile to use for the selected Display.</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>

165
manual/en/displays_sync_groups.html Normal file
View File

@@ -0,0 +1,165 @@
<!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="displays">
<!-- 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><li><a href="displays.html" data-toc-name="displays">Displays</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>
<a href="displays.html">Displays</a>
</li>
<li>
<a href="displays_configuration.html">Display Configuration</a>
</li>
<li>
<a href="displays_settings.html">Display Settings</a>
</li>
<li>
<a href="displays_groups.html">Display Groups</a>
</li>
<li class="active">
<a href="displays_sync_groups.html">Sync Groups</a>
</li>
<li>
<a href="displays_metrics.html">Reporting</a>
</li>
<li>
<a href="displays_command_functionality.html">Command Functionality</a>
</li>
</ul>
</body></html>
<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="sync_groups">Sync Groups <a href="#sync_groups" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Sync Groups contain the Displays that will show synchronised content. Content can be synchronised to play across 2 or more Displays in a mirrored or video wall configuration when scheduling a <a href="scheduling_events.html#content-synchronised-events">Synchronised Event</a>.</p>
<blockquote class="tip"><p>Sync Playlists on different Layouts using the <strong>Content Synchronisation Key</strong>.</p>
</blockquote>
<p><a href="displays.html">Displays</a> first need to be assigned to a <strong>Sync Group</strong>:</p>
<ul>
<li>Click on <strong>Sync Groups</strong> under the <strong>Displays</strong> section of the main CMS menu.</li>
<li>Select the <strong>Add Sync Group</strong> button.</li>
</ul>
<p><img src="img/v4_displays_add_sync_groups.png" alt="Add Sync Group" /></p>
<p>Sync Groups can be saved to Folders to easily control User/User Group levels of interaction for Displays as well as provide an additional way to organise.</p>
<blockquote class="tip"><p>All Displays in a Sync Group need to communicate using their LAN IP address over TCP on the publisher port specified. This is defaulted to 9590 but can be changed if that port is reserved.</p>
<p>We recommend using a wired network and high-powered similar devices for the best Synchronisation.</p>
</blockquote>
<ul>
<li>
<p>On saving use the <strong>Manage Membership</strong> form to select which Displays to include in this Group.</p>
</li>
<li>
<p>On saving use the Edit form use the drop down to select which Display should be the <strong>Lead Display</strong> for the Sync Group.</p>
</li>
<li>
<p>Click to <strong>Save</strong></p>
</li>
</ul>
<blockquote class="tip"><p>Content can now be scheduled to the Sync Group by clicking <strong>Schedule</strong> from the main CMS menu and selecting the <a href="scheduling_events.html#content-synchronised-events">Add Synchronised Event button</a>.</p>
</blockquote>
<h2 id="edit_/_manage_membership">Edit / Manage Membership <a href="#edit_/_manage_membership" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Manage a Sync Group by using the row menu:</p>
<ul>
<li>Select <strong>Edit</strong> to set an alternative Lead Display</li>
<li>Select <strong>Members</strong> to manage which Displays are members of the group.</li>
</ul>
<h4>Next…</h4>
<p><a href="scheduling_events.html#content-synchronised-events">Scheduling Synchronised Events</a></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>

34
manual/en/extract_endings.py Normal file
View File

@@ -0,0 +1,34 @@
import os
files = [
'displays_settings.html', 'displays_sync_groups.html', 'displays_command_functionality.html',
'scheduling_events.html', 'scheduling_overlays.html', 'scheduling_repeats.html',
'scheduling_dayparting.html', 'scheduling_geolocation.html', 'scheduling_layout_list.html',
'scheduling_ad_campaigns.html', 'scheduling_priority_display_order.html',
'layouts_editor.html', 'layouts_editor_data_widgets.html', 'layouts_editor_design_changes.html',
'layouts_editor_editing_tools.html', 'layouts_editor_global_elements.html',
'layouts_editor_library_search.html', 'layouts_editor_playlists.html',
'layouts_editor_using_templates.html', 'layouts_editor_widgets.html',
'layouts_interactive_actions.html', 'layouts_templates.html',
'media_library.html', 'media_playlists.html', 'media_datasets.html', 'media_menuboards.html',
'media_modules.html', 'media_modules_connectors.html', 'media_dashboard_service.html',
'media_resizing_images.html',
'users_administration.html', 'users_groups.html',
'configure_cms_settings.html', 'configure_folders.html', 'configure_tags.html',
'configure_transitions.html',
'troubleshooting.html', 'contact_support.html',
]
marker = ' </div>\n </div>\n </div>'
for fn in files:
with open(fn) as f:
content = f.read()
idx = content.rfind(marker)
if idx == -1:
print(f'=== {fn} === [marker not found]')
continue
snippet = content[max(0, idx-400):idx]
print(f'=== {fn} ===')
print(snippet[-350:])
print()

172
manual/en/getting_started_showing_a_playlist.html Normal file
View File

@@ -0,0 +1,172 @@
<!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="getting_started">
<!-- 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><!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="index.html">Introduction</a></p>
</li>
<li>
<p><a href="getting_started_showing_an_image.html">Show an Image</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_video.html">Show a Video</a></p>
</li>
<li>
<p class="active"><a href="getting_started_showing_a_playlist.html">Show a Playlist</a></p>
</li>
<li>
<p><a href="getting_started_sorting_and_filtering.html">Sort and Filter Grids</a></p>
</li>
</ul>
</body></html>
<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><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="showing_a_playlist_on_displays">Showing a Playlist on Displays <a href="#showing_a_playlist_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p><strong>Create</strong> a <strong>Playlist</strong> of content and <strong>Schedule</strong> to show on <strong>Displays</strong>.</p>
<p>You may have a set of content collated to meet a specific requirement which need to be shown in a rotating sequence on Displays. Playlists allow users to streamline resources and organise multiple content types to play in the order they need to be displayed.</p>
<p>Playlists can have content added by automatic assignment based on selected criteria or by manual selection. For this example Image content already uploaded to the CMS Media Library will be added to a Playlist manually.</p>
<h2 id="add_playlist">Add Playlist <a href="#add_playlist" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>Click on <strong>Playlists</strong> under the <strong>Library</strong> section of the main CMS menu.</li>
<li>Click the <strong>Add Playlist</strong> button.</li>
<li>Provide a <strong>Name</strong> for easy identification in the CMS.</li>
<li>Click Save and the <strong>Playlist Editor</strong> will open.</li>
</ul>
<h2 id="adding_content">Adding Content <a href="#adding_content" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>Using the Toolbox, click on <strong>Library image search</strong> to add Images from the CMS Library.</li>
<li>Use the filters to locate the <strong>Images</strong> to add.</li>
<li>Drag and drop images to add to the <strong>Timeline</strong>.</li>
<li>Re-order the sequence by drag and drop.</li>
</ul>
<p>You can view the total duration of the Playlist at the top of the Timeline.</p>
<ul>
<li>To change the duration of items in the Playlist, click to highlight and select the <strong>Advanced</strong> tab in the <strong>Properties Panel</strong>.</li>
<li>Tick the <strong>Set a duration</strong> box and provide a new duration in seconds.</li>
<li>Click the <strong>Save</strong> button to update the total duration of the Timeline.</li>
<li>Select <strong>Exit</strong> to return to the Playlists grid.</li>
</ul>
<h2 id="select_playlist">Select Playlist <a href="#select_playlist" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>From the Playlists grid use the filters to locate the Playlist.</li>
<li>Use the row menu and select <strong>Schedule</strong>.</li>
<li>Select which <strong>Displays</strong> to show the Playlist on.</li>
<li>If you want to use the default <strong>Always</strong> schedule, and happy with the default settings and have no further advanced scheduling options to set, you can click <strong>Finish</strong> to complete the schedule.</li>
<li>If you want to select alternative created <strong>Dayparts</strong> or <strong>Custom</strong> dates, select <strong>Next</strong>.</li>
<li>If you don’t need to apply any further scheduling options and are happy with the defaults set for <strong>Resolution</strong>, <strong>Background Colour</strong> etc. click to <strong>Finish</strong>.</li>
</ul>
<p>The CMS will now update a Schedule change and the Playlist will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="getting_started_showing_an_image.html">Show a full screen Image on Displays</a></p>
<p><a href="getting_started_showing_a_video.html">Show a full screen Video on Displays</a></p>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>I don’t see the wizard when scheduling a Playlist?</strong></em></p>
<p>A wizard was introduced in v4.4 to simplify the scheduling process. Use the link to view the earlier flow: <a href="getting_started_showing_a_playlist_v4.html">Showing a Playlist</a></p>
<p><em><strong>Can I add Widgets to a Playlist?</strong></em></p>
<p>Yes, Widgets can be added using the Playlist Editor using the top button from the Toolbox.</p>
<p><em><strong>I don’t see any Global or Data Elements to add to my Playlist?</strong></em></p>
<p>Elements are not available in the Playlist Editor. Data Widgets have a selection of Static Templates to choose from to display your data.</p>
<p><em><strong>Do I have to upload the files I want to use to the CMS Media Library before creating a Playlist?</strong></em></p>
<p>No, you can upload media directly to a Playlist by dragging the Upload card for a selected media type to the Timeline and use the file uploader.</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>

170
manual/en/getting_started_showing_a_playlist_v4.html Normal file
View File

@@ -0,0 +1,170 @@
<!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="">
<!-- 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><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="showing_a_playlist_on_displays">Showing a Playlist on Displays <a href="#showing_a_playlist_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p><strong>Create</strong> a <strong>Playlist</strong> of content and <strong>Schedule</strong> to show on <strong>Displays</strong>.</p>
<p>You may have a set of content collated to meet a specific requirement which need to be shown in a rotating sequence on Displays. Playlists allow users to streamline resources and organise multiple content types to play in the order they need to be displayed.</p>
<p>Playlists can have content added by automatic assignment based on selected criteria or by manual selection. For this example Image content already uploaded to the CMS Media Library will be added to a Playlist manually.</p>
<h2 id="add_playlist">Add Playlist <a href="#add_playlist" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>Click on <strong>Playlists</strong> under the <strong>Library</strong> section of the main CMS menu.</li>
<li>Click the <strong>Add Playlist</strong> button.</li>
<li>Provide a <strong>Name</strong> for easy identification in the CMS.</li>
<li>Click Save and the <strong>Playlist Editor</strong> will open.</li>
</ul>
<h2 id="adding_content">Adding Content <a href="#adding_content" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>Using the Toolbox, click on <strong>Library image search</strong> to add Images from the CMS Library.</li>
<li>Use the filters to locate the <strong>Images</strong> to add.</li>
<li>Drag and drop images to add to the <strong>Timeline</strong>.</li>
<li>Re-order the sequence by drag and drop.</li>
</ul>
<p>You can view the total duration of the Playlist at the top of the Timeline.</p>
<ul>
<li>To change the duration of items in the Playlist, click to highlight and select the <strong>Advanced</strong> tab in the <strong>Properties Panel</strong>.</li>
<li>Tick the <strong>Set a duration</strong> box and provide a new duration in seconds.</li>
<li>Click the <strong>Save</strong> button to update the total duration of the Timeline.</li>
<li>Select <strong>Exit</strong> to return to the Playlists grid.</li>
</ul>
<h2 id="select_playlist">Select Playlist <a href="#select_playlist" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<ul>
<li>
<p>From the Playlists grid use the filters to locate the Playlist.</p>
</li>
<li>
<p>Use the row menu and select <strong>Schedule</strong>.</p>
</li>
<li>
<p>The <strong>Select Playlist</strong> form will open to provide further configuration options for the Playlist:</p>
</li>
<li>
<p>Select a specific <strong>Resolution</strong> to use.</p>
</li>
<li>
<p>Set a <strong>colour</strong> to fill any gaps in the background if the Playlist content will not fill the screen.</p>
</li>
<li>
<p><strong>Save</strong> to close the <strong>Select Playlist</strong> form and continue with scheduling.</p>
</li>
</ul>
<h2 id="schedule_event">Schedule Event <a href="#schedule_event" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p>Complete the fields in the <strong>Schedule Event</strong> form:</p>
<ul>
<li>Give the event a <strong>Name</strong> for easier identification in the CMS.</li>
<li>Select which <strong>Displays</strong> this Playlist will be shown on.</li>
<li>From <strong>Dayparting</strong>, select <strong>Custom</strong> to set specific start and end dates/times or select <strong>Always</strong> to show the Playlist constantly.</li>
<li>Click <strong>Save.</strong>
</li>
</ul>
<p>The CMS will now update a Schedule change and the Playlist will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>Can I add Widgets to a Playlist?</strong></em></p>
<p>Yes, Widgets can be added using the Playlist Editor using the top button from the Toolbox.</p>
<p><em><strong>I don’t see any Global or Data Elements to add to my Playlist?</strong></em></p>
<p>Elements are not available in the Playlist Editor. Data Widgets have a selection of Static Templates to choose from to display your data.</p>
<p><em><strong>Do I have to upload the files I want to use to the CMS Media Library before creating a Playlist?</strong></em></p>
<p>No, you can upload media directly to a Playlist by dragging the Upload card for a selected media type to the Timeline and use the file uploader.</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>

193
manual/en/getting_started_showing_a_video.html Normal file
View File

@@ -0,0 +1,193 @@
<!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="getting_started">
<!-- 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><!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="index.html">Introduction</a></p>
</li>
<li>
<p><a href="getting_started_showing_an_image.html">Show an Image</a></p>
</li>
<li>
<p class="active"><a href="getting_started_showing_a_video.html">Show a Video</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_playlist.html">Show a Playlist</a></p>
</li>
<li>
<p><a href="getting_started_sorting_and_filtering.html">Sort and Filter Grids</a></p>
</li>
</ul>
</body></html>
<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><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="showing_a_video_on_displays">Showing a Video on Displays <a href="#showing_a_video_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Add a <strong>Video</strong> file to your <strong>Media Library</strong> and <strong>Schedule</strong> to play on <strong>Displays</strong>.</p>
<p>You may have Video content which has been created to showcase product promotions or show company updates to employees, ready to be shown full screen on your Display network.</p>
<p>Video files are first added to the Library by upload or by URL. For this example a Video file will be uploaded to the CMS Media Library.</p>
<h3>Add Media</h3>
<ul>
<li>
<p>Click on <strong>Media</strong> under the <strong>Library</strong> section of the main CMS menu.</p>
</li>
<li>
<p>Click the <strong>Add Media</strong> button.</p>
</li>
<li>
<p>Select <strong>Add files</strong> and select the Video file to upload.</p>
</li>
<li>
<p>Use the scroll bar to select a frame to use as the Video thumbnail, to make it easier to identify in Media Library lists.</p>
</li>
<li>
<p>Provide a new <strong>Name</strong> or leave this field blank to keep the original file name.</p>
</li>
<li>
<p>Click <strong>Start upload</strong>.</p>
</li>
<li>
<p>Once uploaded click <strong>Done</strong>.</p>
</li>
</ul>
<h3>Select Media</h3>
<ul>
<li>
<p>From the <strong>Media</strong> grid use the filters to make it easier to find the uploaded video file if required.</p>
</li>
<li>
<p>Use the row menu and select <strong>Schedule</strong>.</p>
</li>
<li>
<p>Select which <strong>Displays</strong> to show the video on.</p>
</li>
<li>
<p>If you want to use the default <strong>Always</strong> schedule, and happy with the default settings and have no further scheduling options to set, you can click <strong>Finish</strong> to complete the schedule.</p>
</li>
<li>
<p>If you want to select alternative created <strong>Dayparts</strong> or <strong>Custom</strong> dates, select <strong>Next</strong>.</p>
</li>
<li>
<p>To configure advanced scheduling options and override the duration of the video for example, click <strong>Next</strong>.</p>
</li>
<li>
<p><strong>Duration in loop</strong> determines how long this video should be shown each time it appears in a <strong>Schedule Loop</strong>.</p>
</li>
<li>
<p>You can specify a <strong>duration</strong> here and provide a lower duration to cut the video short. When setting a higher duration, the video will loop back to the beginning and play to satisfy the duration applied.</p>
</li>
<li>
<p>Click to <strong>Finish</strong> once all relevant fields have been completed.</p>
</li>
</ul>
<p>The CMS will now update a Schedule change and your Video will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="getting_started_showing_a_playlist.html">Use Playlists to show a carousal/slideshow of images</a></p>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>I don’t see the wizard when scheduling a Video?</strong></em></p>
<p>A wizard was introduced in v4.4 to simplify the scheduling process. Use the link to view the earlier flow: <a href="getting_started_showing_a_video_v4.html">Showing a Video</a></p>
<p><em><strong>What are Schedule Loops?</strong></em></p>
<p>A Schedule Loop is how media content will play when in schedules with other media content. For example, if you have scheduled 2 media items each with a 10 second duration to be shown at the same time for 1 hour, both items will play for their 10 second durations in fair rotation for the scheduled time.</p>
<p><em><strong>Which file format is recommended for Videos?</strong></em></p>
<p>We recommend H264 MP4 file format.</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>

164
manual/en/getting_started_showing_a_video_v4.html Normal file
View File

@@ -0,0 +1,164 @@
<!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="">
<!-- 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><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="showing_a_video_on_displays">Showing a Video on Displays <a href="#showing_a_video_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Add a <strong>Video</strong> file to your <strong>Media Library</strong> and <strong>Schedule</strong> to play on <strong>Displays</strong>.</p>
<p>You may have Video content which has been created to showcase product promotions or show company updates to employees, ready to be shown full screen on your Display network.</p>
<p>Video files are first added to the Library by upload or by URL. For this example a Video file will be uploaded to the CMS Media Library.</p>
<h3>Add Media</h3>
<ul>
<li>
<p>Click on <strong>Media</strong> under the <strong>Library</strong> section of the main CMS menu.</p>
</li>
<li>
<p>Click the <strong>Add Media</strong> button.</p>
</li>
<li>
<p>Select <strong>Add files</strong> and select the Video file to upload.</p>
</li>
<li>
<p>Use the scroll bar to select a frame to use as the Video thumbnail, to make it easier to identify in Media Library lists.</p>
</li>
<li>
<p>Provide a new <strong>Name</strong> or leave this field blank to keep the original file name.</p>
</li>
<li>
<p>Click <strong>Start upload</strong>.</p>
</li>
<li>
<p>Once uploaded click <strong>Done</strong>.</p>
</li>
</ul>
<h3>Select Media</h3>
<ul>
<li>From the <strong>Media</strong> grid use the filters to make it easier to find the uploaded video file if required.</li>
<li>Use the row menu and select <strong>Schedule</strong>:</li>
</ul>
<p>The <strong>Select Media</strong> form will open to provide further configuration options for the Video:</p>
<p><strong>Duration in loop</strong> determines how long the video should play each time it appears in a <strong>Schedule Loop</strong>.</p>
<ul>
<li>Set a lower duration to cut the original file short or set a higher duration and the video will “loop” back to the beginning to satisfy a longer set duration.</li>
<li>Select a a specific <strong>Resolution</strong> to use.</li>
<li>Set a <strong>colour</strong> to fill any gaps in the background if the media file will not fill the screen.</li>
<li>
<strong>Save</strong> to close the <strong>Select Media</strong> form and continue with scheduling.</li>
</ul>
<h3>Schedule Event</h3>
<p>Complete the fields in the <strong>Schedule Event</strong> form:</p>
<ul>
<li>Give the event a <strong>Name</strong> for easier identification in the CMS.</li>
<li>Select which <strong>Displays</strong> this Video will be shown on.</li>
<li>From <strong>Dayparting</strong>, select <strong>Always</strong> to show the Video constantly or select <strong>Custom</strong> to set specific start and end dates/times.</li>
<li>Click <strong>Save.</strong>
</li>
</ul>
<p>The CMS will now update a Schedule change and your Video will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>What are Schedule Loops?</strong></em></p>
<p>A Schedule Loop is how media content will play when in schedules with other media content. For example, if you have scheduled 2 media items each with a 10 second duration to be shown at the same time for 1 hour, both items will play for their 10 second durations in fair rotation for the scheduled time.</p>
<p><em><strong>Which file format is recommended for Videos?</strong></em></p>
<p>We recommend H264 MP4 file format.</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>

176
manual/en/getting_started_showing_an_image.html Normal file
View File

@@ -0,0 +1,176 @@
<!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="getting_started">
<!-- 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><!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="index.html">Introduction</a></p>
</li>
<li>
<p class="active"><a href="getting_started_showing_an_image.html">Show an Image</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_video.html">Show a Video</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_playlist.html">Show a Playlist</a></p>
</li>
<li>
<p><a href="getting_started_sorting_and_filtering.html">Sort and Filter Grids</a></p>
</li>
</ul>
</body></html>
<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><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="showing_an_image_on_displays">Showing an Image on Displays <a href="#showing_an_image_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Add an <strong>Image</strong> file to your <strong>Media Library</strong> and <strong>Schedule</strong> to play on <strong>Displays</strong>.</p>
<p>You may have image content created outside of the Layout Editor, e.g. created by an agency, in house marketing team etc, ready to be shown full screen on your Display network.</p>
<p>Image files are first added to the Library by upload or by URL. For this example an Image file will be uploaded to the CMS Media Library.</p>
<h3>Add Media</h3>
<ul>
<li>
<p>Click on <strong>Media</strong> under the <strong>Library</strong> section of the main CMS menu.</p>
</li>
<li>
<p>Click the <strong>Add Media</strong> button.</p>
</li>
<li>
<p>Select <strong>Add files</strong> and select the Image file to upload.</p>
</li>
<li>
<p>Provide a new <strong>Name</strong> or leave this field blank to keep the original file name.</p>
</li>
<li>
<p>Click <strong>Start upload</strong>.</p>
</li>
<li>
<p>Once uploaded click <strong>Done</strong>.</p>
</li>
</ul>
<h3>Select Media</h3>
<ul>
<li>From the <strong>Media</strong> grid use the filters to make it easier to find the uploaded <strong>Image</strong> file if required.</li>
<li>Use the row menu and select <strong>Schedule</strong>:</li>
</ul>
<p><img src="img/v4_showing_images_videos_row_menu_schedule.png" alt="Media Row Menu Schedule" /></p>
<ul>
<li>Select which <strong>Displays</strong> to show the Image on.</li>
<li>If you want to use the default <strong>Always</strong> schedule, and happy with the default settings and have no further advanced scheduling options to set, you can click <strong>Finish</strong> to complete the schedule.</li>
<li>If you want to select alternative created <strong>Dayparts</strong> or <strong>Custom</strong> dates, select <strong>Next</strong>.</li>
<li>If you don’t need to apply any further scheduling options and are happy with the defaults set for <strong>Duration in Loop</strong>, <strong>Resolution</strong> etc, click to <strong>Finish</strong>.</li>
</ul>
<blockquote class="tip"><p><strong>Duration in loop</strong> determines how long this Image should be shown each time it appears in a <strong>Schedule Loop</strong>.</p>
</blockquote>
<p>The CMS will now update a Schedule change and the Image will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="getting_started_showing_a_playlist.html">Use Playlists to show a carousal/slideshow of images</a></p>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>I don’t see the wizard when scheduling an Image?</strong></em></p>
<p>A wizard was introduced in v4.4 to simplify the scheduling process. Use the link to view the earlier flow: <a href="getting_started_showing_an_image_v4.html">Showing an Image</a></p>
<p><em><strong>What are Schedule Loops?</strong></em></p>
<p>A Schedule Loop is how media content will play when in schedules with other media content. For example, if you have scheduled 2 media items each with a 10 second duration to be shown at the same time for 1 hour, both items will play for their 10 second durations in fair rotation for the scheduled time.</p>
<p><em><strong>What file extensions are supported on upload?</strong></em></p>
<p>Valid file extensions: jpg,jpeg,png,bmp,gif,webp.</p>
<p><em><strong>Can I upload an animated gif?</strong></em></p>
<p>Animated gif’s are not supported.</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>

171
manual/en/getting_started_showing_an_image_v4.html Normal file
View File

@@ -0,0 +1,171 @@
<!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="">
<!-- 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><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="showing_an_image_on_displays">Showing an Image on Displays <a href="#showing_an_image_on_displays" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Add an <strong>Image</strong> file to your <strong>Media Library</strong> and <strong>Schedule</strong> to play on <strong>Displays</strong>.</p>
<p>You may have image content created outside of the Layout Editor, e.g. created by an agency, in house marketing team etc, ready to be shown full screen on your Display network.</p>
<p>Image files are first added to the Library by upload or by URL. For this example an Image file will be uploaded to the CMS Media Library.</p>
<h3>Add Media</h3>
<ul>
<li>
<p>Click on <strong>Media</strong> under the <strong>Library</strong> section of the main CMS menu.</p>
</li>
<li>
<p>Click the <strong>Add Media</strong> button.</p>
</li>
<li>
<p>Select <strong>Add files</strong> and select the Image file to upload.</p>
</li>
<li>
<p>Provide a new <strong>Name</strong> or leave this field blank to keep the original file name.</p>
</li>
<li>
<p>Click <strong>Start upload</strong>.</p>
</li>
<li>
<p>Once uploaded click <strong>Done</strong>.</p>
</li>
</ul>
<h3>Select Media</h3>
<ul>
<li>From the <strong>Media</strong> grid use the filters to make it easier to find the uploaded <strong>Image</strong> file if required.</li>
<li>Use the row menu and select <strong>Schedule</strong>:</li>
</ul>
<p><img src="img/v4_showing_images_videos_row_menu_schedule.png" alt="Media Row Menu Schedule" /></p>
<p>The <strong>Select Media</strong> form will open to provide further configuration options for the Image:</p>
<p><strong>Duration in loop</strong> determines how long this Image should be shown each time it appears in a <strong>Schedule Loop</strong>.</p>
<ul>
<li>Specify a <strong>duration</strong> to override the Image file duration.</li>
<li>Select a a specific <strong>Resolution</strong> to use.</li>
<li>Set a <strong>colour</strong> to fill any gaps in the background if the Image will not fill the screen.</li>
<li>
<strong>Save</strong> to close the <strong>Select Media</strong> form and continue with scheduling.</li>
</ul>
<h3>Schedule Event</h3>
<p>Complete the fields in the <strong>Schedule Event</strong> form:</p>
<ul>
<li>
<p>Give the event a <strong>Name</strong> for easier identification in the CMS.</p>
</li>
<li>
<p>Select which <strong>Displays</strong> this Image will be shown on.</p>
</li>
<li>
<p>From <strong>Dayparting</strong>, select <strong>Custom</strong> to set specific start and end dates/times or choose <strong>Always</strong> to show the Image on Displays constantly.</p>
</li>
<li>
<p>Click <strong>Save.</strong></p>
</li>
</ul>
<p>The CMS will now update a Schedule change and the Image will be shown on Displays for the timings set in the schedule.</p>
<h2 id="further_reading">Further Reading <a href="#further_reading" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><a href="layouts_editor.html">Use the Layout Editor to create your own content</a></p>
<h2 id="faqs">FAQs <a href="#faqs" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h2>
<p><em><strong>What are Schedule Loops?</strong></em></p>
<p>A Schedule Loop is how media content will play when in schedules with other media content. For example, if you have scheduled 2 media items each with a 10 second duration to be shown at the same time for 1 hour, both items will play for their 10 second durations in fair rotation for the scheduled time.</p>
<p><em><strong>What file extensions are supported on upload?</strong></em></p>
<p>Valid file extensions: jpg,jpeg,png,bmp,gif,webp.</p>
<p><em><strong>Can I upload an animated gif?</strong></em></p>
<p>Animated gif’s are not supported.</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>

143
manual/en/getting_started_sorting_and_filtering.html Normal file
View File

@@ -0,0 +1,143 @@
<!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="getting_started">
<!-- 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><!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="index.html">Introduction</a></p>
</li>
<li>
<p><a href="getting_started_showing_an_image.html">Show an Image</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_video.html">Show a Video</a></p>
</li>
<li>
<p><a href="getting_started_showing_a_playlist.html">Show a Playlist</a></p>
</li>
<li>
<p class="active"><a href="getting_started_sorting_and_filtering.html">Sort and Filter Grids</a></p>
</li>
</ul>
</body></html>
<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><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="sorting_and_filtering">Sorting and Filtering <a href="#sorting_and_filtering" class="header-link"><span class="glyphicon glyphicon-link"></span></a></h1>
<p>Page information within the CMS is presented as tabular data in a grid format. <strong>Grids</strong> have a number of features that when combined create a flexible tool for Users making it easier to visualize and understand presented information.</p>
<p>Multiple filter fields can be used to restrict criteria for returned results.</p>
<ul>
<li>
<p>Use the checkbox to apply advanced filtering options for Names using Regex and provide AND/OR criteria using comma separated terms.</p>
</li>
<li>
<p>The <strong>Advanced</strong> tab provides access to further filtering options for pages.</p>
</li>
</ul>
<p>Results are populated into columns, which can be sorted by clicking on the column header or by using the Shift key to sort multiple columns that contain up/down arrows.</p>
<ul>
<li>Hold shift and click on the column headings to sort in the order selected.</li>
</ul>
<p>The <strong>Column Visibility</strong> button is used to select/de-select which columns are needed in the data table, making it an extremely useful tool for Users to customise which columns should be visible for each grid.</p>
<p>If the number of columns selected can not fit to your screen size, the information will be hidden as additional rows, indicated by a + icon at the beginning of the row. Clicking on this icon will show the hidden information.</p>
<p>At the bottom of selected grids, a <strong>With Selected</strong> option is available for users to multi-select rows in order to easily perform bulk actions, such as Deleting, Sharing and moving items to Folders.</p>
<p>Use the row menu to access a set of actions for a selected item. Selected row menu actions across grids have an ‘auto submit’ capability. Once ticked the action will be automatically submitted without any further confirmation requirements when next selected.</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>

BIN
manual/en/img/display_configuration_map_view_icon.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.3 KiB

BIN
manual/en/img/how_to_create_a_layout.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 50 KiB

BIN
manual/en/img/how_to_create_a_playlist.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 176 KiB

BIN
manual/en/img/how_to_creating_user_groups.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 977 KiB

BIN
manual/en/img/how_to_creating_users.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.3 MiB

BIN
manual/en/img/how_to_design_changes.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 646 KiB

BIN
manual/en/img/how_to_display_configuration.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 548 KiB

BIN
manual/en/img/how_to_layout_list_campaign.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 440 KiB

BIN
manual/en/img/how_to_managing_folders.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 369 KiB

BIN
manual/en/img/how_to_managing_tags.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 564 KiB

BIN
manual/en/img/how_to_show_a_video.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 876 KiB

BIN
manual/en/img/how_to_show_an_image.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 542 KiB

BIN
manual/en/img/how_to_simple_scheduling.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 70 KiB

BIN
manual/en/img/how_to_simple_scheduling_4_4.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 MiB

BIN
manual/en/img/how_to_sorting_and_filtering.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 MiB

BIN
manual/en/img/how_to_use_global_elements.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
manual/en/img/how_to_use_library_searches.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 208 KiB

BIN
manual/en/img/how_to_using_editing_tools.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 386 KiB

BIN
manual/en/img/how_to_using_repeats.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 MiB

BIN
manual/en/img/how_to_using_templates.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 172 KiB

BIN
manual/en/img/how_to_what_is_a_display.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 94 KiB

BIN
manual/en/img/layout_editor_overview_explainer.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 79 KiB

BIN
manual/en/img/layouts_toolbar_1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.8 KiB

BIN
manual/en/img/media_module_emergency_alerts_elements.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 84 KiB

BIN
manual/en/img/media_module_national_weather_alerts_elements.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 95 KiB

BIN
manual/en/img/report-fault-step1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

BIN
manual/en/img/v4.1_layouts_add_layout.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
manual/en/img/v4.1_layouts_editor_add_playlists.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 109 KiB

BIN
manual/en/img/v4.1_layouts_editor_convert_playlist.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 188 KiB

BIN
manual/en/img/v4.1_layouts_editor_playlist_cycle_playback.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 41 KiB

BIN
manual/en/img/v4.1_layouts_editor_playlist_spots.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 110 KiB

BIN
manual/en/img/v4.1_layouts_editor_playlists_preview_content.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 127 KiB

BIN
manual/en/img/v4.1_layouts_editor_synchronisation_key.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

BIN
manual/en/img/v4.1_layouts_layout_editor_overview.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 136 KiB

BIN
manual/en/img/v4.1_media_playlists_embedding.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 146 KiB

BIN
manual/en/img/v4.1_media_playlists_grid.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 39 KiB

BIN
manual/en/img/v4_campaigns_ad_campaign_grid.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
manual/en/img/v4_campaigns_assign_layouts.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

BIN
manual/en/img/v4_campaigns_assign_layouts_ad_campaign.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 684 KiB

BIN
manual/en/img/v4_campaigns_edit_ad_campaign.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 44 KiB

BIN
manual/en/img/v4_campaigns_edit_layout_list.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

BIN
manual/en/img/v4_campaigns_view_added_ad_campaigns.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 84 KiB

BIN
manual/en/img/v4_displays_add_sync_groups.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
manual/en/img/v4_displays_administration_display_map_status.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 728 KiB

BIN
manual/en/img/v4_displays_administration_grid.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

BIN
manual/en/img/v4_displays_administration_map_view.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.4 MiB

BIN
manual/en/img/v4_displays_bandwidth.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
manual/en/img/v4_displays_bandwidth_display.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 31 KiB

BIN
manual/en/img/v4_displays_commands.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
manual/en/img/v4_displays_commands_add_command.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

BIN
manual/en/img/v4_displays_edit_form.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 32 KiB

BIN
manual/en/img/v4_displays_edit_profilesettings.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 60 KiB

BIN
manual/en/img/v4_displays_group_dynamic.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 24 KiB

BIN
manual/en/img/v4_displays_groups_add.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

BIN
manual/en/img/v4_displays_groups_grid.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
manual/en/img/v4_displays_groups_memberships.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

BIN
manual/en/img/v4_displays_manage_dashboard.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

BIN
manual/en/img/v4_displays_move_cms.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
manual/en/img/v4_displays_proof_of_play_dashboard.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
manual/en/img/v4_displays_proofofplay.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

BIN
manual/en/img/v4_displays_proofofplay_summary_report.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
manual/en/img/v4_displays_reporting.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 43 KiB

BIN
manual/en/img/v4_displays_reporting_proof_of_play_type.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
manual/en/img/v4_displays_settings_profiles.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
manual/en/img/v4_displays_status_marker_cluster_chart.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 65 KiB

BIN
manual/en/img/v4_displays_summary_connected.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

BIN
manual/en/img/v4_displays_time_connected.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 47 KiB

BIN
manual/en/img/v4_layouts_actions_tab.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 17 KiB

BIN
manual/en/img/v4_layouts_add_layout.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
manual/en/img/v4_layouts_add_template_form.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
manual/en/img/v4_layouts_add_text_element.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 129 KiB

BIN
manual/en/img/v4_layouts_campaign_add_ad_campaign.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
manual/en/img/v4_layouts_campaign_add_layout_list.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

BIN
manual/en/img/v4_layouts_campaigns_grid.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 31 KiB

BIN
manual/en/img/v4_layouts_data_elements.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 17 KiB

BIN
manual/en/img/v4_layouts_data_slots_groups.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 106 KiB

BIN
manual/en/img/v4_layouts_duplicated_elements.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 80 KiB

BIN
manual/en/img/v4_layouts_editor_clock_configuration.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

BIN
manual/en/img/v4_layouts_editor_context_menu.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 54 KiB

Some files were not shown because too many files have changed in this diff Show More