Vizrt Feed Streamer User Guide

Version 1.5 Copyright © 2018 Vizrt. All rights reserved. No part of this software, documentation or publication may be reproduced, transcribed, stored in a retrieval system, translated into any language, computer language, or transmitted in any form or by any means, electronically, mechanically, magnetically, optically, chemically, photocopied, manually, or otherwise, without prior written permission from Vizrt. Vizrt specifically retains title to all Vizrt software. This software is supplied under a license agreement and may only be installed, used or copied in accordance to that agreement.

Disclaimer Vizrt provides this publication “as is” without warranty of any kind, either expressed or implied. This publication may contain technical inaccuracies or typographical errors. While every precaution has been taken in the preparation of this document to ensure that it contains accurate and up-to- date information, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained in this document. Vizrt’s policy is one of continual development, so the content of this document is periodically subject to be modified without notice. These changes will be incorporated in new editions of the publication. Vizrt may make improvements and/or changes in the product (s) and/ or the program(s) described in this publication at any time. Vizrt may have patents or pending patent applications covering subject matters in this document. The furnishing of this document does not give you any license to these patents.

Technical Support For technical support and the latest news of upgrades, documentation, and related products, visit the Vizrt web site at www.vizrt.com.

Created on 2018/03/12 Vizrt Feed Streamer User Guide - Version 1.5

Contents

1 Introduction...... 11 1.1 Feed Streamer Components ...... 12 1.2 Related Documents ...... 13 1.3 Customer Feedback and Suggestions ...... 13 1.4 Customer Support Request ...... 14 1.4.1 Before Submitting a Support Request...... 14 1.4.2 Submitting a Support Request...... 14 1.4.3 System Log Files ...... 15

2 Requirements ...... 16 2.1 Data Hub and Feed Streamer Server Requirements ...... 16 2.1.1 Hardware...... 16 2.1.2 Software ...... 17 2.2 Feed Streamer Client Requirements...... 17 2.2.1 Hardware...... 17 2.2.2 Software ...... 17 2.3 Social TV Plugin Requirements ...... 18 2.3.1 Hardware...... 18 2.3.2 Software ...... 18 2.4 Upgrading...... 18 2.4.1 Clean upgrade ...... 18 2.4.2 Migrating data when upgrading ...... 18 2.5 Product Notifications...... 19

3 Installation...... 20 3.1 There are two main installers: ...... 20 3.2 Installation Recommendations ...... 20 3.3 Feed Streamer Server and Data Hub Installation ...... 21 3.3.1 Clean installation...... 22 3.3.2 Upgrade from previous versions ...... 23 3.4 Feed Streamer Client Installation...... 24 3.4.1 Clean Installation...... 24 3.4.2 Upgrade from Previous Versions ...... 26 3.5 Installing the Social TV Viz Plugins ...... 27 3.5.1 To install the Social TV Plugins ...... 27 3.6 Installing Individual Software Packages ...... 27

3 Vizrt Feed Streamer User Guide - Version 1.5

3.6.1 Installing the Data Hub ...... 28 3.6.2 Installing the Feed Streamer Server ...... 28 3.6.3 Installing the Viz Ticker Feed Service ...... 29 3.6.4 Installing the Feed Streamer Client...... 29 3.7 Installing the Chrome Extension for Feed Streamer ...... 30 3.7.1 Installing the Chrome Extension for Feed Streamer ...... 31

4 Configuration ...... 33 4.1 Configuring Ports...... 33 4.1.1 Modifying the port number ...... 33 4.2 Configuring the Viz Trio Client...... 34 4.2.1 Configuring Viz Trio 2.12 and Later...... 34 4.2.2 To assign a keyboard shortcut in Viz Trio ...... 34 4.2.3 Configuring Viz Trio 2.11 and Earlier ...... 35 4.3 Configuring the Feed Streamer...... 35 4.3.1 Internet Access via Proxy ...... 36 4.3.2 Feed Streamer Shared and Local Settings ...... 37 4.3.3 Media Caching Settings...... 42 4.3.4 Adding Custom Reader Configurations ...... 45 4.3.5 Changing the Data Hub URI, Trio MSE or Ticker MSE ...... 45 4.3.6 Configuring Data Hub Backup and Load Balancing ...... 49 4.4 Configuring the Chrome Extension for Feed Streamer ...... 51 4.4.1 Configuring the DataHub ...... 51 4.4.2 The Extension’s User Interface...... 52 4.4.3 Defining a Default Group and Source ...... 54 4.5 Configuring the Viz Ticker Feed Service ...... 56 4.5.1 Install ...... 56 4.5.2 Run as application ...... 56 4.5.3 Configure (expert) ...... 57 4.5.4 Enabling cached file checking ...... 58

5 Working with Feed Streamer ...... 59 5.1 Feed Streamer Workflow...... 59 5.2 Working with Sources...... 60 5.2.1 Adding a Source ...... 61 5.2.2 Enabling/disabling a Source...... 63 5.2.3 Deactivate with power icon ...... 63 5.2.4 Deactivate by right-clicking a source...... 64 5.2.5 Modifying a Source ...... 64 5.2.6 Deleting a Source...... 65 5.2.7 Message Limitation...... 67

4 Vizrt Feed Streamer User Guide - Version 1.5

5.2.8 Profanity Filter ...... 67 5.2.9 Auto-approving Items ...... 68 5.2.10 Reflect Feed...... 68 5.2.11 Grouped Sources ...... 69 5.2.12 New and total items...... 70 5.3 Working with Groups ...... 71 5.3.1 Add a Group ...... 71 5.3.2 Modify a Group...... 71 5.3.3 Delete a Group ...... 72 5.3.4 Delete multiple groups ...... 72 5.4 Working with Items ...... 72 5.4.1 Viewing Items ...... 73 5.4.2 Delete Items ...... 74 5.4.3 Previewing Items...... 74 5.4.4 Re-order moderated items ...... 76 5.4.5 Moderate Items...... 78 5.4.6 Edit Mode ...... 80 5.5 Moderation ...... 90 5.5.1 Add a message to a source or group...... 90 5.5.2 Download Media ...... 93 5.5.3 Moderation by Source ...... 94 5.5.4 Moderation by Group...... 97 5.5.5 Grid View and List View...... 100 5.5.6 Copy URI...... 102 5.5.7 Empty moderated items ...... 102 5.5.8 Searching Items ...... 105 5.6 Destinations...... 107 5.6.1 Destination - Ticker ...... 108 5.6.2 Destination - Trio...... 110 5.6.3 Live Playout ...... 111 5.6.4 Media caching buttons in Live Playout...... 113 5.6.5 Missing media warning message...... 114 5.7 Top menu navigation ...... 114 5.8 Working with Spaces ...... 115 5.8.1 Creating a Space...... 115 5.8.2 Adding Sources to Spaces ...... 116 5.8.3 Adding Groups to Spaces...... 117 5.8.4 Viewing Spaces ...... 119 5.8.5 Renaming a Space...... 120 5.9 Feed Streamer themes...... 121 5.9.1 Selecting a theme ...... 121

5 Vizrt Feed Streamer User Guide - Version 1.5

5.9.2 Carbon theme...... 122 5.9.3 Steel theme...... 123 5.10 Users List...... 124 5.11 Import/export utility ...... 125 5.11.1 Export tab ...... 125 5.11.2 Import tab ...... 125

6 Default Source Types ...... 126 6.1 Edit source settings...... 126 6.2 Atom ...... 127 6.3 BBC feed ...... 127 6.4 Facebook ...... 128 6.4.1 To use ...... 129 6.4.2 Common Parameters ...... 130 6.4.3 Facebook Polls...... 132 6.4.4 Facebook Reactions ...... 133 6.4.5 Facebook Q&A ...... 135 6.4.6 Facebook Rate Limit...... 136 6.5 Flicker...... 137 6.6 GeoChart ...... 137 6.7 Instagram ...... 139 6.8 Mashable ...... 140 6.9 RSS ...... 140 6.10 SQL Plugin ...... 141 6.10.1 Connect to a database ...... 141 6.10.2 SQL Plugin Query Modes ...... 143 6.11 TechCrunch ...... 151 6.12 Twitter ...... 152 6.12.1 Functionality common to all panels...... 153 6.12.2 Search ...... 156 6.12.3 User List ...... 158 6.12.4 Favorites...... 159 6.12.5 Collection ...... 161 6.12.6 Trends...... 163 6.13 WordPress...... 170 6.14 Yahoo Finance Historical Data ...... 171 6.15 Yahoo Finance Quotes...... 171 6.16 YouTube ...... 172

6 Vizrt Feed Streamer User Guide - Version 1.5

7 Working with the Chrome Extension for Feed Streamer ...... 173 7.1 Accessing the context menu ...... 173 7.2 Copy to clipboard ...... 174 7.3 Add to Source ...... 174 7.4 Add to Group ...... 175 7.5 Group and Source Defaults...... 175

8 Working with External Viz Applications ...... 177 8.1 Working in Viz Trio ...... 177 8.1.1 Workflow ...... 177 8.1.2 Feed Streamer External Moderation Dialog...... 178 8.1.3 Paste clipboard message from the Feed Streamer Chrome extension into a Viz Trio page ...... 178 8.2 Working with Viz Multichannel ...... 179 8.2.1 Channels ...... 179 8.3 Working with Viz Pilot ...... 180 8.3.1 Feed Browser and Feed Linker...... 180 8.3.2 Using the Moderation Tool in Viz Template Wizard ...... 180 8.3.3 Using Update Service ...... 183 8.4 Working with Severe Weather plugins...... 184 8.4.1 Configuring and setting up sources ...... 185 8.4.2 Severe Weather integration with Feed Streamer...... 185 8.4.3 To install the Weather Feed Streamer Plugins ...... 186 8.4.4 Adding and configuring Viz Weather Feed Streamer sources ...... 187 8.4.5 Viz Weather Workflow ...... 195 8.5 Working with Viz Weather ...... 196 8.6 Working with Viz Ticker ...... 196

9 Third Party Integrations ...... 198 9.1 Activating a Custom Integration ...... 198 9.2 Applicaster ...... 199 9.3 BumeBox ...... 199 9.4 Excitem...... 200 9.5 Facebook Signal ...... 201 9.6 Flowics...... 201 9.7 Monterosa feeds ...... 201 9.8 Never.No...... 202

7 Vizrt Feed Streamer User Guide - Version 1.5

9.9 SAM Desk...... 202 9.10 Spredfast ...... 203 9.11 Tagboard ...... 204 9.12 Telescope ...... 205 9.13 Twitter Curator ...... 205 9.14 Wayin...... 205 9.15 Wochit ...... 206 9.16 NewsAPI...... 206 9.17 Tintup...... 206

10 Defining Custom Readers ...... 208 10.1 How to Define a Custom Reader...... 209 10.1.1 Understanding Requests ...... 210 10.1.2 Understanding Responses...... 212 10.1.3 Including Media Objects in Feed Streamer Atom Entries ...... 216 10.1.4 Including Geolocation in Feed Streamer Atom Entries...... 217 10.1.5 Including VDF payloads in Feed Streamer Atom Entries ...... 218 10.1.6 Reading JSON Feeds...... 218 10.1.7 Template Switching ...... 221 10.1.8 Define Different Roots per Template ...... 223 10.1.9 Concatenating Selected Nodes ...... 223 10.1.10 Reflecting Feeds ...... 224 10.1.11 Calculating Percentages for Concatenated Selected Nodes ...... 225 10.1.12 Using the Value of a Parameter on Other Parameters ...... 227 10.1.13 Basic Authentication ...... 228 10.1.14 Removing Expired Messages ...... 228 10.1.15 Grouping Sources ...... 229 10.2 The Configuration File Format...... 229 10.2.1 Overview...... 230 10.2.2 Caption...... 231 10.2.3 DateFormat...... 231 10.2.4 Entry...... 232 10.2.5 Image ...... 233 10.2.6 InitialReadLimit...... 233 10.2.7 Name...... 233 10.2.8 NameSpaces ...... 234 10.2.9 Option ...... 235 10.2.10 Options ...... 235 10.2.11 Parameter ...... 236 10.2.12 Parameters ...... 237

8 Vizrt Feed Streamer User Guide - Version 1.5

10.2.13 Reader...... 237 10.2.14 RefreshRate ...... 238 10.2.15 ReaderTypes...... 238 10.2.16 Response...... 239 10.2.17 Root ...... 239 10.2.18 Template ...... 239 10.2.19 Templates...... 240 10.2.20 Url ...... 241 10.2.21 Value ...... 241

11 Social TV REST API ...... 242 11.1 Sources...... 242 11.1.1 URL...... 242 11.1.2 Delete a source...... 243 11.2 Groups...... 243 11.2.1 URL...... 243 11.2.2 Delete a group...... 243 11.3 Messages...... 244 11.3.1 Message Information ...... 244 11.3.2 Read group messages...... 245 11.3.3 Read source messages...... 245 11.3.4 Search messages ...... 245 11.3.5 Associate message(s) to a group...... 246 11.3.6 Associate message(s) to a group in a certain order ...... 246 11.3.7 Unassociate message(s) from a group...... 247 11.3.8 (Un)marking message(s) as Favorite/Approved/Rejected ...... 247 11.4 Spaces ...... 247 11.4.1 URL...... 247 11.4.2 Delete a space ...... 248 11.4.3 Read space groups ...... 248 11.4.4 Read space sources ...... 248 11.4.5 (Un)Associate source to a space...... 248 11.4.6 (Un)Associate group to a space ...... 249 11.5 Pagination...... 249

12 Scene Design ...... 250 12.1 Standard Field Identifiers ...... 250 12.2 Scene Design Examples...... 251 12.3 Scene Design for Trio...... 251 12.3.1 Scene Presenting a Single Message ...... 251 12.3.2 Scene Presenting Multiple Messages ...... 252

9 Vizrt Feed Streamer User Guide - Version 1.5

12.3.3 Accessing VDF Payload Data ...... 253 12.4 Scene Design for Ticker ...... 256 12.5 Social TV Viz Plugins ...... 256 12.5.1 Common Properties ...... 256 12.5.2 STV_GroupsReader ...... 257 12.5.3 STV_HttpRecognizer ...... 259 12.5.4 STV_MessagesReader...... 260 12.5.5 STV_PlaylistsReader ...... 266 12.5.6 STV_SourcesEditor ...... 270 12.5.7 STV_SourcesReader...... 273 12.5.8 STV_SplitAuthor...... 276 12.5.9 STV_TextHighlight ...... 277 12.5.10 STV_WordCloud ...... 280 12.5.11 VLC plugin...... 282 12.6 Control Plugins ...... 283

13 Troubleshooting ...... 284 13.1 Troubleshooting Tips...... 284 13.1.1 Data Hub installation freezes for a long time ...... 284 13.1.2 Cannot connect to Data Hub, or can’t see data in Feed Streamer...... 285 13.1.3 Feed Streamer is slow or unsuccessful when fetching images...... 285 13.1.4 New messages stop arriving ...... 285 13.1.5 No messages ever arrived ...... 286 13.1.6 When using STV_MessagesReader plugin, I cannot see the thumbnails...... 286 13.1.7 Feed Streamer and Data Hub run, and can define sources, but no messages arrive ..286 13.1.8 Cannot login to Facebook, Instagram and Twitter on a Windows Server 2008 machine.2 86 13.1.9 I modified my plugin config file and cannot get new messages or add sources ...... 286 13.1.10 Search on Moderation Panel using special characters doesn’t return expected results.28 7 13.1.11 Cannot create Trio pages...... 287 13.1.12 Data Hub service crashed and no space left on C drive...... 287 13.1.13 Database file getting large and filling hard drive space ...... 287 13.1.14 Cannot add Twitter account (the IE window doesn’t appear)...... 288 13.1.15 Media files not saving in configured folder...... 288 13.1.16 Pusher service not starting...... 288 13.1.17 Ticker Feed Service does not install ...... 288 13.2 Known Limitations ...... 290

10 Vizrt Feed Streamer User Guide - 1.5

1 Introduction

Feed Streamer is an easy-to-use software application that processes information from the Internet, including social media, weather, traffic and financial content from Web Sites, and makes it available for broadcast. Broadcasters can easily integrate any source of online information, allowing them to transform a chaotic flood of data into coherent, visually-compelling broadcasts. Using Feed Streamer, content can be captured from many sources, including Twitter, Facebook, Flickr, YouTube, Instagram, Weibo and Tudou as well as third-party partners such Never.no and Spredfast. In addition, Feed Streamer can be easily configured to capture content from any Internet service that publishes feeds in RSS, Atom or most XML- or JSON-based formats. Using the Feed Streamer, users can easily: • Define searches to select content related to specific subjects from a variety of social services • Moderate the incoming streams of messages • Merge approved messages into a single group or multiple groups intended for different outputs • Push the various streams to Viz Ticker or Viz Trio for on-air presentation • Moderate items from within Viz Trio • Merge captured content with Viz scenes Feed Streamer’s streamlined, logical user interface puts the journalist in full control of what content is selected, and where it is broadcast. The sources of online data and information are in a state of constant flux, with new services appearing almost every day. It is impossible for a single, static application to meet all possible

requirements, both present and future. Feed Streamer therefore includes several different customization mechanisms: • XML configuration files that let you capture content from almost any XML- or JSON-based feed • An HTTP REST API for integrating data aggregated by Feed Streamer • A .NET SDK for creating your own Feed Streamer plugins to meet highly specialized requirements. This section contains information on the following topics:

• Feed Streamer Components • Related Documents • Customer Feedback and Suggestions • Customer Support Request

1.1 Feed Streamer Components

The components of the Social TV solution are: 1. Data Hub: This is where captured data and content is stored ready for broadcast.

2. Social TV Server: This contains the Data Pusher service, which is responsible for bringing the data that the Feed Streamer clients request, and the Ticker Feed Service which is responsible for synchronizing messages from a social feed to a Viz Ticker carousel. 3. Feed Streamer Client: This package consists of three parts, as follows. • Feed Streamer for moderating content • The Social Ticker Controller web application, monitoring and editing synchronization between a DataHub and a Viz Ticker system. • The Feed Streamer External Moderation dialog for Viz Trio. • Scripting library to use External Moderation from Viz Pilot 4. Social TV Plugins: (STV Plugins) This package contains a set of Viz plugins that can be used to incorporate Social TV content into scene designs.

1.2 Related Documents • Viz Artist User’s Guide: Contains information on how to create graphics scenes in Viz Artist. • Viz Engine Administrator’s Guide: Contains information on how to install the Viz Engine software and supported hardware. • Viz Ticker User’s Guide: How to install, configure and use the Viz Ticker client, and configure the output channels. • Viz Trio User’s Guide: How to install, configure and use the Viz Trio client, and configure the output channels. • Viz Pilot User’s Guide: How to install, configure and use Viz Pilot. • Viz Multichannel User’s Guide: How to install, configure and use Viz Multichannel.

1.3 Customer Feedback And Suggestions We encourage suggestions and feedback about our products and documentation. To give feedback and, or suggestions, please identify your local Vizrt customer support team at www.vizrt.com. 1. Click on Contact (top of the page). 2. The Vizrt office which is nearest to your location will be shown, or select from the list of Vizrt offices. 3. Click on the Contact button for the office you want. 4. Complete the required details in the window that opens.

 Note:

If this message is for Customer Support, and there is a Support Contract in place, then click on the ‘For support requests, please visit our support portal’ link in the message window.

A Vizrt representative will contact you as soon as possible.

1.4 Customer Support Request Support Requests are supported by Vizrt if customers have a valid Service Agreement in operation. Customers who do not have a Service Agreement and would like to set up a Service Agreement should contact their regional sales representative (see Customer Feedback and Suggestions). When submitting a Support Request relevant and correct information should be given to Vizrt Support, to make sure that Vizrt Support can give the quickest and best solution to your Support Request. This section contains information on the following topics: • Before Submitting a Support Request • Submitting a Support Request • System Log Files

1.4.1 Before Submitting a Support Request Before a Support Request is submitted make sure that you:

Read: • The relevant User Guide or Guides (see Related Documents). • The release notes. and Check: • That the system is configured correctly. • That you have the specified hardware, tested and recommended versions Always refer to your Vizrt Service Level Agreement document.

1.4.2 Submitting a Support Request When completing a Support Request, add as much information as possible. This section contains information on the following topics: • Content of a Support Request • To submit a Support Request • Obtain windows event logs in case of application crash

Content of a Support Request The report should contain information about these topics: • Problem description: Include a good description of what the problem is and how to reproduce it. Remember to use simple English. • Screen shots and illustrations: Use to simplify the message. • System log files: Send the System Log Files.

• System Config file: Send the system config file (e.g. Viz Artist program folder ).

 Note:

If the operating system is Windows 7 and up, the config file can be stored at: \AppData\Local\VirtualStore\ (check user rights).

• Software configuration: Add exact versions of software (-build) used. • Hardware configuration: Add exact versions of hardware used. • System setup: Describe differences in the installation, if any, from the recommended setup. • System Network: Add a description of how the network, bandwidth, routers, and switches are configured. Always refer to your Vizrt Service Level Agreement document.

To submit a Support Request 1. On the www.vizrt.com page, click on Support. 2. Click on Report a case. 3. Click on LOG IN to login to the Customer and Partner portal. 4. At the top of the Case Management page, click on Report a Case. 5. In the online form complete the required minimum information (shown by a red asterisk) and click SAVE. 6. In the saved Support Case that opens, complete the various text boxes and upload any required documents, files, etc. (see Content of a Support Request). To track the status of open support tickets, login to the Customer and Partner portal. Add information or communicate about the cases directly with the support team.

Obtain windows event logs in case of application crash To obtain windows event logs, open Windows Event Log (event viewer), search for the recent events related to datahub, Feed Streamer and .Net. Copy relevant data from the lower tab. Open a CRM case or send it to Vizrt support.

1.4.3 System Log Files Feed Streamer and Data Analytics:

C:\ProgramData\Vizrt\Logs\VizSocialize

Data Hub:

C:\ProgramData\Vizrt\Logs\VizDataHub

2 Requirements Viz Social TV 1.5 consists of a set of components that works together: • Feed Streamer Client 1.5 • Feed Streamer Server 1.5 • Data Pusher 1.5 • Ticker Feed Service 1.5 These components cannot be mixed with previous versions. Viz Social TV components use external Vizrt software. The following versions are minimum versions for Social TV 1.5: • Viz Ticker 2.5 • Media Sequencer 1.23 • Viz Engine 3.7 • Trio 2.12 • Viz Pilot 8.0 In case of Viz Ticker, 2.5 is the minimum version. Previous version will not work. In the other products, older versions may work, but we recommend the versions above, or higher. The Feed Streamer infrastructure is flexible and expandable. It can be installed in many different configurations and integrated in many different ways with other Vizrt systems and components. The requirements are therefore to a large degree dependent upon the particular configurations and integrations you select. Bearing that in mind, the following sections describe the basic hardware and software requirements for the system installation packages: • Data Hub and Feed Streamer Server Requirements • Feed Streamer Client Requirements • Social TV Plugin Requirements • Upgrading • Product Notifications

2.1 Data Hub And Feed Streamer Server Requirements The Data Hub and Social TV Server should be installed on the same machine. The machine must have internet access (either direct or via proxy). This section contains information on the following topics: • Hardware • Software

2.1.1 Hardware Minor installations require: • Any PC (capable of running Windows 7 or 8) • Any network card

• 16GB RAM Major installations also require:

• SSD drive with at least 0.5 TB available for data, and ~40 GB for a separate OS partition

2.1.2 Software • Windows 7 or 8 64-bit (for a minor installation) • Windows 2008 Server SP2 64-bit or 2012 Server (for a major installation) • Microsoft .NET Framework 4.5.2 • Oracle Java Runtime Environment 8 64-bit or later • Microsoft Visual C++ 2010 Redistributable Package (x86) (http://www.microsoft.com/en\- us/download/default.aspx ) In addition, for a major installation:

• Antivirus SW without endpoint protection • No other SW installed alongside the Data Hub and Social TV server

 Note:

Social TV Server was tested and works best with the Windows 7 64-bit operating system or Windows Server 2008 or newer.

2.2 Feed Streamer Client Requirements The Feed Streamer Client needs to be able to access the internet (either direct or via proxy). The Feed Streamer can be enabled to use a proxy to access the internet, for more information see Feed Streamer Shared and Local Settings.

2.2.1 Hardware • Any PC (capable of running Windows 7 or 8) • Any network card • 8GB RAM

2.2.2 Software • Windows 7 or 8 • Microsoft .NET Framework 4.5.2 • IE 8 or above (for Feed Streamer) • Media Sequencer 1.23 or above

 Note:

Social TV Client was tested and works best with the Windows 7 64-bit operating system but can also be used with Windows 7 32-bit.

2.3 Social TV Plugin Requirements The Social TV Plugins can only be installed on a machine where Viz Artist and/or Viz Engine is already installed.

2.3.1 Hardware • No additional requirements beyond those imposed by Viz Artist/Viz Engine

2.3.2 Software • Viz Engine/Artist 3.8 or above • DataPool 2.13.2 or above • Viz Trio 2.12 or above • Viz Ticker 2.5 or above • Media Sequencer 1.23 or above

2.4 Upgrading

2.4.1 Clean upgrade If upgrading from a previous version, the installer will automatically uninstall existing software components and install the new version.

2.4.2 Migrating data when upgrading You must run the installers without removing previous versions when data migration is expected. By data is meant items (media such as videos, photos and audio) from sources, filters and source and group lists, among other things. The data will be detected, allowing the data migration to be carried out.

2.5 Product Notifications

The product notification icon is located in the top-right corner of the user interface, above the moderated list. The red circle indicates a new notification. Clicking the product notification icon opens an external feed in a browser. Information in the feed may be related to bug fixes or tips on how to operate the Social TV solution.

3 Installation The Feed Streamer installation consists of several installers. The installers are bundled into a Server package and a Client package. The Server package basically contains everything you need to run a SocialTV solution, including the client.

 IMPORTANT! Version 1.5 contains breaking changes on how the Pusher, DataHub, the Viz Ticker feeder and the client works together. When upgrading to version 1.5, both the server parts and the client needs to be upgraded at the same time.

3.1 There Are Two Main Installers: Vizrt.FeedStreamer.Server-x.x.x.xxxx.exe – includes a Viz Data Hub installation, Ticker Feed Service, Feed Streamer Server (Data Pusher) and Feed Streamer Client (Feed Streamer). Vizrt.FeedStreamer.Client-x.x.x.xxxx.exe – includes the Feed Streamer Client. The Social TV Viz Plugins remain as separate installers (a 64-bit version and a 32-bit version) and should be installed on all machines running Viz Engine/Artist. This section contains the following topics: • Installation Recommendations • Feed Streamer Server and Data Hub Installation • Feed Streamer Client Installation • Installing the Social TV Viz Plugins • Installing Individual Software Packages • Installing the Chrome Extension for Feed Streamer

3.2 Installation Recommendations The packages can be installed in various ways according to the following recommendations. You can install all the packages on one machine, or install them all on different machines in your network. In practice, however, these are the principles that should govern where you install the various packages: 1. A standard installation consists of one Data Hub installation, one Feed Streamer server installation, and many Feed Streamer client installations 2. All machines on which the Feed Streamer server and client are installed must have an Internet connection, either directly or via proxy. 3. It is required, that the Data Hub and Feed Streamer Server packages are installed on the same machine, including the Ticker Feed Service. 4. You can install the Feed Streamer client package on any machine(s). They do not need to be in the same LAN as the Feed Streamer server, but clients need to be able to access the server through HTTP.

5. The Feed Streamer External Moderation dialog can either run from the FeedStreamer installed folder or from a network copy of that folder.This may be the case for clients with many seats want to avoid repetitive installations/upgrades. 6. The Social TV Plugins must be installed on machines where Viz Artist and/or Viz Engine is installed.

3.3 Feed Streamer Server And Data Hub Installation This installer will install all software components required for running a Server machine. The installer checks the machine for installations of previous versions, removes them and installs the new software components. This section contains information on the following topics: • Clean installation • Upgrade from previous versions

3.3.1 Clean installation • Run the installation file Vizrt.FeedStreamer.Server-x.x.x.xxxx.exe. The installer dialog will open

• Configure the required parameters • Installing Viz Feed Streamer Client is optional. Check this check box if using the server machine for moderation. • Installing the Viz Ticker Feed Service is optional. Check this check box if you plan to synchronize between a social source and a Viz Ticker system. • Click Install.

3.3.2 Upgrade from previous versions • Run the installation file Vizrt.FeedStreamer.Server-x.x.x.xxxx.exe. The installer dialog will open.

• The installer will display information about the software installed on the machine before removing it • If a database with version 1.2 schema is detected, the installer will automatically upgrade the existing database to 1.3 schema and import the sources, groups and messages (default) • De-select the ‘Upgrade existing database’ and ‘Include Messages’ options to create a fresh clean database • Set the Viz Data Hub data files path, if required • Set the path to the SSD drive, if available

• Set the Feed Streamer Client installation option, if required. (If a previous client installation was detected, the check box will be selected automatically.) • Note the disk space requirements. If the target disk has less than 500MB free memory, the installer will not start the installation • Click Install

3.4 Feed Streamer Client Installation This installer will install a new version of the Feed Streamer Client. The installer checks the machine for previous version installations, removes them and installs the new software components. After all previous versions are removed, all the remaining files from the Feed Streamer folder are copied to a backup folder under:

C:\Program Files (x86)\vizrt\Viz Feed Streamer\Backup

The backup includes user files and modified files from the original installation. If using custom readers, copy the required files back to the Feed Streamer folder hierarchy. This section includes the following topics: • Clean Installation • Upgrade from Previous Versions

3.4.1 Clean Installation Perform a clean installation of Feed Streamer 1.3: • Run the installation

• The installer dialog will open

• Configure the required parameters, including the Install Location, Datahub Host, Viz Trio MSE and Ticker MSE • Click the link to install the Configuring the Chrome Extension for Feed Streamer • Click Install. The installer will install the Feed Streamer client.

3.4.2 Upgrade from Previous Versions • Run the installation. The installer dialog will open

• The installer will display information about the software installed on the machine before removing it. • If a server with a different version is installed, the installation can not continue until it is removed. This is in order to prevent a version mismatch between the server and client software • Click the uninstall button next to the displayed server version. The server will be uninstalled and the install button will be enabled. • Click Install to continue with the client installation.

3.5 Installing The Social TV Viz Plugins The Social TV Viz Plugins package contains a set of Viz plugins that can be used to incorporate Social TV content into scene designs. The plugins help other applications, especially interactive applications, to access the Data Hub. These plugins are needed for integration with Viz Multichannel, as it is not yet directly integrated with Social TV. Viz Multichannel can then control the plugin, telling it what source or group to read messages from, and the plugin will get the data from Data Hub. The plugins are not required for integration with Viz Trio, Viz Multiplay, Viz Ticker or Viz Pilot. The Social TV Plugins can only be installed on machines where Viz Artist and/or a Viz Engine is already installed.

3.5.1 To install the Social TV Plugins

1. Start the Social TV Plugins installer (SocialTVVizPluginsSetup-version.msi) 2. Select installation folder. Click Next 3. Click Close

 Note:

Note that there are two Social TV installers, a 32 and 64-bit version.

See Also

• Configuring the Chrome Extension for Feed Streamer

4 Configuration Configuring the Feed Streamer solution in its simplest form basically requires you to configure the client machine’s Data Hub connection. This section contains information on the following topics: • Configuring Ports • Configuring the Viz Trio Client • Configuring the Feed Streamer • Configuring the Chrome Extension for Feed Streamer • Configuring the Viz Ticker Feed Service

4.1 Configuring Ports Feed Streamer system components connect with each other via your local network and also require an Internet connection. During the initial configuration of the system, the different communication ports should be enabled in firewalls etc. The following section lists the Feed Streamer system components and the default ports they use. For each component, the steps to modify the port number are described. • DataHub default port: 8089 (HTTP) • CouchDB default port: 5984 (HTTP) • CouchDB Lucene default port: 55984 (HTTP) • Media Sequencer (for Viz Trio and Viz Ticker) default ports: 8580 (HTTP) and 8594 (TCP) • Viz Ticker Feed Service default ports: 8800 (HTTP Web server), 8801 (Peptalk over TCP) and 8802 (Peptalk over WebSocket/HTTP)

4.1.1 Modifying the port number The following section describes how to modify the port number for each of the applications. DataHub (default 8089) • Change: Stop DH service • Modify port in C:\Program Files (x86)\Vizrt\Viz Data Hub\Common.config • Start DH service • Update clients (FS, STV, ...) settings CouchDb (default 5984) • Stop DH service • Stop couchdb-lucene service • Stop CouchDb service • Modify port in C:\Program Files (x86)\Vizrt\Viz Data Hub\VizDataHub.exe.config • Modify port and un-comment in C:\Program Files (x86)\Apache Software Foundation\CouchDB\etc\couchdb\local.ini • Modify port in C:\Apache Software Foundation\couchdb-lucene-0.10.0- f4b092b\conf\couchdb-lucene.ini

• Start CouchDb service • Start CouchDb-lucene service • Start DH service CouchDb-Lucene (default 55984) • Stop couchdb-lucene service • Stop CouchDb service • Modify port in C:\Program Files (x86)\Apache Software Foundation\CouchDB\etc\couchdb\local.ini • Modify port in C:\Apache Software Foundation\couchdb-lucene-0.10.0- f4b092b\conf\couchdb-lucene.ini • Start CouchDb service • Start couchdb-lucene service The Media Sequencer(s) used for Viz Ticker and Viz Trio require: • Port 8580 for HTTP • Port 8594 for TCP Viz Ticker Service (default 8800, 8801 and 8802). These ports cannot be changed in the current version of SocialTV.

4.2 Configuring The Viz Trio Client If the Social TV client package (the Feed Streamer) is installed on the same machine as Viz Trio, then you can display the Feed Streamer External Moderation Dialog within Viz Trio from which it is possible to moderate feeds. Configuration of the Viz Trio client differs slightly between versions. The details are provided below: • Configuring Viz Trio 2.12 and Later • Configuring Viz Trio 2.11 and Earlier

4.2.1 Configuring Viz Trio 2.12 and Later The only configuration required to enable this function is the assignment of a keyboard shortcut for displaying the Feed Streamer External Moderation dialog.

4.2.2 To assign a keyboard shortcut in Viz Trio 1. Start Viz Trio 2. Click Config (upper left) 3. Under the User Interface section select the Keyboard Shortcuts and Macros option 4. Double-click on GUI:show_feed_streamer_moderation in the displayed list of commands 5. Press the key combination you want to assign to the Feed Streamer External Moderation dialog 6. Click OK

4.2.3 Configuring Viz Trio 2.11 and Earlier

 Note: This is only relevant for users of Trio versions 2.11 and earlier.

In addition to assigning a keyboard shortcut (see To assign a keyboard shortcut in Viz Trio), a script macro must be created in Trio. The macro allows the external moderation tool to be opened from within Trio. Create a new script macro in Viz Trio and copy the following code into it (changing the path to "Program Files (x86)" if needed):

Dim Shell Set shell = CreateObject("WScript.Shell") cmd = """C:\Program Files\Vizrt\Viz Feed Streamer\ExternalTrioModeration.exe""" cmd = cmd & " -template " & TrioCmd("page:getpagetemplate") cmd = cmd & " -show " & """" & TrioCmd("show:get_show_name") & """" shell.Run cmd Set shell = Nothing

These instructions are also available in the Feed Streamer installation dialog and in the file:

C:\Program Files (x86)\Vizrt\Viz Feed Streamer\readme.rtf

If Media Sequencer is not running on the same machine as Trio then a -mse [MSE host or ip] parameter can be added to the calling macro. See Also • Feed Streamer Client Installation • Working in Viz Trio

4.3 Configuring The Feed Streamer In many cases, the Feed Streamer requires no configuration. It includes a set of ready-configured plugins for consuming feeds from a number of the most popular social web services such as Facebook and Twitter. The only situations in which any configuration is required are: • You want to set up proxies to be used by the Feed Streamer Client and/or Server, or change the cache location. • You want to gather content from a source that is not covered by the one of the standard plugins, in which case you may want to add your own custom reader configuration • You need to change the host name/IP address settings you entered when installing the Feed Streamer. This section contains information on the following topics:

• Internet Access via Proxy • To install Squid

• Feed Streamer Shared and Local Settings • Shared Settings • Data Hub (Host and Port) • Media Settings • User Settings • Proxy Settings • Local Settings

• Media Caching Settings • Media Item Life Cycle

• Adding Custom Reader Configurations • Changing the Data Hub URI, Trio MSE or Ticker MSE • Command Line Parameters • Configuration Options

• Configuring Data Hub Backup and Load Balancing • Hot Backup • Cold Backup • Load Balancing and Failover

4.3.1 Internet Access via Proxy Feed Streamer must have access to the internet, either directly or via a proxy. If the system administrators do not want to open the whole client machine to the internet directly, and there is no existing proxy server, then a Squid proxy can be set up on the server. Squid is a very powerful tool that can be used in a variety of cases. Therefore, Vizrt recommends that your Squid proxy be set up by a network professional.

 Note: Intensive testing is required of all applications using Data Hub with every setup with Squid.

To install Squid 1. Download Squid from http://sourceforge.net/projects/squidwindowsmsi/ 2. Install Squid on the Data Hub server 3. Configure it to run as a service using the command line:

C:\squid\sbin\squid.exe -i

4. Start Squid via the command line:

net start squid

Alternatively, you can start it from the Windows services list and also configure it to run automatically when the machine starts.

4.3.2 Feed Streamer Shared and Local Settings The Settings window in Feed Streamer, which is opened by clicking Settings in the top menu, contains two windows: Shared Settings and Local Settings.

Shared Settings

The following settings appear in the Shared Settings window: 1. Data Hub (Host and Port) 2. Media Settings 3. User Settings 4. Proxy Settings

Data Hub (Host and Port)

• If the Data Hub connection information is set as part of the program’s shortcut properties, then any changes made in the Settings window will not be stored. In this case, a message appears, warning that changes will not be stored. To change the Data Hub settings, see Changing the Data Hub URI, Trio MSE or Ticker MSE. • If an argument is not provided in the shortcut properties, then the Data Hub host/port are stored in a registry and so changing the setting here can have an effect. To configure: 1. Enter the hostname 2. Enter the Port number 3. Click Connect

 Note:

Click Change to enter a different hostname and port.

Media Settings

The path on a local or network drive where Feed Streamer caches media that has been downloaded (e.g. messages, thumbnails, images, videos). Set a media folder by either creating one during install or in the Settings panel, which requires a restart of Feed Streamer and the Data Pusher service. Also ensure that the media folder is located in a common folder accessible by all clients and servers, for example on a UNC network path or a mapped drive that is mapped on all related machines. For more information about media caching, see Media Caching Settings. By default, media will be displayed as small thumbnails in Feed Streamer, but the larger image will be downloaded and sent to a template on air.

User Settings

Filters selected for every group are unique for different users and are saved and retrieved in two different ways. This section describes how to save and access the same filter from different workstations. Filters selected for every group are unique for different users and are saved and retrieved in two different ways. This section describes how to save and access the same filter from different workstations. • Based on username only: This option allows you to save and retrieve filters from different workstations. All users have a unique account that saves the each user’s settings. This means that the filter would stay the same if you logged in with the same username from two workstations. • Based on user and computer hostname: This option allows you to save and retrieve filters in a fixed workstation. Saved filters cannot be accessed from different workstations even if you are logged in with the same username.

Proxy Settings • Clients Proxy (Host, Username and Password): Defines the proxy settings to be used by all client machines. These settings are stored in the Data Hub and only need to be set once, and will then apply to all clients connecting to the Data Hub. • Pusher Proxy (Host, Username and Password): Defines the proxy settings to be used by the Data Pusher server.

Local Settings The following settings appear in the Local Settings window: 1. Viz Trio MSE • Enter the hostname or IP address of the machine on which the Viz Trio Media Sequencer is installed 2. Viz Ticker MSE • Enter the hostname or IP address of the machine on which the Viz Ticker Media Sequencer is installed 3. Local Client Proxy • Overrides the Proxy settings in Shared settings. This means that a Proxy can be configured once for all FeedStreamer clients, or individually for each FeedStreamer client.

4.3.3 Media Caching Settings Note that Feed Streamer clients should run under a user with sufficient permissions to write into the media caching folder. Other Viz apps using the media such as Viz Engine and Viz Trio should be able to read from this location. For more information see the section below on Media Item Life Cycle. Auto-approved messages Messages set to auto-approve do not download to the media folder by default. The pusher service must be configured in order for auto-approved messages to download. Follow these steps to configure the pusher services to download auto-approved messages • Open View local services

• Right-click the Vizrt DataPusher service and click Properties

• Log in as a different user with enough permissions

 Note:

Alternatively, set auto-approved messages to download by granting the media folder with the least permission.

Media Item Life Cycle The life cycle of media items is as follows: • The media belonging to a message is downloaded when the message is approved or added to a group. • The media is verified when a message/group is being sent to Trio/Ticker or used through the Social TV Plugins. This also applies to author thumbnails. • Media is removed when a message is deleted. Thumbnails are never removed.

4.3.4 Adding Custom Reader Configurations The world of social media is rapidly changing, with new services appearing on a regular basis. There are also many services that are popular only in certain countries or regions. For this reason, the Feed Streamer includes a generic plugin called Vizrt.Socialize.Plugins.XML_JSON that can be used to consume any XML- or JSON-based feed. In order to create a reader for a particular service, you simply add information about the service and how you want to use it to an XML configuration file called Vizrt.Socialize.Plugins.XML_JSON.xml.

Vizrt.Socialize.Plugins.XML_JSON.xml can be found in the plugins folder of your Feed Streamer installation:

• Windows 64-bit: C:\Program Files\vizrt\Viz Feed Streamer\Plugins • Windows 32-bit: C:\Program Files(x86)\vizrt\Viz Feed Streamer\Plugins The reader configurations defined in this file are used by the Feed Streamer server as well as by Feed Streamer clients: any changes you make should be made on all Feed Streamer clients and on the server installation. So if you modify this file you must copy it to your Feed Streamer server installation and to all the other Feed Streamer clients that use the same server.

 Note: After copying your modified Vizrt.Socialize.Plugins.XML_JSON.xml to all the required installations, you must restart the Data Pusher service. The Data Pusher service is part of the Social TV Server installation.

On a server installation, Vizrt.Socialize.Plugins.XML_JSON.xml can be found in the plugins folder of the Social TV server installation:

• Windows 64-bit: C:\Program Files \vizrt\Viz Social TV\Plugins • Windows 32-bit: C:\Program Files(x86)\vizrt\Viz Social TV\Plugins For information on how to create custom feed readers by editing Vizrt.Socialize.Plugins.XML_JSON.xml, see Defining Custom Readers. See Also • Third Party Integrations

4.3.5 Changing the Data Hub URI, Trio MSE or Ticker MSE During installation of the Social TV Client package, you can set the following values: • Data Hub URI: The URI of the Data Hub • Ticker MediaSequencer Hostname/IP: The hostname or IP address of the machine on which the Viz Ticker Media Sequencer is installed • Trio MediaSequencer Hostname/IP: The hostname or IP address of the machine on which the Viz Trio Media Sequencer is installed These values are used to set parameters in the startup commands executed by the *Feed

Streamer *desktop shortcut. So if you need to change them all you need to do follow the procedure below.

Command Line Parameters It is possible to set command line parameters when starting the FeedStreamer client. 1. Right-click on the Feed Streamer shortcut 2. Select Properties... from the displayed menu 3. Edit the command line in the Target field 4. Click OK The parameters you can edit in the Target field are: • -DataHubURI: The URI of the Data Hub • -TrioMse: The hostname or IP address of the machine on which the Viz Trio Media Sequencer is installed • -TickerMse: The hostname or IP address of the machine on which the Viz Ticker Media Sequencer is installed • -LogLevel: The amount of logging information in the log file. Possible values: A number from 0-3 where 0 = Debugging, 1 = Information, 2 = Warnings, 3 = Errors. Default is 1 where the log contains Information, Warnings and Errors. For example:

"C:\Program Files (x86)\Vizrt\Viz Feed Streamer\FeedStreamer.exe" -DataHubURI localhost -TrioMse localhost -TickerMse localhost -LogLevel 0

Configuration Options Configure Feed Streamer’s properties either via Feed Streamer’s Settings panel or by defining them in the Feed Streamer shortcut. Settings panel

Shortcut

 Note: Settings defined in the shortcut take precedence over-and are used in place of-settings entered in the Settings window. This allows users running multiple Feed Streamers to connect each Feed Streamer to a different Media Sequencer, among other things.

4.3.6 Configuring Data Hub Backup and Load Balancing Users can configure two types of backup for the Data Hub, and should also consider installing up a load balancing and failover solution. • Hot Backup • Cold Backup • Load Balancing and Failover

Hot Backup Hot backup is achieved with a CouchDb replication feature. Set up a replication of the Data Hub between the main and the backup machine by following the steps in the following sections: • Backup machine • Server (main) machine • During Operation

 Note:

For more information visit http://wiki.apache.org/couchdb/Replication

Backup machine 1. Install the SocialTV server. 2. Stop the Vizrt Viz DataPusher service and disable it. 3. Stop the Vizrt Data Hub, CouchDB Lucene and Apache CouchDB services (in this order). 4. Open the folder "C:\Program Files (x86)\Apache Software Foundation\CouchDb\var\lib" (or the folder containing the DB files if configured differently). 5. Delete the "couchdb" folder (the database folder). 6. Restart Apache CouchDB, CouchDB Lucene and Vizrt Data Hub services (in this order). 7. Run the Data Hub Launcher.

8. Click the Data Hub Launcher icon in the systray (bottom right corner of the screen).

9. Select "Backup Server Mode" (check). 10. Restart the Vizrt Data Hub service.

Server (main) machine 1. Create a batch file in the "C:\Program Files (x86)\Vizrt\Viz FeedStreamer" folder (or edit the existing bat file), containing the replication command. 2. The command must be on a single line. Replace "BackupDatahubHost" with the hostname of the backup Data Hub machine:

{{curl \-s \-S \-X POST http://127.0.0.1:5984/\_replicate}}{{\-d " \ {"""source""":"""viz\_data\_hub\_1\_3\_0""",}}{{"""target""":"""http://192.168.1.107:5984/ viz\_data\_hub\_1\_3\_0""",}}{{"""continuous""":true, """create\_target""":true} "}}{{\-H "Content\- Type: application/json"}}

3. Save and Run the batch file. 4. Add a shortcut to the replication batch file in the Startup folder so that it executes every time the main machine starts.

 Note:

Do not run Feed Streamer on the backup machine. Use the backup machine only if a failure occurred in the main machine.

 Note:

A media folder existing on the same server must be handled separately by other software that will copy the files to the same location on the backup server. Consult your IT responsible person, if required.

During Operation 1. The backup machine should be installed with a full server package to enable faster failover. 2. The server machine should be running at all times.

3. Ensure that the Data Pusher service is not running. Only start it in the event of a system failure when switching to the backup machine.

Cold Backup Cold backup can be achieved by simply copying database files on a regular basis. 1. On the main Data Hub machine, go to:

C:\Program Files (x86)\Apache Software Foundation\CouchDB\var\lib\couchdb

2. Make a copy of the following: a. viz_data_hub.couch file b. .viz_data_hub_design folder 3. On the backup Data Hub machine: a. Paste the files into the corresponding locations on the backup machine

 Note:

Backup is updated to the last copy time of the files.

When using this option neither the Data Hub nor CouchDB services should be running on the backup machine. They should only be started upon failover.For more information see http:// wiki.apache.org/couchdb/How\_to\_make\_filesystem\_backups

Load Balancing and Failover It is possible to setup Data Hub to support failover and load balancing. This can easily be achieved by setting up a failover and load balancing cluster. Squid can be used for this purpose. Squid is a very powerful tool and it can be used in a variety of cases. Therefore Vizrt recommends that your Squid proxy and the DNS failover is set up by a network professional. Also, note that intensive testing of all applications using Data Hub with every setup with Squid is required. See how To install Squid.

4.4 Configuring The Chrome Extension For Feed Streamer Learn to configure the extension in the following sections: • Configuring the DataHub • The Extension’s User Interface • Defining a Default Group and Source

4.4.1 Configuring the DataHub Configure the DataHub connection in the Feed Streamer Chrome extension.

1. Open the Google Chrome browser 2. Click the Feed Streamer Chrome extension icon in the toolbar 3. Click the settings icon to configure DataHub

4. Enter the hostname and port number to configure the DataHub according to the Feed Streamer settings

5. Click Connect 6. The application returns to the home screen. Click the settings icon again to confirm a successful connection, which is indicated by a green checkmark:

 Note:

After successfully configuring the DataHub, head over to the Working with the Chrome Extension for Feed Streamer chapter to learn how to send items to Feed Streamer.

4.4.2 The Extension’s User Interface The extension’s user interface gives you access to the Spaces, Working with Sources and Groups created in the Feed Streamer client. Click the extension icon in Chrome’s extension toolbar to display the extension’s user interface.

The user interface is divided into three panels: Spaces, Sources and Groups. The Spaces drop-down menu lists all the Spaces defined for the Feed Streamer client. Selecting a particular Space will list all its Sources and Groups. If, however, no Space is selected and you select All in the menu, all Sources and Groups will appear in the panels. The Sources panel lists the sources created for the Feed Streamer client. The Groups panel lists the groups created for the Feed Streamer client.

 Note: Clicking a Group or Source will make it the Default. In a set-up where Defaults are not defined, it is still possible to send items to other Sources and Groups not defined as Default. Learn more about Defining a Default Group and Source.

4.4.3 Defining a Default Group and Source Gain quick access to frequently used Sources and Groups by designating them as Default sources and groups. Default sources are the last two parameters (Add to Source and Add to Group) at the bottom of the list in the context menu.

Set default sources 1. Open the extension’s user interface 2. Click a source and a group 3. The selected source and group is labeled Default to confirm the selection In this example, the ATP tennis Source and Sports Group are selected as the default source and default group.

 Note: Default sources and groups can also be set per Space. The default sources and groups that show in the context menu will change depending on the Space selected. See Working with Spaces for more information.

4.5 Configuring The Viz Ticker Feed Service The Vizrt Social TV 1.5 solution introduced a new workflow for sending social messages from DataHub to Viz Ticker carousels. In previous versions, the FeedStreamer client itself did the synchronization between the social sources and a carousel in a Viz Ticker system. In SocialTV 1.5, the ticker feeder mechanism is moved from the FeedStreamer client to a service running on the server. The service is automatically installed and started on same server as the one running DataHub. This service will synchronize approved messages from any source or group on the DataHub, to a ticker in a Media Sequencer running a ticker system. The user interface is web based, which means that any web browser can control and monitor the service. The Ticker Destination panel now contains a button opening the default browser with the URL to the new Social Ticker Controller web application.

 Note: The Viz Ticker Feed Service should be installed and run on the same host as the DataHub, but it can synchronize Tickers on multiple Media Sequencers.

Learn the following: • Install • Run as application • Configure

4.5.1 Install The Viz Ticker Feed Service is bundled with the Feed Streamer Server installer. It contains a JAVA jar file (TickerFeedService.jar) that can be run in a console, and an exe file that can be run as a service (TickerFeedService.exe).

The files are installed to C:\Program Files (x86)\Vizrt\Viz Feed Streamer

4.5.2 Run as application

1. Open a Command Prompt window and change directory to C:\Program Files (x86)\Vizrt\Viz Feed Streamer 2. Start the java service with the command java -jar TickerFeedService.jar

Startup parameters The service has the following startup parameters:

Param Description Default value

-help List the available startup parameters. n/a

Param Description Default value

-filename The file name or full path to where the content C: of the service is persited. \ProgramData\Vizrt\FeedStreamer\ VizTickerFeedService.xml

4.5.3 Configure (expert) The Ticker Feed Service communicates through the same protocol as the Media Sequencer: The Peptalk protocol. This means that the content of the service can be inspected and changed with VdomConfig, which is a tool bundled with the Media Sequencer: 1. Open an internet browser 2. Navigate to http://mse_host:8580/app/vdomconfig/vdomconfig.html 3. In the Server Host field, enter the host name where the Ticker Feed Service runs, and add port 8802:

Under the node mse_entries, there will be one child for each Media Sequencer. Each of these children has a list of updaters, one for each carousel being updated from a DataHub feed. Each updater has an own log, which can be inspected live with VdomConfig.

The content of the Ticker Feed Service is automatically persisted to C: \ProgramData\Vizrt\FeedStreamer\VizTickerFeedService.xml

The log file is written to C:\ProgramData\Vizrt\Logs\VizSocialize

4.5.4 Enabling cached file checking

When the Ticker Feed Service generates elements for a Viz Ticker carousel - it looks for the cache attribute on media elements in the Atom feed entry. If this attribute exists, it contains a file name to a locally cached media file on the Media Folder path. Together, the path and the file name points to a file that should exist in the cache. Per default - there is no explicit file system check whether the cached files actually exist. To enable file checking, open VdomConfig and set the value of the check_cache attribute on each node under the mse_entries node to true:

The Ticker Feed Service will extract the fulle caches file path and insert it into the field in the MSE element. But if the attribute is set to true, the service will also check whether this file actually exist on the local file system - and if not, the original URL to the media file will be used. In this case, the Viz Engine will have to download the resource when the scene containing it is taken to air - and that may take some time, or the original resource could be unavailable.

5 Working With Feed Streamer This section describes how to collect content on a particular subject from a range of online sources, moderate and organize that content and then forward it for playout to Viz Trio and/or Viz Ticker. This section contains information on the following topics: • Feed Streamer Workflow • Working with Sources • Working with Groups • Working with Items • Moderation • Destinations • Top menu navigation • Working with Spaces • Feed Streamer themesFeed Streamer themes • Import/export utility

5.1 Feed Streamer Workflow

The Feed Streamer client allows you to:

1. Define sources.Working with Sources are queries that select items about a subjects you are interested in. These queries retrieve content from, for example, a social media service such as Twitter or Facebook. 2. Add groups (if required). Define your own Working with Groups in addition to the predefined Approved, Rejected and Favorites groups. This lets you classify approved items according to how they are to be broadcast or which show they are to be broadcast with 3. Moderate the items arriving from the sources you have defined. Moderation means to select the items that you consider suitable for broadcast. The data displayed on the Feed Streamer is retrieved by the Data Pusher service, which constantly monitors all the sources you define and generates a stream of items for you to moderate. Your basic choices as a moderator are to: • Approve items that you think are suitable for broadcast. • Reject items that you think are not suitable for broadcast. • Mark items as Favorites. You can mark any items as favorites, even ones you have already approved or rejected - it’s simply a way of highlighting them. You might, for example, want to highlight “difficult” items so that you can discuss them with someone before making the decision to approve or reject them. • Add items to your own custom groups. Adding an item to a user-defined group automatically adds it to the Approved group as well (if it is not already approved) 4. Send content to your Destinations. Send groups of items to air. You can send groups or sources either to Viz Ticker tickers or to Viz Trio shows.

5.2 Working With Sources

The Sources List contains a list of the currently defined sources.

Sources are the various social media websites Feed Streamer gathers information from. Examples of sources include Facebook and Instagram. For a full list of sources that can integrate with Feed Streamer, see the Default Source Types chapter. This section includes information on the following topics • Adding a Source • Enabling/disabling a Source • Modifying a Source • Deleting a Source • Message Limitation • Profanity Filter • Auto-approving Items • Reflect Feed • Grouped Sources • New and total items See Also • Default Source Types

5.2.1 Adding a Source Add a new source. 1. Click the Add new source icon on the right of the panel’s title bar

2. Select a source from the list. Here, Mashable is selected.

 Note:

Each source has different parameters. In the case of Mashable, you must enter a title and select a topic, as detailed in the following steps.

3. Enter the source’s Title

 Note:

Failure to give a title will produce the following error message. A sourcecan notbe created until a title is provided.

4. Select a topic from the drop-down list

5. Optional: Select Reflect Feed and enter the message limitation settings 6. Click Add and Close

7. The newly-created source now appears in the Source List.

 Note:

Some sources such as Instagram and Facebook require the user to login toan account to enable Feed Streamer to retrieve search results within them.

5.2.2 Enabling/disabling a Source Activate or deactivate a source by right-clicking it in the source list or clicking the enable/disable icon, as described below. After a source has been deactivated, the deletion settings - which relate to the maximum number of elements stored and for how long - are also deactivated. Click the gray icon to enable the source and refresh the feed.

 Note: Enabling/disabling a source only prevents the feed from loading new items into the unmoderated window. Enabling/disabling a source does not affect the status of previously moderated or unmoderated content or content loaded into groups.

5.2.3 Deactivate with power icon The power icon appears next to the source name in the source list panel. A source is enabled when the icon is blue, as shown here:

Pause a source’s feed from loading content by clicking the power icon. Once the source is disabled the power icon will turn gray.

5.2.4 Deactivate by right-clicking a source 1. Right-click a source in the source list 2. Select Active in the context menu

3. Click either On to activate a source or Off to deactivate a source.

5.2.5 Modifying a Source

The name and settings of each Source can be edited by clicking the Pencil icon (1) and editing the desired details (2). The context menu, which is presented by right-clicking on a source name, contains options for Editing, Renaming, Deleting, Activating/deactivating and emptying moderated items, described here.

 Note: Sources can also be renamed by clicking a source in the source list and pressing F2.

5.2.6 Deleting a Source Delete a source. Keyboard method

1. Click a source in the source list 2. Press DELETE 3. Click OK. Right-click method

1. Right-click a source in the source list 2. Click Delete from the context menu 3. Click OK. Delete multiple sources 1. Hold down either the SHIFT or CTRL key while selecting multiple sources to delete

2. The selections are highlighted in blue

3. Press the DELETE key or right-click and select Delete from the context menu. 4. Press OK.

 Note:

In a scenario where two Feed Streamers are running off the same server, deleting a source from one Feed Streamer will remove the items from that source in the second Feed Streamer. In this case, the items in the source deleted from the first Feed Streamer are removed from a group or moderation list that appears in the second Feed Streamer. The user is not notified that the items were removed; the moderation list refreshes automatically to reflect the removal of the message.

5.2.7 Message Limitation

Each source has two parameters that control the how many items each source can have and how long they will be stored. A regular automatic cleanup removes the items that are outside these limits. Lifespan (days): Any unmoderated items which have not been changed in this time frame are removed. Changed means that the item has been either moderated, unmoderated or updated from the external feed. Maximum (items): Any unmoderated items exceeding this number will be removed chronologically (from oldest to newest), regardless of their age (see previous parameter). Message limitation has two main benefits: 1. Working with a smaller source is easier because search results are narrower and there is less need for pagination. 2. Limited data size. An unlimited data size means that, over time, the system will get slower as the server hard disk fills up. These parameters can be changed when you add or modify a source.

5.2.8 Profanity Filter

When adding a Twitter or Facebook source, a profanity filter can be enabled. If a message contains unacceptable words, either the entire message can be removed, or the offending words can be hidden and replaced with ***. The list of profanities is stored in the following file:

C:\Program Files (x86)\Vizrt\Viz Feed Streamer\Plugins\profanity.txt

5.2.9 Auto-approving Items Send items directly to the moderated list with the Auto-Approve option. Enable Auto-Approve by clicking the checkbox that appears next to the source’s title when editing a source. Once checked, all new items will skip past the moderation list and appear in the moderated list.

When the Auto-Approve checkbox is clicked the option to Delete old items appears in the lower left corner of the panel. If checked, this option will remove all items that appeared in the unmoderated panel before clicking Auto-Approve. This setting is not specific to Auto-Approve; it appears when any setting in the source edit panel is changed.

 Note: Items from auto-approved sources will only download to the media folder if the pusher service is configured correctly. Click here for more information.

5.2.10 Reflect Feed The items from a source will be synced with the original feed when the Reflect Feed option is enabled. This means that all items removed from the original feed - the feed from the media outlet, i.e. an RSS feed from the BBC - will also be deleted from the moderated and unmoderated lists in Feed Streamer. In this case, approved items will also be removed. Reflect Feed is only available for certain sources. The following applies when Reflect Feed is enabled: • Items in the unmoderated list (Feed Streamer’s left-hand panel) will be ordered according to when they were published in the original feed • Items in the moderated list (the right-hand panel) will be ordered by approval time. A message can be approved by dragging it into a specific order or by pressing Approve, which brings it to the top of the list.

• Auto-approved source items will maintain the same order as in the original source • Manually-approved source items will appear in the moderated panel in the same order as the original source The Reflect Feed toggle button appears in the source edit panel, which is accessed by clicking the pencil icon next to the source name:

 Note: The Deletion Settings (Max items and Lifespan) are unavailable when Reflect Feed is enabled because then the original source determines which items appear in the list and for how long. Any changes they make to the feed will automatically reflect in the Feed Streamer feed.

5.2.11 Grouped Sources Grouped sources are sources that have multiple sub-sources. They appear in the Add New Source list with a bracketed number, indicating how many sub-sources were included in the group. In this example, two sub-sources were grouped under the Spreadfast source. The relevant source can then be selected from the Type drop-down box.

See Also • Sources can also be grouped when creating readers by defining reader groups. Click here for instructions.

5.2.12 New and total items The number of new and total items appears next to the source name in the source list. Here, the ATP tennis source has 2 new message out of a total of 370 items.

A notification also appears at the top of the unmoderated list when a new message arrives. Click the notification to view the item.

5.3 Working With Groups

The Groups List contains a list of the groups to which items can be assigned. The list always includes the default groups Approved, Favorites and Rejected, in addition to the groups you have defined. This section contains information on the following topics: • Add a Group • Modify a Group • Delete a Group

5.3.1 Add a Group

You can add new groups by clicking on the Add (+) button on the right of the panel’s title bar.

5.3.2 Modify a Group Rename a Group by: • Selecting it and pressing the F2 key; or • Right-clicking a Group and selecting Rename in the context menu.

5.3.3 Delete a Group Delete a Group by: • Selecting a Group and pressing the DELETE key; or • Right-clicking a Group and selecting Delete in the context menu.

 Note:

Any existing items belonging to this group will be deleted.

5.3.4 Delete multiple groups 1. Hold down either the SHIFT or CTRL key while selecting multiple groups you wish to delete 2. The selections are highlighted in blue

3. Press the DELETE key or right-click and select Delete from the context menu. 4. Press OK

5.4 Working With Items This section contains the following subsections: • Viewing Items • Delete Items • Previewing Items • Re-order moderated items • Moderate Items • Edit Mode

5.4.1 Viewing Items Items contain the content that arrives into Feed Streamer from the sources. Examples include social media posts, news stories, and other web content. Items appear in Feed Streamer’s moderation panels, typically with the following information:

The numbers in this image correspond to the order of the listed items below.

1. Thumbnail: The source’s logo. 2. Profile photo: The photo that appears next to a source or user’s name 3. Default media: This is a thumbnail placeholder of any media associated with the item. Items can contain three types of media: video, audio, and links. 4. Author: The name, person or entity that posted the item. In the case of a news source, the article author’s name often appears here. For social media websites, this is the handle or username of the individual who made the post. 5. Title bar: Title of the news story or the content in a social media post. Click Expand to see the entire title and Collapse to read the condensed version.

6. Summary: The content associated with an item. This can be the first sentence of a news article or a social media post.

 Note:

When available, geo-location information (latitude and longitude) is also displayed in the summary field. See the Standard Field Identifiers section for more information about using geo-location.

7. Item moderation icons: Click here for more information. 8. Download Media: Click here for more information. 9. Lock: If locked, changes to the item in the original feed do not appear in Feed Streamer, and vice versa. 10. Time: Time when item was published and loaded into Feed Streamer (GMT + timezone offset).

5.4.2 Delete Items Delete any item, both items that are manually-added, from reflection sources (those with Reflect Feed enabled) or items added via the Vizrt Feed Streamer Chrome Extension. 1. Right-click an item in either moderation list 2. Click Delete

3. Click Yes to confirm.

 Note:

Deleting a message will remove it from the system, including its associations with all groups and sources.

5.4.3 Previewing Items Preview images or video in items containing media in both the unmoderated and moderated lists

1. Click the media thumbnail associated with an item

2. The Media Preview window appears showing the selected media

3. Click X to close the window and return to Feed Streamer

Media icons There are three media icons corresponding to each media type that can be associated with an item: video, audio, and links. The icon appears as a translucent element over the thumbnail image of the media in an item in the moderated and unmoderated lists. The video icon

The link icon

The audio icon

 Note: Click here to learn how to upload custom links in Edit Mode.

When an item has multiple media items (two or more) the icon that appears in the item depends on the media combinations associated with it. The following scenarios apply: • The link icon will show in an item with both a link and audio media • The video icon will show in an item with both a video and link media • The video icon will show in an item with both a video and audio media

5.4.4 Re-order moderated items Re-arrange items in the moderated list with the drag-and-drop method.

1. In the moderated list, click and hold an item you want to move

2. Drag it to the desired position and drop it

3. After dropping the item it will appear in the desired position, and other items will adjust accordingly.

 Note:

Re-arranging unmoderated items is not possible because they are sorted by their publish date only. Feed Streamer records the order of moderated items by the order in which they are approved. If that approval order is interrupted by manually moving an item, Feed Streamer will then sort in that order. This means that manual ordering overrides the date of approval for moderated items.

5.4.5 Moderate Items The several ways to move items between the unmoderated and moderated lists are explained in these sections: • Drag and drop items • Moderation icons • Filter Items

Drag and drop items Click an item in one of the lists and drag and drop it into the other list. You can select and drag and drop several items together by hold the SHIFT key and clicking the desired items before dragging and dropping.

Moderation icons

The moderation icons appear on the right side of an item when you point to it with the cursor. The buttons to use are:

• : (in the unmoderated list) moves selected items to the moderated list

• : (in the moderated list) moves selected items to the unmoderated list

 Note:

You can move several items at once by selecting them and then using a button in any one of the items in your selection.

The other buttons displayed on the items have the following purposes:

• : Approve the selected items if they are suitable for broadcast

• : Reject the selected items if they are not suitable for broadcast

• : Mark the selected items as favorites

Filter Items You can filter the items in unmoderated list (left-hand list) of unselected items using the controls displayed at the top of the list.

1. Tagged as: Select items tagged as Approved, Favorites and Rejected 2. From source: Select the required sources from the pull-down menu. Only items from these sources will be listed. 3. In group: Select the required groups from the pull-down menu. Only items in these groups will be listed. 4. Word search: Enter one or more words you are interested in. Only items containing one or more of the words you enter will be listed. 5. Geo-location: Click to determine where the message was sent from. The data is provided in latitude and longitude. Note that this is only available for select sources.

 Note:

Each Feed Streamer user has their own set of persistent filters, which will be retained per group between multiple Feed Streamer sessions.

5.4.6 Edit Mode Edit mode allows you to customize an item’s information, including the author, title and summary as well as any associated media.

This section has the following subsections: • To enter Edit Mode • Edit profile photo • Delete profile photo • Edit default media • Edit the item’s author, title and summary • Uploading links • Edit contributor • Set Geo Location • Add additional fields (payload) • Edit Mode in Grid View

To enter Edit Mode 1. Rest the mouse pointer over an item in either the moderated or unmoderated list

2. Click the pencil icon

3. The item modification icons are replaced with the edit mode frames

4. Click Done to save changes and Cancel to exit Edit Mode

5. Items are locked after editing, meaning they will not be updated. Edited items are also labeled with a gray pencil.

 Note:

Press TAB to switch between frames.

Edit profile photo Edit the profile photo that appears next to the source or user’s name. 1. Click the folder icon in the profile photo

2. Locate the file and click Open

3. The new profile picture is now visible.

 Note:

Clicking the profile photo will open the preview media window, allowing you to view a larger image.

Delete profile photo 1. Hover the mouse pointer over the profile photo

2. Click the garbage bin icon that appears

Edit default media Edit the default media (or thumbnail) associated with an item. 1. In Edit Mode, hover the mouse pointer over the default media photo 2. Three icons appear: Move to Additional Media Fields, Remove Image and Edit Image

a. : Click to move default media to Additional Fields. Click here for more info.

b. : Click to remove the default media

c. : Click to upload a new default media or remove default media

 Note:

In Edit Mode, click the default media thumbnail to preview the media.

Edit the item’s author, title and summary 1. Click the pencil icon to enter Edit Mode

2. Edit the author (1), title (2) and summary(3)

3. Click away from the frame or press TAB to confirm your edit.

Uploading links Upload three kinds of links: Video, Audio and URL link.

Edit contributor Change an item’s thumbnail image (source logo). 1. Enter Edit Mode 2. Click the contributor field

3. Type a source name (from your available sources)

 Note:

Select from a list of sources by clicking drop-drop down menu icon

4. The thumbnail image changes to your match your query.

5. Click away from the field to confirm your selection.

Set Geo Location Set an item’s custom location in terms of geographic coordinates. 1. In Edit Mode, click the Geo Location field

2. Click 3. Type the desired location

4. A list of places generates in the drop-down list. Click the most relevant match.

5. The location’s coordinates now appear in the Geo Location field

 Note:

The latitude and longitude coordinates entered in Edit Mode do not show in items in the moderation lists. They only show when an item’s Edit Mode is open. Some items may contain geographic coordinates that are visible in the moderation lists. These coordinates were embedded in the item by the source from where the item originated, for example, a post from Facebook.

 Note:

Only a place’s geographic coordinates are transferred when sending items to a third party, not the place name itself.

Add additional fields (payload) Add custom metadata to an item. 1. In edit mode, click + Add Field under Additional Fields (Payload) 2. Enter the Field Name and Value for the new field. Here we have added four additional fields and filled out three of them with geographic information.

3. Click Done

Additional Media Fields Add video, audio or images to an item. 1. In Edit Mode, click + Media under Additional Media Fields

2. A new media field appears

 Note:

Click + Media to add multiple media fields.

3. Select media to upload by clicking the folder icon. 4. Select the media and click Open.

5. Optional: Click the check mark/up-arrow icon to send the media the default media field.

 Note:

Additional media fields are not used when creating Viz Trio/Ticker elements.

Edit Mode in Grid View

1. Click the Grid View icon above the unmoderated list 2. Click an item’s pencil icon to enter Edit Mode 3. Edit Mode opens in a separate window titled New Message Editor 4. Click Done to save changes or Cancel or X to return to Feed Streamer.

5.5 Moderation

The Moderation panel contains two lists - list 1 and list 2 (pictured above): • List 1, the unmoderated list on the left, contains unmoderated items. These are items that have not been approved or added to a group, for example. • List 2, the moderated list on the right, contains moderated items. These are items that have been approved or added to a group.

This section contains information on the following topics: • Add a message to a source or group • Download Media • Moderation by Source • Moderation by Group • Grid View and List View • Copy URI • Empty moderated items • Searching Items

5.5.1 Add a message to a source or group Manually add a message to a source’s unmoderated or moderated list.

 Note: The procedure is almost identical when manually-adding items to groups, with the exception that the + Add Message icon only appears in the moderated list when viewing Groups.

1. Select a source and click + Add Message at the top of either the unmoderated or moderated list

2. Edit Mode opens with blank fields

3. Fill in the desired fields

4. Click Done

 Note:

Click here to learn to customize an item's text and media.

5. The newly-created item appears at the top of the list.

 Note:

Feed Streamer will not remove items manually-added to reflection sources.

5.5.2 Download Media An item will download automatically to a local folder when added to a Group, tagged as Approved or sent to the Feed Streamer with the Chrome extension. To manually download media 1. Select an item in the unmoderated list 2. Click the Download Media icon

3. Once downloaded, the icon will appear with a checkmark

 Note:

Download media for several items by selecting the desired items and clicking the Download Media button for only one of them. Click here to learn more about downloading media.

5.5.3 Moderation by Source Moderation by source refers to a number of actions you can take to organize and view items in a selected source. Moderation options include, among other things, grouping media items as Favorites or Approved, searching for items using keywords and editing item content.

 Note: The panels and icons described in this section appear only when a group in the Source List is selected.

Moderate media items in a source in both moderation panels: • Item moderation icons in the unmoderated list • Item moderation icons in the moderated list

Item moderation icons in the unmoderated list These icons appear next to media items in the unmoderated panel when a source is selected and resting the mouse pointer on an item.

They are defined as follows:

• : Filter results from a source by entering key words. Only items containing one or more of the key words will be listed. See Searching Items.

• : Tag the item as Rejected. This will move it to the Rejected group. • : Tag the item as a Favorite. This will move it to the Favorite group.

• : Click to edit item. See not yet created section on editing items

• : Click Approve to send the media item from the unmoderated to the moderated list. Alternately, drag an item and drop it into the moderated list, as shown here:

• : See Download Media • : If locked, changes to the item in the original feed do not appear in Feed Streamer, and vice versa.

Item moderation icons in the moderated list These icons appear next to media items in the moderated panel when a source is selected and resting the mouse pointer on an item.

They are defined as follows:

• : Filter results from a source by entering key words. Click here for more info. • : Remove the media from the moderated list. Mouse-over the underscore and it turns yellow, indicating the deletion option is available.

• : Tag the item as Rejected. This will move it to the Rejected group. • : Tag the item as a Favorite. This will move it to the Favorite group.

• : Click to edit item. See not yet created section on editing items.

• : This icon confirms that the media has successfully downloaded. • : If locked, changes to the item in the original feed do not appear in Feed Streamer, and vice versa.

5.5.4 Moderation by Group Moderation by group refers to a number of actions you can take to organize and view media items. Moderation allows you to filter items to view content from particular sources or groups. It also entails actions such as removing or favoriting media items. In the image below, the Sports group is selected (1), which makes visible the group moderation panel (3) and moderation action icons for a particular media item (2).

Media items in groups can be moderated in three ways: • Group moderation panel in the unmoderated list • Group moderation icons in the unmoderated list • Group moderation icons in the moderated list

 Note:

The panels and icons described in this section appear only when a group in the Group List is selected.

Group moderation panel in the unmoderated list The moderation panel appears about the unmoderated list of media items when a group is selected.

The various fields in this panel are described as follows: 1. Tagged as: View items tagged as Approved, Favorites or Rejected.

 Note:

Each of these tags is a group. So when Approved is clicked, only items in the Approved group will be listed.

2. From Source: Select the source(s) and their associated media you want to view.

 Note:

The filtered items will appear in the unmoderated list.

3. In Group: Select the group(s) and their associated media you want to view 4. Word Search: Filter results from a group by entering key words. Click here for more info.

5. : Click to filter by geolocation data. Only items with geolocation data are listed.

Group moderation icons in the unmoderated list These icons, which are highlighted in blue below, appear in each media item in the unmoderated list.

The icons are defined as follows:

• : Tag the item as Approved. This will move it to the Approved group.

• : Tag the item as Rejected. This will move it to the Rejected group. • : Tag the item as a Favorite. This will move it to the Favorite group.

• : Click to edit item. See not yet created section on editing items

• : Move the selected item to the moderated list and to the selected group.

 Note:

Add an item to the moderated list with the drag and drop method. Drag and drop multiple items by pressing the CTRL key while clicking on the desired items.

• : See Download Media • : If locked, changes to the item in the original feed do not appear in Feed Streamer, and vice versa.

Group moderation icons in the moderated list These icons, which are highlighted in blue below, appear in each media item in the moderated list.

The icons are defined as follows:

• : Filter results from a group by entering key words. Click here for more info. • : Remove the media from the moderated list. Mouse-over the underscore and it turns yellow, indicating the deletion option is available.

• : Tag the item as Rejected. This will move it to the Rejected group. • : Tag the item as a Favorite. This will move it to the Favorite group.

• : Click to edit item. See not yet created section on editing items

• : See Download Media • : If locked, changes to the item in the original feed do not appear in Feed Streamer, and vice versa.

5.5.5 Grid View and List View Items in the Moderation panel can be viewed in two ways - in List View and Grid View.

Toggling between views • Click the switch views icon next to Moderation button

• In Feed Streamer’s top menu, click View -> Grid View Moderation

List View In List View, media items are stacked on top of each other in both moderation panels. In List View, the most recent item appears at the top of the list.

 Note: List View is Feed Streamer’s default view.

Grid View In Grid View, items in the moderation panels are organized next to each other. Expand the moderation window to increase the number of items that appear on a single line. In Grid View, the most recent item appears farthest left in the top row.

5.5.6 Copy URI

The Copy URI icon is available at the top of each list in the Moderation panel. This button copies the URI of the currently displayed list to the ClipBoard. The URI includes source, filter and sort criteria. In addition, the URI can be used in a web browser to view the raw result as returned by the server. The URI can also be useful for troubleshooting. To copy a URI: 1. Click the URI icon, either in the unmoderated or moderated panel 2. Paste the text, for example: http://localhost:8089/search?q=\-(directory:"/directory/id/urn:uuid: 681c584b-2133-47dc-8863-b0f4b8b4a321") AND +category:Message AND + (category:"Geolocation") AND -(category:"urn:uuid:5e9228b8-eda8-4c44-99f7- c984ddb78314") AND "happy"*&limit=15&sort=\published

5.5.7 Empty moderated items Emptying moderated items moves items from the moderated list back to the unmoderated list.

The procedure for removing moderated items is the same regardless of the group or source they are part of. There are three ways to empty moderated items: • In the moderated panel • In the source list • In the groups list

In the moderated panel The icon for emptying moderated items appears in the top-left corner of the moderated panel. The icon is available when a source is selected from the sources list and also when a group is selected in the groups list. There are three steps for removing items with this icon. Three steps for emptying moderated items 1. Select a group (in this case Tennis) 2. Click the Empty Tennis icon in the moderated panel

3. Click Yes to continue or No to cancel.

 Note:

The name of the icon to empty moderated items in the moderated panel changes depending on which group is selected. If the group Favorites is selected, the icon will

be named Empty Favorites; if the group BBC Top News is selected, the icon will appear as Empty BBC Top News, and so on.

In the source list Empty a source’s approved items (which appear in Feed Streamer’s moderated panel). 1. Right-click a source in the source list 2. Click Empty Approved in the context menu

3. Click Yes to confirm or No to cancel.

 Note:

Any item removed from the Approved list will also be removed from any group it's associated with.

In the groups list Empty a group’s moderated items. 1. Right-click a group in the group list 2. Click Empty Approved in the context menu

3. Click Yes to confirm or No to cancel.

5.5.8 Searching Items The Word Search bar appears in both moderation panels when moderating both Sources and Groups. Entering a word search will retrieve results from the selected source.

Customize your search results with the following search techniques to easily locate your media: • Place the search query in quotation marks to retrieve the exact phrase

 Note:

Search terms without quotation marks will find all words with any distance.

• Use the asterisk () to specific words in a phrase. For example, New will find all phrases starting with ‘New’ • Place an asterisk after the first letters in a search query. For example, New* will find all phrases starting with ‘New’ • Searching with #, & and + will produce the following error:

• The following characters have no effect on search results and do not return an error: @ ! " ' ( ) * , - . / : ; < > = ? [ ] \ ^ _ ` { } | ~

5.6 Destinations

This panel contains the destinations to which you can send approved items, that is, Viz Ticker tickers and Viz Trio Shows. • The TICKER pane contains a button opening the Social Ticker Controller web application. From SocialTV version 1.5 the Ticker pane has been replaced with a web application as a frontend for the Ticker Feed Service running on the DataHub host. • The TRIO pane contains a queue for each of your Trio shows. You can send items to Trio by dragging one of your groups or sources on to the Trio show. Only approved items will be sent when a source is dragged into a destination.

 Note: You can only send groups of items or an entire source to a destination, you cannot send individual items.

This section contains information on the following topics: • Destination - Ticker • Destination - Trio • Live Playout • Media caching buttons in Live Playout • Missing media warning message

5.6.1 Destination - Ticker

The left side of the window contains lists of sources and groups. The number behind each source is the number of approved messages in the source. This is the amount of messages that will go on air in the Ticker system. Each Tab on the right side contains one MSE Ticker host. Each time a FeedStreamer client opens the Ticker destination pane with a different Ticker MSE, a new tab is created. It is possible to add new MSE connections and remove them - by clicking the plus button to the right, or the x button on the tabs. Each tab represents a synchronization between the DataHub, and an MSE. Each row in the Ticker pane represents a ticker carousel. The carousel is divided into two areas: the left side is the ticker queue and the right side reflects the current carousel status in Viz Ticker. This section contains information on the following topics: • Assign Groups to a Ticker • Remove Groups or Sources from a Ticker • Ticker System Controls • Duration • Carousel Maximum Size See Also • Configuring the Viz Ticker Feed Service

Assign Groups to a Ticker You can send items to Ticker by dragging one of your groups or sources onto the ticker queue. Drag the group or source you want to publish onto the required ticker queue.

 Note: The items you add to a ticker queue are only queued and will only appear in the broadcast carousel when you press the Add button.

Click the ticker queue’s Add button to move the items from the queue to the ticker carousel.

 Note: When a group has been Added to a carousel, then any changes that are made to the contents of the group are directly reflected in the broadcast carousel. That is, the Ticker Feed Service keeps adding more items on the carousel as new items are added to the group.

Assuming that the system, program and this particular ticker are all switched ON, the items in your selected group are now displayed in the ticker carousel, and a green activity indicator is displayed above the ticker queue. If the ticker carousel was already displaying items, the new group of items replaces the old items. The green lamp will flash when the Ticker Feed Service is updating carousel elements from the feed.

 Note: When assigning a group to a carousel Feed Streamer only supports the use of the default templates from each carousel.

Remove Groups or Sources from a Ticker To remove a group or source from a ticker queue, hold your mouse pointer over the queue and then click on the Delete button that appears. To stop synchronization between a group or source and a ticker carousel, click on the carousel’s Delete button (The garbage bin). The elements in the ticker will then continue running, but the synchronization is off. Dropping a new group or source on a ticker queue replaces the old one, and adding a new group or source to a carousel replaces the old one. All the elements of the existing carousel is deleted and new ones are inserted. The Ticker system will play the existing message to the end, and then continue with the new messages.

Ticker System Controls The TICKER pane contains controls the tickers directly from the Feed Streamer.

You can stop and start the ticker system as a whole (Main), stop and start the Program and stop and start individual ticker carousels. Any custom buttons created in the Viz Ticker Wizard will appear in the TICKER pane as well as in the Viz Ticker client, and work in exactly the same way.

 Note: Feed Streamer only supports the Main Channel.

It is possible to filter what carousels are visible in Feed Streamer by using access groups which are managed from the Ticker application.

 Note: For more information on setting up a ticker or using access groups, see the Viz Ticker User’s Guide.

Duration The Duration parameter defines how long a ticker item will remain on screen before being replaced by the next item. This parameter is only valid for flipping carousels (not scrollers).

Carousel Maximum Size You can set the maximum number of items for each Ticker carousel, where each item is an approved message from the Feed Streamer. By default, the maximum is set to 100. If you drag a group containing more than the specified number of items into the Ticker queue, only the first specified maximum number of items will be sent to Ticker. So if a group containing five items is dragged into the queue with a maximum of three items, only the first three of the five items will be sent to Ticker.

5.6.2 Destination - Trio

You can send items to Trio by dragging one of your groups onto the Trio show.

First, select the required show from the SHOWS drop-down menu, then drag the group you want to publish onto the required Trio template.

To add the pages, click the template’s Add button . Viz Trio pages are now created from the items currently in the group, and are available for the Viz Trio operator to use. This is confirmed by the appearance of a check-mark in the Add button .Updates in the group are not automatically translated to new pages. That means that if the group is updated, and corresponding new pages are needed in Trio, then the Add button must be clicked again. You can drop a group on top of an existing group, the new group replaces the old group. To remove a group from a template, hold your mouse pointer over the template and then click on the Delete button that appears.

 Note: You do not necessarily need to remove groups in this way: dropping a new group or source on a template replaces the old one.

View only Social TV-related Trio templates with the Edit Visible and Hide/Show All toggles.

• Edit visible When checked, the icon to the left of the template becomes visible. When this is checked, the selected template will be hidden from the Feed Streamer interface, indicated by the appearance of the icon. • Hide/Show Allows users to Hide or Show all templates.

 Note:

Depending on whether a certain template is visible or hidden, it either will or will not appear in the list of templates that appear when Live Playout is activated.

5.6.3 Live Playout Live Playout allows you to send items directly from Feed Streamer to on air.

Live Playout has basic operations such as Take/Continue/Take Out. In addition, you can select which template to use and which output channel to trigger the graphic to. Activate Live Playout by clicking a button that appears on top of both moderation lists (unmoderated and moderated).

 Note: All templates are based on Trio shows that are defined in the connected Media Sequencer.

Live Playout has three areas, as shown here:

1. The live playout settings area 2. The area for selecting a default template and enabling live playout

 Note:

This functionality is available in both moderation lists

3. The area for selecting templates and channels and the playout buttons

Live Playout Settings The channels, templates and default templates that show in the Live Playout options for an item are determined by the Live Playout Settings.

The following parameters appear in the Live Playout Settings: • Shows: Choose relevant Viz Trio show • Output Profiles: Select the relevant Viz Trio profile,

 Note:

The Live Playout button is only available if the Trio media sequencer is configured under the settings or part of the shortcut parameters (see Configuring the Feed Streamer).

Selecting a Default Template and Enabling Live Playout

• : The Default Template drop-down is used to select a template that will be used for all items unless manually changing for a particular message

• : Toggle Live Playout on and off. Here, Live Playout is on, indicated by the blue icon in the slider.

Selecting Templates and Channels and the Playout Buttons

• : The templates listed in this drop-down menu are paired with the selected Viz Trio show. Only those templates set to visible under destinations/Trio will appear in this list.

• : A list of all channels that are available on the selected profile

• : The Take button animates the item on air

• : The Continue button continues the animation on air

• : The Take Out button removes the graphic from on-air

5.6.4 Media caching buttons in Live Playout The follow buttons appear when Live Playout is activated. When clicking Take, Feed Streamer will download any media associated with the message if the media has not downloaded. • A disabled button indicates that the media downloaded. This button usually appears in the moderated list as the media has, in most cases, already been manually downloaded in the moderated list. • The enabled button appears when media has not yet been downloaded. It primarily appears in the unmoderated list when media does not automatically download. The following error

message can accompany these kinds of items:

• Click the enabled button to force download the media and the button will transform to disabled indicating that the media is ready. • A red icon indicates that the media did not download. This could appear as a result of a broken link or that no media folder has been defined.

• A yellow warning symbol will appear in the download media icon if a media folder has been created but the download was still unsuccessful. These warning messages accompany messages with templates that do not require the missing media.

5.6.5 Missing media warning message Users are warned when attempting to perform a Take on items with missing media that is required by a template. The error message shown below will appear in such cases. Clicking Take will play out the message without the missing media, for example, a photo or video.

5.7 Top Menu Navigation Various Feed Streamer functionality is included in the top menu for easy accessibility. The menu shortcuts are available under the headings File, View, Settings and Help.

The following options are included under File: • New Source (see Adding a Source) • New Group (see Add a Group) • Edit Spaces (see Working with Spaces) • New Space (see Working with Spaces) • Exit Feed Streamer The following options are included under View: • Moderation (see Moderation) • Grid View Moderation (see Grid View and List View) • Destinations - Ticker - Trio (see Destinations) • View - Style - Carbon - Steel (see Feed Streamer themes) • Users List (see Users List) Click the Settings menu item to access options for configuring Feed Streamer. The following options are included under Help: • Online Manual (Opens the online documentation) • Product News (see Product Notifications) • Chrome Extension (see Installing the Chrome Extension for Feed Streamer) • About (opens the About box)

5.8 Working With Spaces Spaces offer you a way of organizing groups and sources. The main functionality in Spaces involves: • Creating a Space • Adding Sources to Spaces • Adding Groups to Spaces • Viewing Spaces • Adding Sources to Spaces

5.8.1 Creating a Space Create a space.

1. Click the Edit/Add spaces folder icon

2. Click the Add New Space icon (1) in the Spaces dialogue menu. A new space called New Space appears in the Spaces lists

3. Rename the Space 4. Click Enter 5. Click Finish

 Note:

Any changes to a source or group that belongs to more than one space will be reflected in all spaces.

5.8.2 Adding Sources to Spaces Add a source to a space. 1. Click the Edit/Add spaces folder icon

2. In the Spaces dialogue menu, select a space in the source list

3. Select the desired sources (1) from the Available Sources panel. Click (2) the > icon (2) to add the source to the Space

4. The source moves from the Available Sources panel to the Sources in Space panel

 Note:

Click the > icon to send the source back to the Available Sources panel

5. Click Finish

 Note:

The same source can be added to more than one Space.

5.8.3 Adding Groups to Spaces Add a Group to a Space.

1. Click the Edit/Add spaces folder icon

2. In the Spaces dialogue menu, select a space in the source list 3. Select the desired Groups (1) from the Available Groups panel. Click (2) the > icon (2) to add the source to the Space

4. The groups move from the Available Groups panel to the Sources in Group panel

 Note:

Click the > icon to send the groups back to the Available Groups panel

5. Click Finish

 Note:

The same source can be added to more than one Space.

 Note:

Groups must first be created in the Working with Groups panel before they can be added to Spaces.

5.8.4 Viewing Spaces View individual Spaces in the Feed Streamer user interface. 1. Click the Spaces drop-down menu 2. Select a space (in this case Sports)

3. The Sources and Groups lists now show only those sources and groups designated to the Sports space. This Space has an Instagram source called ATP tennis and a group called

Sports.

 Note:

By default, All Spaces is selected, which shows all Groups and Sources created for a particular Feed Streamer client.

5.8.5 Renaming a Space Rename a space. 1. Click the Edit/Add spaces folder icon

2. The spaces dialogue menu appears. Right click the space you want to rename 3. Click Rename 4. Enter the Space’s new name 5. Press Enter

5.9 Feed Streamer Themes Feed streamer can be viewed in two different themes: • The carbon theme, a grey interface, and; • The steel theme, a silver interface.

5.9.1 Selecting a theme 1. Click View in the top menu 2. Click Style in the drop-down menu 3. Click Carbon or Steel 4. The interface will change to the selected theme, and your selection is confirmed with a check mark next to the selected theme in the Style menu item

5.9.2 Carbon theme

5.9.3 Steel theme

5.10 Users List

The Users List provides information on users who accessed the DataHub. Access it by clicking View -> Users List in the Feed Streamer menu. Information displayed in this window includes the name of any user who has accessed the DataHub, the time of their last connection and whether or not they are currently connected.

 Note: A green circle next to the user name indicates users currently connected to the DataHub, while a grey circle indicates no connection to the DataHub.

5.11 Import/Export Utility

This utility tool enables backing up and migrating data in the DataHub between systems. The utility is available a the installation folder of the sever, which by default goes to C:\Program Files (x86)\vizrt\Viz Feed Streamer. It is only available to users after installing the Feed Streamer server.

5.11.1 Export tab When clicking the export button the data base schema will be exported from the DataHub to an XML file. If the 'Export Messages' tab is checked the items, the media items collected by the sources, will be exported as well. • Select or deselect 'Export Messagses'. Click Export. • Select location to save the 'DH_Export.xml' file. • The export process will start.

5.11.2 Import tab Import an XML file containing the Feed Streamer schema and, if applicable, items. Chose to Import Only Missing Data or a Full Import, which will delete the existing database with the data from the XML file to be imported.

 Note: Transferring content and configuration in the event of upgrading from one version of Feed Streamer to another occurs automatically when installing the Feed Streamer server.

6 Default Source Types

The following Source types are bundled with Feed Streamer’s default installation: • Atom • BBC feed • Facebook • Flicker • GeoChart • Instagram • Mashable • RSS • SQL Plugin • TechCrunch • Twitter • WordPress • VizBoldYahoo Finance Historical Data • VizBoldYahoo Finance Quotes • YouTube

6.1 Edit Source Settings Each source contains a small dialogue box for configuring settings. This is where you, among other things, filter data, log in and choose deletion settings. To edit a source’s settings:

1. Hover the mouse pointer over a source in the Source List and a pencil icon appears.

2. Click the pencil to open the dialogue box.

 Note:

The Sources and Readers reside in C:\Program Files (x86)\vizrt\Viz Feed Streamer\Plugins. Additional readers exist in subfolder .../Custom Readers/ For more information, visit the Third Party Integrations section.

See Also • Working with Sources • Modifying a Source

6.2 Atom

Atom: a general Atom feed reader. Result: item per element in feed Source Parameters Feed URL: URL link to Atom feed Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.3 BBC Feed

BBC feed: public feed from the BBC, split by story types. Result: item per element in feed Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

Parameters Feed Kind: select type in dropdown menu

6.4 Facebook

Facebook: search for public posts and pages on Facebook.

 Info: The Facebook plugin has a hard-coded limit of 300 posts into the past.

Xml file: Vizrt.Socialize.Plugins.Facebook.xml This section contains the following subsections:

• To use • Common Parameters • Parameters that are always visible • Page Feed parameters • Q&A Post parameters

• Facebook Polls • Facebook Reactions • Facebook Q&A • Facebook Rate Limit

6.4.1 To use 1. Create a new source by clicking the Add Source button:

2. Enter a title for the source. 3. Log in to a Facebook account by clicking the + Add Account icon:

 Note: Multiple accounts can be added in order to increase the rate limitation stipulated by some providers. Defining multiple accounts will cause Feed Streamer to switch between the accounts when a limit is reached.

6.4.2 Common Parameters

The parameters that are available to the user depend on which tab in the Facebook panel is selected.

Parameters that are always visible • Title: Title of source, identifying the source in the sources list. • Auto-Approve: All incoming posts will be approved if checked. • Add Account: Add an additional Facebook account. • Filter Profanity: Filter items that have words deemed offensive, learn more here. • Remove Message: Posts with profanity will not show in Feed Streamer. • Hide Profanity: Any profanity in the post will be replaced with ‘XXX’.

Page Feed parameters • User or Page Name: Select to receive posts from a particular Facebook user or page. • Include post from: • All: Posts from visitors and the owner of the page. • Users: Only posts from visitors of the page. • Owner: Only posts from the owner of the page.

• Filter by Type: All, one or multiple values: Posts/Links/Photos/Videos • The type of content to retrieve: • Albums: Select an album from the drop-down, showing one item per picture from the selected album. • Reactions: Select a post from the drop-down. The message list will then contain this post with the reactions count of the post (likes, haha, love etc.). • Include comments: If checked, the message list will also contain the comments of the selected post.

Q&A Post parameters

• User or page name: Select to receive posts from a particular Facebook user or page. • Drop down menu: Select from a list of posts. Various post types appear in the list, including videos, photos and links.

6.4.3 Facebook Polls

 Warning. Facebook Polls. This functionality was deprecated by Facebook since 2014. SocialTV no longer support it from version 1.5.

6.4.4 Facebook Reactions

 Warning. Comments to a Facebook post in the Facebook reactions feature will not be shown with author or thumbnail. Facebook has discontinued this information in their API since March 2018.

Gather reactions on a Facebook post. Count the number of Like, Love, Haha, Wow, Sad and Angry reactions a post receives. Choose whether or not to include comments on the post. The reactions count is summarized in the main post. They are also included as additional fields when opening the post (entering edit mode for the message). These numbers can be inspected and edited when editing the post (clicking the pencil icon). After editing, the post will be locked, meaning it will not fetch updates. Unlock the post again by clicking the lock. To add a new Facebook reactions source: 1. Add a new source. 2. Enter a title and a Facebook account. 3. Click Page Feed. 4. Enter the name of Facebook page you want reactions from. 5. Check Filter By Types. 6. Click Reactions. 7. From the dropdown list, select the post to get reactions from.

In Feed Streamer, the post now appears with the reactions count:

Update the reactions count manually by clicking the name of the source in the Sources panel to the left. If you choose to include comments in the source list, a notification appears on the top of the unmoderated panel when there are new comments on the post.

6.4.5 Facebook Q&A Bring one post and its comments into Feed Streamer as a conversation between the commentators of the post. Once brought into Feed Streamer, these elements can be moderated with the Item moderation icons in the unmoderated list. 1. Open the Facebook configuration pane by clicking Facebook’s pencil icon 2. Click the Q&A Post icon 3. Select to receive posts from a particular Facebook user or page 4. From the drop-down list, select the relevant post 5. Click Save 6. The post appears in the unmoderated list, as shown here:

7. The comments and replies to comments appear below the post, with the most recent comments/replies appearing first in the list. Replies to comments are prefaced by A: while

replies to the post are prefaced with Q:.

 Note:

Pictures posted as replies to comments appear as blank in Feed Streamer.

6.4.6 Facebook Rate Limit Facebook does not allow unlimited calls into their API. Each time the DataPusher connects to Facebook and update a source - we use one or two calls to Facebook. Everyone using FeedStreamer connects to Facebook through the same application ID (app) - so the rate limit is common for all users of this software. It means that one user can overload the Facebook API and this will affect all other users. According to Facebook, our app can make 200 calls per hour per user in aggregate. As an example, if our app has 100 users, this means that our app can make 20,000 calls. This isn't a per- user limit, so one user could make 19,000 of those calls and another could make 1,000. This limit is calculated based on the number of calls made in the previous hour.

 Note: To help reduce the risk of hitting the rate limit - you may add more Facebook accounts in the Facebook plugin. All users added will increase the limit.

See also Facebook rate limit (external link)

6.5 Flicker

Flicker: searches for a specific term among images posted on Flicker. Result: item per element in feed Parameters Search Term: enter term in the text box Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.6 GeoChart

GeoChart: Display 3D histogram of message quantities. The resulting display is a grid of 3D square pipes, where each pipe shows the amount of items in each square area. A single snap of these pipes over a map shows the status of items for a certain timestamp. Pipes can be animated if a range of dates shall be displayed over a given area.

To use:

• Provide a title • Enter a Data Hub to connect to • Select a source from all the sources in the selected Data Hub.

 Note:

Only sources with geo-located items work with this feature.

• Select the geo bounding box (left, right, bottom, up represents degrees for west, east, south, north) • Columns: The number of vertical regions the above bounding box should be divided into. This will also determine the amount of pipes that will be displayed (the result of columns with ‘x’ rows determines the number of rectangular areas the bounding box will be divided into) • Frequency: every sec/min/day comprising a format. See RefreshRate. • Period: period to display. See time unit described here.

• From/to: Dates to be displayed in this source.

 Note:

The date range can be defined in the Period text field or in the to/from/ combination.

• Single item: Do not animate the GeoChart, only show latest timestamp. Result: Data in content/payload that can be read by VizWorld GeoChart plugin. Xml file: Vizrt.Socialize.Plugins.GeoChart.xml

6.7 Instagram

Instagram: Retrieve images posted on Instagram. Search by hashtag or by user.

 Info: The Instagram plugin will fetch 140 posts back in time. It will add new posts when they appear.

To use • Log in to an Instagram account (details will be kept on that machine)

• Select hashtag or user search

• Type a term and a drop-down menu of matched terms will appear. Select the item from the generated list. • Select a term from the drop-down menu Multiple accounts can be added in order to work around the Max items limitation stipulated by some providers. Defining multiple accounts will cause Feed Streamer to switch between the accounts when a limit is reached. Result: item per element in feed Xml file: Vizrt.Socialize.Plugins.Instagram.xml

6.8 Mashable

Mashable: Searches among posts from Mashable.com split by story types. To use Select type from the dropdown menu (social media, technology, business, U.S & world, entertainment, video) Result: item per element in feed Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.9 RSS

RSS: RSS (Rich Site Summary) is a format for delivering continuously-changing web content. Many news-related websites, weblogs and other online publishers syndicate their content as an RSS Feed available to the public. To use Type in the feed URL in the textbox. Items are created for each item in the RSS feed.

Result: item per element in feed Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.10 SQL Plugin

SQL plugin: The SQL plugin enables Feed Streamer to fetch information saved on a database system. A common integration is with an Oracle database. The SQL source type is based on SQL queries workings in the same way as XML/JSON feeds. The SQL plugin has two query modes - Basic and Advanced - that offer different methods of accessing a database or data file. Click here to learn how to use these modes. This section covers the following topics: • Connect to a database • SQL Plugin Query Modes

6.10.1 Connect to a database Feed Streamer connects to a database with a connection string. Entering a connection string is required regardless of the query mode you are using to bring data into Feed Streamer. Learn how to connect to a database and configure the connection in these sections: • Connection String • Connection Properties

Connection String

Enter a connection string to establish a direct connection to a database or data file. Enter a connection string in the form:

Provider=;Data Source=;Initial Catalog=;Persist Security Info=True;User ID=;Password=

Connection Properties The connection properties window provides an alternative method of connecting to a database. It is useful if you do not have a database connection string. This section covers the following: • How do I open the Connection Properties window? • What are the options in the Connection Properties window?

How do I open the Connection Properties window? 1. Open the SQL configuration panel. 2. Click the database button.

What are the options in the Connection Properties window? The Connection Properties window contains the following text fields:

1. Data source: Choose the relevant data source to connect to, for example an Oracle database or Microsoft SQL server.

a. Change button: Click to open the Change Data Source configuration window where you can set the relevant data source and data provider.

2. Server name: The database’s location. 3. Log in to the database: Enter the user name an password to connect to the data source, if required. 4. Advanced: Configure initialization, pooling, security and data source settings.

5. Test connection: Test the connection to the database.

6.10.2 SQL Plugin Query Modes The SQL source has two query modes - Basic and Advanced. They offer two different ways to bring database data into Feed Streamer. In Basic Mode, manually select data to bring into Feed Streamer from drop down lists. Advanced Mode lets you select data to bring into Feed Streamer using SQL commands. Learn these modes by clicking the links below: • Basic Query • Advanced Query

Basic Query The options in basic query mode allow you to customize the data brought in to Feed Streamer from an SQL database. A typical workflow is first selecting a database schema, for example a database containing election data. The database may be organized into columns (tables) with each column containing a state’s election results. You then select the relevant column from the table drop down list. The Fields (id, title etc.) correspond to an Edit Mode field. This allows you to add data from columns in the database into a message’s fields in edit mode. How to use the schema and tables drop down lists and the fields parameters are described in more detail below. • How do I select Basic Mode? • What are the Basic Mode parameters?

How do I select Basic Mode? • Click the Basic Mode radio button.

What are the Basic Mode parameters? Read the following parameter descriptions to learn how to customize the data you bring into Feed Streamer from an SQL database.

1. Schema: Select a database schema. The schema structure contains tables, stored procedures, functions and more to organize the data in the database. 2. Table: Choose a specific table belonging to that schema in the database. Each row in a table is a message in the new source. 3. Field: Select which fields to show in the message. The options in the drop-down lists correspond to the columns in the schema. a. In this example, the entry_id column is set for the id field, the Match Day column is selected for the title field and team_id is set for the summary field.

 Note:

Selecting a value from the id drop-down list is required in order bring data from the other fields into Feed Streamer.

b. View data from the selected columns in Edit Mode for a message.

4. Preview Data: Click to open the Database Preview window where you can view all tables in the selected database schema. This is useful if you want an overview of a schema’s content.

5. Add all columns to Additional Fields: Check to add all schema columns to the Additional Fields section in Edit Mode.

Advanced Query In advanced query mode, you can enter valid SQL commands to bring data from a database into Feed Streamer. • How do I select Advanced Query mode? • What are the Advanced Mode options? • Example workflow

How do I select Advanced Query mode? • Click the Advanced Mode radio button.

What are the Advanced Mode options?

• Preview Output: Preview the data before uploading it to Feed Streamer. Click to open the Database Preview window with two text fields: the SQL Query editing window for entering SQL Commands; and the Output Preview pane which shows the data that will be fetched by

those commands.

• Preview Data: Click to open the Database Preview window where you can view all tables in the selected database schema. This is useful if you want an overview of a schema’s content. • SQL Query editing window: Text field for entering SQL commands.

 Note:

This means all database columns will show in the Add additional fields (payload) field in edit mode when Advanced Mode is selected.

Example workflow This scenario outlines bringing data from a database containing ice hockey league statistics into Feed Streamer using SQL commands. The task is to assign data from a schema to populate a message’s various fields in Edit Mode, for example a message’s title, summary, contributor etc. 1. First, preview the database to determine which data to bring in to Feed Streamer:

a. Click Preview Data to preview the data and view the columns where the data is organized.

2. Now use SQL Commands to associate the database column headers with Feed Streamer message fields. a. Preview the data before transferring it into Feed Streamer by clicking Preview Output. b. Enter some SQL commands and click Refresh Output.

c. Click Close.

 Note:

Visit w3schools for a free tutorial on learning the SQL language.

3. In the SQL configuration window, the SQL commands entered in the Preview Output window appear in the SQL Query window.

 Note:

Edit the SQL commands here, if necessary. But remember to move the mouse focus away from the editing window in order for the edits to be recognized.

4. Click Save and check Delete old items to clear previous search results from the unmoderated panel, ensuring messages will only show data retrieved from the latest SQL commands.

5. Select a message in the unmoderated panel and open Edit Mode to view the imported data in the relevant fields.

6.11 TechCrunch

TechCrunch: Using FeedBurner API to get all items related to TechCrunch, split by types. To use Select type in thedropdown menu (general, startups,fundings & exists, social, mobile, gadgets, greentec) Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml Result: item per element

6.12 Twitter

Twitter: Retrieve Twitter items that match the search criteria. Result: An item per tweet in search results.

 Info: Twitter is limited by the API which will only return posts from the last week, up to a certain limit. So If a Twitter user has not tweeted anything in the last week, you will get no posts for that Source.

File: Vizrt.Socialize.Plugins.Twitter.dll (no XML, only a .DLL file) Dialog box

The dialogue box contains five panels for filtering data. Click the following points in the list below to learn how to use the functionality contained in each one. • Functionality common to all panels • Log in • Search • User List • Favorites • Collection • Trends

6.12.1 Functionality common to all panels The following options are always visible on the Twitter dialogue box regardless of the filtering panel selected.

1. Auto-Approve: When checked, items will be sent directly to the moderated list. 2. Update notification: Notification that the Twitter account is updated every second. 3. Remove Re-tweets: Ensures re-tweets are not brought into the unmoderated panel. 4. Deletion: Max sets the max items a source can bring into feed streamer, while the amount of days an item is visible in FeedStreamer is set by Lifespan. If Should affect approved messages is checked, also approved messages will be removed by the deletion criteria. 5. Reflect Feed: When checked, this option will make sure that removals and edits of tweets in the original Twitter source will be reflected in FeedStreamer. NB! If the original list of tweets is long, the reflection mechanism will update one and one page (50 items) in FeedStreamer. 6. Delete old items: If checked, this option will remove all items in the unmoderated panel when clicking Save.

1. Click the + Add Account button

2. Enter your Twitter user name and password.

3. Your twitter profile picture will appear to confirm successful log in.

Add multiple accounts Add multiple accounts to work around the Max items limitation stipulated by some providers. Defining multiple accounts will cause Feed Streamer to switch between the accounts when a limit is reached. 1. Click + Add Account.

2. Follow the steps to add an additional account.

6.12.2 Search

There are six search filters, as outlined below in List of search filters below. Search for data using one or multiple filters. To use: Click the checkbox next to the desired search filter and add details. Here, two search filters are active - Word or #Tag Search and User Search.

List of search filters • Word or #tag search: Type term. Complex queries can be defined using https://twitter.com/ search\-home. Use a word or hash tag search.

• Top trends: Trending tweets for a specific city. Trending tweets appear here after searching for them in the Trends panel. Click Top Trends to change the city, as shown here:

• User search: From, only items from a certain user; to, only items addressed to a specific user (message begins with @user) • Filter By Type:Text only/image/vine video • Filter By Language: Select a language in drop-down menu • Geo Search: Find only tweets that are geo-located (can be used on a map). Use this search option to limit the area to a certain location. • Filter Profanity: Filter items containing words deemed offensive.

6.12.3 User List

Get items from a specific list defined by a certain user. To use: 1. Search for a user, for example CNN. 2. Select the user from the drop-down menu to get all of its lists.

3. Select a list in the drop-down menu.

6.12.4 Favorites

Select a user and get all items that the user marked as favorites.

1. Type a name in the User name text box.

2. Select the item from the generated list.

3. Click Save.

6.12.5 Collection Ingest Twitter Collections (manually-selected collections of tweets).

User name: Type the user you want to retrieve collections from. Select Collection: Select the desired collection from the drop-down list box.

6.12.6 Trends

Search for currently popular hashtags in a specific city. The trends tab allows you to: • Search for trends • Create a source based on trending hashtags

Search for trends 1. Open the Twitter configuration pane by clicking the pencil icon.

2. Click the Trends tab.

3. Enter the desired city in the Top Trends text box.

4. Press ENTER or select the location from the drop-down list.

5. The trending hashtags appear in the dialogue box.

 Note:

The number of tweets containing each hashtag is given below the hashtag.

6. Click Save.

7. The trending tweets for the location now appear in the unmoderated column.

Create a source based on trending hashtags Trending hashtags appear in the search tab under the Word or #Tag Search search filter.

 Note: Search for trends first in order for them to appear in the Search tab.

1. Click the pencil icon to open the Twitter source configuration box.

2. Click the Search tab and click Word or #Tag Search

3. Click the desired hashtag.

4. The hashtag appears in the search box. 5. Click Save.

6. Tweets tagged with #MerylStreep now appear in the unmoderated column.

6.13 WordPress

WordPress: Get content from a WordPress-style feed. Result: item per element in feed Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.14 Yahoo Finance Historical Data

Yahoo Finance Historical Data: Get historical data for stocks from Yahoo Finance API

 WARNING! This plugin has been removed in SocialTV 1.5, as Yahoo has discontinued the historical finance data API.

6.15 Yahoo Finance Quotes

Yahoo Finance Quotes: current stock info To use Select a stock symbol. Multiple symbols can be entered, wrapped with quotes and separated by a comma Search for symbols by visiting https://finance.yahoo.com/lookup Result: Summary of latest stock activity contained in the Summary field. Additional data in the content-payload (Price, Volume, Ask, Bid, Year-low, Year-high, Days-low, Days-high, Open, Previous-close)

Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

6.16 YouTube

YouTube: brings video clips from YouTube. To use Type search string in textbox Result: item per element in feed

Xml file: Vizrt.Socialize.Plugins.XML_JSON.xml

7 Working With The Chrome Extension For Feed Streamer

Add content directly from social media websites to Feed Streamer with the Chrome extension for Feed Streamer. This chapter contains the following sections: • Accessing the context menu • Copy to clipboard • Add to Source • Add to Group • Group and Source Defaults

 Note:

Items sent to the Feed Streamer with the Chrome extension will be downloaded in the same way as approved and associated items.

See Also • Installing the Chrome Extension for Feed Streamer • Configuring the Chrome Extension for Feed Streamer

7.1 Accessing The Context Menu 1. Open any of the supported social media websites (for example Twitter, Facebook or Instagram) 2. Right-click an item on a page’s News Feed

3. Click Vizrt Viz Feed Streamer in the context menu

7.2 Copy To Clipboard Copy the URI of an item to the clipboard and paste into Viz Content Pilot. 1. Right-click an item on a social media website 2. Click Vizrt Viz Feed Streamer -> Copy to clipboard 3. Paste the item’s URI into a Pilot template. For more information, see populating content from the Chrome extension clipboard.

7.3 Add To Source Send an item to a Source. 1. Right-click an item on a social media website 2. Click Vizrt Viz Feed Streamer -> Add to source

3. Select the relevant source in the list

4. The item now appears in Feed Streamer, in the source’s moderated list

 Note:

Click 1 New Message Available notification that appears at the top of each moderation list to view items that do not automatically appear in the lists.

7.4 Add To Group Send an item to a Group. 1. Right-click an item on a social media website 2. Click Vizrt Viz Feed Streamer -> Add to group 3. Select the relevant group in the list

4. The item now appears in Feed Streamer, in the group’s moderated list.

7.5 Group And Source Defaults Send items to a Default Source or Group 1. First, define your default source and group. See Defining a Default Group and Source 2. Right click an item

3. Select the default source and group to send an item to. The default sources and groups appear at the bottom of the context menu

8 Working With External Viz Applications This section describes how to use Feed Streamer to send and moderate data for use in other Viz applications, such as Viz Trio, Viz Multichannel and Viz Pilot. This section contains information on the following topics: • Working in Viz Trio • Working with Viz Multichannel • Working with Viz Pilot • Working with Severe Weather plugins • Working with Viz Weather

8.1 Working In Viz Trio Feed Streamer includes a Viz Trio plugin that lets you moderate feeds directly in Viz Trio instead of using the stand-alone Feed Streamer application. The plugin provides a Feed Streamer External Moderation Dialog that allows you to directly select entries from the Working with Sources defined in the Feed Streamer, and add them to your Viz Trio playlists. You can open the Feed Streamer External Moderation dialog by pressing the keyboard shortcut that has been associated with it (see Configuring the Viz Trio Client). You can then use it to select social media items that you want to add to a playlist. This section contains the following subsections: • Workflow • Feed Streamer External Moderation Dialog • Paste clipboard message from the Feed Streamer Chrome extension into a Viz Trio page

8.1.1 Workflow 1. Start Viz Trio 2. Open your show 3. Import and read the template that has been created for handling social content. Templates are created in Viz Artist and must contain certain tab fields. For more information see Scene Design for Trio. 4. Open the Feed Streamer External Moderation Dialog by pressing the associated keyboard key (see Configuring the Viz Trio Client) 5. Filter Items, if necessary. 6. Paste clipboard message from the Feed Streamer Chrome extension into a Viz Trio page until the right-hand list contains all the items that you want to add to your playlist. 7. Click the Add button to generate pages based on the current template and add them to the Viz Trio page list. The pages are added as a group with the name Feed Streamer. 8. Click OK to close the Feed Streamer External Moderation dialog

8.1.2 Feed Streamer External Moderation Dialog

Moderation in the External Moderation Dialogue, which contains the unmoderated and moderated lists, functions the same way as moderation in Feed Streamer. See Moderate Items for instructions on moving items between the lists and filtering items using the moderation icons.

 Note: Items approved in the External Moderation Tool will also be approved in Feed Streamer.

8.1.3 Paste clipboard message from the Feed Streamer Chrome extension into a Viz Trio page Pasting a message copied to the clipboard from the Feed Streamer Chrome extension into a new Viz Trio page has two steps: • Enabling clipboard interaction • Adding a Script in Trio

Enabling clipboard interaction Steps to enable clipboard interaction: 1. Open the Internet Options menu 2. Click the Security tab 3. Click the Custom Level button 4. Scroll down to Scripting and click Enable

5. Click OK.

Adding a Script in Trio

Add the script located at C:\Program Files (x86)\Vizrt\Common\Social TV\Viz Trio\Trio.vbs and assign it a hotkey: 1. In Viz Trio, click File -> Configuration 2. Under User Interface click Keyboard Shortcuts and Macros 3. Click Add Script 4. Assign a key, name and description as desired 5. Paste the content of the file mentioned above into the script area 6. Click OK.

8.2 Working With Viz Multichannel When working with Viz Multichannel, the Social TV Viz Plugins are used to automate what comes out of the Data Hub and into pages of Multichannel.

8.2.1 Channels The system can work with any number of channels. For example, when working with Viz Multichannel, an operator can create a group of mediated postings, and point them at a template for Channel A, then create a new group and point them over to Channel B.

8.3 Working With Viz Pilot

• Feed Browser and Feed Linker • Using the Moderation Tool in Viz Template Wizard • Using Update Service

8.3.1 Feed Browser and Feed Linker The Feed Linker control can be added to Viz Pilot templates in Template Wizard and is used to define a feed source. When a template with a Feed Linker control is used in Viz Pilot’s Director or Viz Pilot’s Newsroom Component, the Feed Browser window is opened and lists the items from the feed source that was defined in the template. When an entry is selected by the user, the data is mapped to fields in the template. This allows the user to pick an item from a feed and have the corresponding data applied to fields in the template, instead of manually typing in information. The template designer uses scripting to map the feed data to fields in the template. The Feed Linker supports many types of feeds, including those provided by Social TV.

Example URI The following URI links to a list of the Working with Sources defined in Feed Streamer:

http://:8089/directory/title/Socialize/Sources/feed

From this list of sources, you can click to view the individual messages in each source.

 Note: You can get a specific URI from Feed Streamer by using the Copy URI function.

8.3.2 Using the Moderation Tool in Viz Template Wizard Feed Streamer has a helper script that can be used from Viz Template Wizard to launch the external moderation tool. This enables populating template fields with selected items (see the Feed Streamer External Moderation Dialog section for information about using the moderation tool).

• Feed Browser and Feed Linker • Example URI

• Using the Moderation Tool in Viz Template Wizard • Instructions for installing the script • Using the script

• Populating contents from a single message into template fields • Populating content from the Chrome extension clipboard • Update contents of a single message in a template field • Populating contents from multiple messages into a template’s ControlList • Saving filters with contents populating templates

• Using Update Service

Instructions for installing the script The script is available at C:\Program Files\vizrt\Common\Social TV\Viz Template Wizard\STV.vbs. To use the script it must first be added to the scripting repository. On a machine running Viz Template Wizard:

• Copy the script to C:\Users\[user name]\AppData\Local\Vizrt\VCP\Scripts folder • Create a new template, enable scripting, go to script editor, right click and choose "use script unit..." or "open..." • Right-click and select "save to repository".

To update a version of the script: 1. Copy the script to the plugins folder 2. Run Template Wizard and update the script by clicking Yes when prompted

Using the script The script provides two functions that can be used by the template’s script to fill the controls with information from Feed Streamer items. Usage is shown in a basic example where template and scenes can be found at C:\Program Files\vizrt\Common\Social TV\Viz Template Wizard. In order to use the examples, first import the archive into Viz Artist and load the template from file within the Viz Template Wizard.

Populating contents from a single message into template fields FillMessageFromExternalModeration(Form, FieldPrefix) is a function that receives the template form and field prefix as parameters. It will launch the moderation tool and populate the template’s form controls with message fields. The field to control lookup is based either on the control ‘Name’ attribute or ‘ControlObjectName’ attribute. For example, a TTWUnitEdit with Name=title or ControlObjectName=title will be filled with a message title. The FieldPrefix parameter can be used in the event there are multiple controls that should be filled from multiple messages. For example, we might have a text box named ‘msg1title’ and another named ‘msg2title’, and call the function providing ‘msg1’ to populate the first text and call it a second time with ‘msg2’ to populate the second text. The available field names are the same described in the Standard Field Identifiers section of the manual.

 Note: Any number of messages can be selected in the moderation tool, but only the content of the first message will be used to fill the template.

Populating content from the Chrome extension clipboard After installing the Vizrt Viz Feed Streamer Chrome extension, right click messages on social media websites and copy them to the clipboard. This will store the selected message so that it can be used to populate VCP templates. In the template define a button that will populate the template from the clipboard and save the data element.

FillMessageFromClipboard(Form, FieldPrefix) is a function that receives the template form and field prefix as parameters. This will copy the content from the clipboard into the template.

Update contents of a single message in a template field

Use the UpdateMessage function to update a message in a template field by calling the UpdateMessage function and entering the message ID that will be used to populate the fields. Usage:

UpdateMessage Sender, MessageId, ""

 Note: This is an alternative method to update the message that was populated by the External Moderation Tool.

Populating contents from multiple messages into a template’s ControlList FillListFromExternalModeration(ListControl) is a function that receives a TTWTableEditor control and populates its columns with the information of the messages selected in the moderation tool. Note that this control cannot be modified in the template; rather, it is generated by the wizard when creating a new template, and the columns correspond to the tab fields of the ControlList of the scene. Note that any number of messages can be selected in the moderation tool, but only the allowed number by the ControlList will be used to populate the table. It is possible to configure the ControlList to allow any number of rows, and in this case, all selected messages will be used. Please refer to the Viz Artist manual for more information about the ControlList plugin.

Saving filters with contents populating templates Pilot external moderation users can reuse their previously used filter. A specific single message template filter can be remembered and opened from an external moderation tool using the suffix WithFilters. For example, instead of saving a template script called FillmessageFromExternalModeration, save it as FillmessageFromExternalModerationWithFilters.

Similarly, filtering of populating contents from multiple message control lists can be remembered. In this case, the template script must be saved as FillListFromExternalModerationWithFilters instead of FillListFromExternalModeration. The script with these new functions expects an additional argument template name.This value is kept in Viz Pilot reserved word SCV_TemplateName. See Also • Filter Items

8.3.3 Using Update Service To automatically fetch the latest content of a social message from the DataHub before a Media Sequencer Take operation, use the new update service endpoint in DataHub: http://datahub_host:8089/update_service

A good use case is to set up a source in FeedStreamer to a Facebook post, and use the new Facebook reactions feature, which will fetch the number of reactions (likes etc.) to a message, and update the message in DataHub. To ensure that the latest reactions count is taken on air - the Pilot template of the graphics can be configured to use the update service end-point in the DataHub. The data flow is then: • A template is created in Viz Pilot Template Wizard with an External Moderation button. • When this template later is opened in Director, the External Moderation tool selects a post in DataHub and fills in the field with the data at the current time. • Later, the data element based on this template is ready to go on air. But in the meantime, the data may have been changed in the DataHub. Instead of manually opening the element and filling in the latest data, the Media Sequencer will fetch the latest data from the Update Service endpoint in the DataHub. • The data on air will reflect the latest data in the DataHub.

In detail, to enable this functionality for a scene that is played out through the MSE: • The Pilot template of the graphics must contain a field named id. This can be added by adding another TextBox (Unicode Edit) to the template in Template Wizard, and set the ControlObject property to id. This TextBox can be hidden.It is only used to enhance the VDF payload behind the graphics to carry the id of the message to the update service. • An external update service must be configured for the template, by adding a service URL in the "Update Script Editor". This URL points to the new endpoint in DataHub, for instance, http://datahub_host:8089/update_service • The Media Sequencer will on "take" on a Data Element created based on this template, send an HTTP request to the DataHub endpoint with the VDF payload of the element, and the DataHub will replace the values in the payload with the latest data that is pushed to the DataHub from the social source. Adding a field with ControlObject called id:

Configuring this template to use the DataHub as an external update service:

8.4 Working With Severe Weather Plugins Severe Weather is the name of a group of plugins that appear as Feed Streamer sources. Data collected by these sources relates to severe weather conditions such as various weather alerts, LSRs (local storm reports) and lightning alerts. Once collected, Feed Streamer sends the data to Viz Weather where it is displayed. In addition to handling severe weather alerts, Feed Streamer, the underlying data-fetching technology, can be used to integrate Viz Weather with various social media sources. Viz Weather comes with Viz Engine plugins for integrating weather alerts in Viz Artist scenes as well as editors for working with severe weather in the Viz Weather client GUI.

Viz Weather collects and receives severe weather data by integrating with Feed Streamer, a tool for fetching, moderating and organizing both unstructured and structured datasources. Examples of data types Feed Streamer can fetch are weather data, news and RSS feeds and various social media feeds from providers such as Twitter, Facebook, Instagram and many more.

This section contains information on the following topics:

• Configuring and setting up sources • Severe Weather integration with Feed Streamer • To install the Weather Feed Streamer Plugins • Adding and configuring Viz Weather Feed Streamer sources • NWS Warnings • Weather Lightning • Weather LSR • AllisonHouse LSR

• Viz Weather Workflow

8.4.1 Configuring and setting up sources Viz Weather uses Feed Streamer to collect, organize and moderate severe weather data from various Internet sources, including social media. A flexible tool, Feed Streamer can fetch and moderate/organize almost any Internet datasource provided the source has a published API. Feed Streamer comes with many predefined datasources, while Viz Weather provides additional integrations and plugins for fetching severe weather data.

8.4.2 Severe Weather integration with Feed Streamer Dedicated Severe Weather Feed Streamer plugins (readers) were added to Feed Streamer to allow the ingestion of severe weather data. The appropriate datasources must be configured with the Feed Streamer Client to utilize the Feed Streamer severe weather resources (Alerts and Messages). Feed Streamer continuously polls the

source to keep it current after it has been defined and configured. The update is not in real time and depends on network (Internet) speed and other factors. The severe weather sources are created like any other source in Feed Streamer: File - New Source or click the ‘+’ icon to add a new source and then configure the source as indicated in the image below:

8.4.3 To install the Weather Feed Streamer Plugins The Weather plugins for Feed Streamer are the Feed Streamer severe weather sources, for example weather data aggregation source AllisonHouse LSR. To install the plugins: 1. Start the installer (VizWeather-FSPlugins-.msi)

2. Click confirmations and make sure to install the plugins in the directory where Feed Streamer are installed. Unless Feed Streamer is installed in a different directory than standard the default directory suggested should be fine. The Viz Weather Feed Streamer components should now be installed.

8.4.4 Adding and configuring Viz Weather Feed Streamer sources Severe Weather provides plugins for: • Lightning • Alerts (also referred to as Warnings or Watches) • Messages To add data for any of these severe weather message types: 1. Start Feed Streamer Add new datasource using File > Source in the Feed Streamer main menu or click the “+” button in the sources window:

Then add the desired severe weather source types: • NWS Warnings • Weather Lightning • Weather LSR • AllisonHouse LSR

When sources are defined, click the Pencil icon on the source to view and change the source parameters, if applicable.

NWS Warnings

Select Reflect Feed to ensure that the source stays updated and mirrors the incoming feed, which has been filtered according to your selections. Select Auto Approve if using alerts in a ticker because the Ticker integration displays only Approved items. The Regions Filter is a list of regional codes (FIPS codes) of counties and/or states separated by a comma. When defining Alert sources is it possible to define several sources of the same type (NWS Warnings) provided that the sources are saved with different names. This allows for analyzing the data from different angles, for example by region, alert-type and similar.

 Note: The drop-down menu options for the NWS Warnings plugins are configurable and can be changed to reflect user requirements.

The settings for the NWS Warnings are normally located in:

C:\Program Files (x86)\vizrt\Viz Feed Streamer\Plugins as: Vizrt.Weather.FeedStreamerPlugins.NWSAlerts.xml Vizrt.Weather.FeedStreamerPlugins.NWSAlerts.floods.xml

These files provide the settings for the NWS Alerts can be altered by the administrator. Be careful when editing. Always keep a backup. Feed Streamer and the DataPusher service must be restarted after changing the XML settings files in order for the options to be reflected in the UI. Alternatively, restart the machine. Examples:

By modifying EventFilter combo boxes in the XML, users can configure the editors for allowing easy filtering options. The filter result of these editors is defined as the Full feed, filtered by location as selected in state/ regions/dma, and filtered by type as selected in all the Event Filter combo boxes. In the above examples event/floods/winds – related. Leaving drop-down items unselected will result in items not being filtered, and all incoming items will be part of the source.

 Note: Designated Marketing Area (DMA) is a common geographical split targeted for TV advertisers using cable TV marketing. There are 210 DMAs in the United States.

Weather Lightning

Normally, choose “From WDT” (Weather Decision Technology) as the source. For the other options, contact your Vizrt representative. Provide “Bounding Box” LAT/LONG for North, East, South, West for the region of interest you would like to receive data for. In the example above: N=70, E=140, S=-70 and W=-140.

Weather LSR

AllisonHouse LSR

8.4.5 Viz Weather Workflow After defining the desired sources in Feed Streamer, the items of the data source can be displayed in one of the following ways: • Through Viz Weather: For selecting sources and saving them with the data element, and combining the alerts display with the weather show (see Working with Viz Weather).

• Through Viz Ticker: By dragging groups/sources to a Ticker destination placeholder in Feed Streamer.

• Using Social TV plugins in scenes created in Viz Artist. These plugins read the items directly from DataHub. Items are selected by source name, type, group or substring. Useful for interactive scenes and when maximum scene design flexibility is required. For more details, refer to the scene design tutorial.

8.5 Working With Viz Weather Viz Weather collects and receives severe weather data via an integration Feed Streamer. This data becomes available in Viz Weather via three data editors: the Severe Weather Lightning editor, the Severe Weather Alerts editor and the Severe Weather Messages editor. For more information about the Severe Weather editors in Viz Weather, please refer to the ‘Working with Severe Weather editors’ section in the Viz Weather User's Guide. See Also • Viz Pilot User’s Guide for information on the Feed Browser and the Feed Linker control.

8.6 Working With Viz Ticker The Ticker Feed Service is synchronizing between a social source feed on the DataHub and a carousel in a Viz Ticker System.

 Info: The current version of the SocialTV software only supports one Viz Ticker channel called Main.

When a Viz Ticker system is up and running on a Media Sequencer, both scrolling and flipping carousels can be populated automatically from a social source feed. Changes in the feed are reflected in the carousel after a few seconds. See Working with Ticker Destinations to learn more on how to integrate between FeedStreamer and Viz Ticker.

9 Third Party Integrations Feed Steamer has many third-party integrations. This section includes information on each third party provider and the specific information that is required in each case. This section contains information on the following topics: • Applicaster • BumeBox • Excitem • Facebook Signal • Flowics • Monterosa feeds • Never.No • SAM Desk • Spredfast • Tagboard • Telescope • Tintup • Twitter Curator • Wayin • Wochit The following plugins have been discontinued in version 1.5: • BloombergNewsAndPics • BuzzDial • Cambrium • CellJournalist • Microsoft Pulse The following plugins are added in version 1.5: • NewsAPI

9.1 Activating A Custom Integration Some third-party integration files include customer-specific information, such as the subscription of the provider. This info must be configured inside the corresponding plugin file. Existing template integration files (plugins) for each third-party provider can be found under:

C:\Program Files (x86)\Vizrt\Viz Feed Streamer\Plugins\Custom Readers

To activate a particular integration, the specific file should be copied to the /Plugins folder of both the Feedstreamer client and the DataPusher server installation. Both applications are installed on the same path - but the client and the server may be installed on different machines:

C:\Program Files (x86)\Vizrt\Viz Feed Streamer\Plugins\

After placing the file you must restart the Feed Streamer client (on the client machine) and the Viz Data Pusher service on the Data Hub (server) machine.

 Note: Creating new integration files is described in the section Defining Custom Readers

9.2 Applicaster

File name: Vizrt.Socialize.Plugins.XML_JSON.Applicaster.xml Applicaster engages viewers with second screen and companion apps. Mobile application users may answer any quiz/poll/trivia game. The result is provided in a feed from Applicaster. The GUI in Feedstreamer requires the user to enter the full URL to the feed containing the results.

9.3 BumeBox

File name: Vizrt.Socialize.Plugins.XML_JSON.BumeBox.xml BumeBox hosts Q&A events on social media, and provides the results in a feed. You need the BumeBox partner ID and an API key. These must be entered in the dialog box. Then The combo box will be filled with a list of events that belongs to your BumeBox account. Select one event, and the Moderation list in FeedStreamer will be filled with the questions and answers from the event.

9.4 Excitem

Filename: Vizrt.Socialize.Plugins.XML_JSON.Excitem.xml Excitem is a company that engage audience in real time polling and feedback. The result is provided in a feed. To access the data you will need a token from Excitem. Replace the contents of the Value field with the customer’s token in both the Feedbacks and Polls reader in the following file: Vizrt.Socialize.Plugins.XML_JSON.Excitem.xml

{token} textbox (your token)

9.5 Facebook Signal

File name: Vizrt.Socialize.Plugins.XML_JSON.FacebookSignal.xml Journalists use Signal to surface relevant trends, photos, videos and posts from Facebook and Instagram for use in their storytelling and reporting. This integration does not require any additional configuration once activated. The integration includes access to content from collections, all exported metrics and metrics from collections. It is possible to set a default account by replacing the contents of the Value field with the customer's account ID in the following file: Vizrt.Socialize.Plugins.XML_JSON.FacebookSignal.xml

{account} Facebook Account textbox (Signal account name)

9.6 Flowics

File name: Vizrt.Socialize.Plugins.XML_JSON.Flowics.xml Flowics offers feeds of user generated content from a wide range of social sources. The plugin distributed with SocialTV has a demo token exposing feeds with sample content. Replace the value of api_token everywhere in the file: Vizrt.Socialize.Plugins.XML_JSON.Flowics.xml, for instance:

https://live.flowics.com/api/1.1/widgets/{Ticker}/data.json?api_token=FtKPo4JJYuSOuEpcu_HT4Q&v=2

9.7 Monterosa Feeds

File name: Socialize.Plugins.XML_JSON.Monterosa.xml You need to obtain the full URL to the feed providing your data. In addition, you should obtain an event ID and an access token from Monterosa. The token should be entered into the Value node here:

Authorization textbox Authorization bearer token Bearer <bearer token>

The token is sent as a header to the request URL.

 Note: The poll feed from Monterosais organizedin such a way that the JSON_XML base plugin is not able to parse more than one single post per feed. This is due to the poll questions description and the poll answers residing in disjoint locations in the feed, making it impossible for a simpleXPATH(v 1.0) location to associate answers to questions.

9.8 Never.No

File name: Vizrt.Socialize.Plugins.XML_JSON.NeverNo.xml For Streams of messages, polls and world clouds, replace the contents of the SourceUri with the customer’s URI on each particular reader in the file: Vizrt.Socialize.Plugins.XML_JSON.NeverNo.xml

{ComboParameter} Feed Name combobox

9.9 SAM Desk

File name: Vizrt.Socialize.Plugins.XML_JSON.SAM.xml Edit values of Username and Password under credentials as well as under the combo options parameter in Vizrt.Socialize.Plugins.XML_JSON.SAM.xml

NKN2RCXntLHi14Ot Vad6wE1iP2a22CIzJxhG8NdUZ6Uro2np {id} Story Name combobox

9.10 Spredfast

File names: Vizrt.Socialize.Plugins.XML_JSON.Spredfast.xml The Spredfast platform allows brand marketers to manage all of their social accounts from one platform. The result is streams of aggregated content from social sources, like Facebook and Twitter.

To connect to a Spreadfast source, you normally need a Spreadfast user account. Some of the Spreadfast plugins expose the account name in the GUI, some of them has the user account inside the plugin XML, and some do not require an account. In case the user account is given through the plugin XML, replace the contents of the Value field with the customer’s account in the XML files that require this, for instance Vizrt.Socialize.Plugins.XML_JSON.SpredfastFacebookHashtags.xml:

Spredfast https://docs.vizrt.com/vizstvfs/fsplugins/images/sources/Spredfast.png

http://api.massrelevance.com/{user}/{stream}/facebook_hashtag_counts.json {user} textbox massreldemo {stream} Stream combobox

Here the Parameters section contain a user parameter where the default value is set. Replace the text (massreldemo) with the real user name, The parameter attribute Internal hides the parameter from the GUI, supplying the value directly from the XML. Set te value to false to make the parameter appear in the GUI so the user can enter the user account.

9.11 Tagboard

FIle name: Vizrt.Socialize.Plugins.XML_JSON.Tagboard.xml. You need to obtain your Tagboard ID and enter it into the dialog box. Set the default value by changing the Value node:

{TagboardID} Tagboard ID textbox 294991

Also change the tgb-api-key and the tgb-user-key under the Value node:

tgb-api-key textbox JDJhJDEwJGNCbFJhQU43R1J0NjBMWjViclZZSi5ZelNNU2NtTUFpYVFVMjZFY0lFNU8xQ1hPdzF1eWVh

tgb-user-key textbox JDJhJDEwJEVFaUlseS8wVWxQWE5uMXhDS1N6ck9DLzVtcFlldnB2alp4UGdPMUJ4RlNCRGJmaGhaT2Nx

9.12 Telescope

File name: Vizrt.Socialize.Plugins.XML_JSON.Telescope.xml Replace Value field with the customer's authentication token in the following file: Vizrt.Socialize.Plugins.XML_JSON.Telescope.xml

{apikey} Api Key textbox VIZRTtesting

9.13 Twitter Curator There are two types of integrations with Twitter Curator. One is called Twitter Curator, which includes Stream and Collection Messages, Treandlines and Metrics of Streams. The other Twitter Curator Compare, which enables comparing two or more streams in order to create polls. In both cases you need to obtain an authorization token and replace it in the XML.

File name: Vizrt.Socialize.Plugins.XML_JSON.Curator.xml

{auth_token} textbox 2hxAhdEkcgKr8rx5Gu

9.14 Wayin

File name: Vizrt.Socialize.Plugins.XML_JSON.Wayin.xml The plugin consists of four readers: • Wayin Search - feed of messages based on the search parameters. • Wayin Search Top Stats - list of top terms, locations or connections with their volume count. • Wayin Search Trends - volume Linegraph based on the search parameters.

• Wayin Search Metrics - metrics of gender and sentiment based on search parameters. Replace the contents of the Value field with the customer’s API Key in the files below:

{apikey} apikey textbox 33089dtc76gn0qonie2fg6pjc

9.15 Wochit

File name: Vizrt.Socialize.Plugins.XML_JSON.Wochit.xml Wochit enables users to create their own videos worth sharing. Each user as access to their own video library. You need to obtain a partner ID from Wochit. Replace the contents of the Value field with the partnerID:

{partnerID} textbox e1ae33dbfecb1684a686c3a00db517ee48e283f25f661fd7d7c9480767969a88

9.16 NewsAPI

File name: Vizrt.Socialize.Plugins.XML_JSON.NewsAPI.xml NewsAPI is a simple API that returns JSON metadata for the headlines currently published on a range of news sources and blogs (70 and counting). You need to obtain an API key and replace the content of the Value node:

{api_key} textbox 1e9c957d899446f18cc679d693e0f492

9.17 Tintup

FIlename: Vizrt.Socialize.Plugins.XML_JSON.TintUp.xml

From Tintup you need to obtain a tint name and the access token from your Tintup account. These can be filled into the dialog box in the FeedStreamer GUI:

10 Defining Custom Readers Data is available from a wide range of sources, a spectrum that is continuously expanding. There are also many services that are popular only in certain countries or regions. The Feed Streamer therefore includes a generic plugin called Socialize.Plugins.XML_JSON that you can use to create custom feed readers that can consume any XML- or JSON-based feed. In order to create a reader for a particular service, you simply add information about the service and how you want to use it to an XML configuration file called Socialize.Plugins.XML_JSON.xml, or create it in a file with the name format Socialize.Plugins.XML_JSON.[Your Name].xml.

If you make changes to Socialize.Plugins.XML_JSON.xml you need to make sure your changes are copied to all Feed Streamer and Social TV server installations. For details, see Configuring the Feed Streamer.

 Note: When you develop and test a new plugin, the XML file must be deployed to both the Feed Streamer client installation and the Data Pusher server installation. The most convenient way of testing and developing is to have both the client and server installed on the same PC. The plugin folder is in both cases: C:\Program Files (x86)\Vizrt\Viz Feed Streamer\Plugins You need to restart both the Feed Streamer client and the Data Pusher server for changes to take effect.

In order to add reader definitions to Socialize.Plugins.XML_JSON.xml you need to be comfortable editing XML files. It also helps to have some basic understanding of XPath (see http:// en.wikipedia.org/wiki/XPath).

Socialize.Plugins.XML_JSON.xml has a root element called ReaderTypes, containing a sequence of Reader elements. Each Reader element, contains configuration data for a different service. It specifies: • How to request a feed from the service • What to extract from the returned feed

 Note:

You should be able to create feed readers for the vast majority of social media services using the Socialize.Plugins.XML_JSON plugin. For special cases where this is not possible, it is possible to create your own Feed Streamer plugins using the Social TV SDK. For more information about this, please contact your Vizrt representative.

This section contains information on the following topics: • How to Define a Custom Reader • The Configuration File Format See Also

• Third Party Integrations

10.1 How To Define A Custom Reader

The simplest method of creating a reader is to copy an existing Reader element and edit it. You do, however, need a basic understanding of how a Reader element is structured, and how it is used by the Feed Streamer.

A Reader element always contains a Name and Icon element that determine its appearance in the Feed Reader, but its most important child elements are:

• Request, which determines the URL that a source sends to request a feed, and • Response, that defines how the returned feed is interpreted and converted into a Feed Streamer item

This section contains information on the following topics:

• Understanding Requests • An Example Request

• Understanding Responses • Xpath extensions • An Example Response • Using parameter values inside entry templates

• Including Media Objects in Feed Streamer Atom Entries • Author thumbnail • Video Clips and Images

• Including Geolocation in Feed Streamer Atom Entries • Including VDF payloads in Feed Streamer Atom Entries • Reading JSON Feeds • Multiple Root Nodes • Arrays • Attributes and Namespaces • Example

• Template Switching • Define Different Roots per Template • Concatenating Selected Nodes • Reflecting Feeds • Calculating Percentages for Concatenated Selected Nodes • Using the Value of a Parameter on Other Parameters • Basic Authentication • Removing Expired Messages • Grouping Sources

10.1.1 Understanding Requests The URL sent by a Feed Streamer source is formed by combining a basic URL template (defined in the Url element) with various parameters specified by the Feed Streamer user when the source is defined. These parameters are defined in Parameter elements, and the Parameter element has a number of child elements that allow you to define the caption used to name it in the Feed Streamer dialog, a default value, a list of allowed values or options and so on. Request parameters can be combined with the URL template in two different ways: • They can be appended to the end of the URL template as ordinary HTTP request parameters, or • They can replace special placeholders in the URL A parameter that is to replace a placeholder must have a name that is enclosed in braces like this:

{topic} Topic ...

When a source is created in the Feed Streamer, whatever the user specifies in the Topic field will replace all occurrences of {topic} in the URL template. If the Feed Streamer user specifies “sport” in the Topic field, then the template

http://my-service.com/{topic}/entry will be converted to the URL

http://my-service.com/sport/entry

If the parameter name is not enclosed in braces then the template

http://my-service.com/entry will be converted to the URL

http://my-service.com/entry?topic=sport

An Example Request

The following example shows a Request element that creates and submits a request to Instagram:

http://instagram.com/tags/{tagName}/feed/recent.rss {tagName} Tag Name textbox

The Url contains one placeholder, called {tagname}, and one corresponding parameter with the same name and the caption “Tag Name”. This parameter therefore appears in the Feed Streamer’s Add New Source dialog like this:

If the Feed Streamer user enters “trees” in the Tag Name field, then the URL actually submitted when this source is selected is:

http://instagram.com/tags/trees/feed/recent.rss and Instagram will return a feed containing pictures tagged #trees.

10.1.2 Understanding Responses The Feed Streamer uses a similar templating mechanism for converting the response returned from a web service into a stream of Feed Streamer items. Feed Streamer’s native format is Atom, an IETF standard syndication format (see http://tools.ietf.org/html/rfc4287). Each Feed Streamer item is stored in the Data Hub as an Atom entry element. For example:

entry1234567 What’s up?

Not much.

My Social Service

 Note: Defining the "id" tag in the response section is mandatory. In addition, the "id" should be something unique per entry.

One of a Response element’s child elements, therefore, is always an Atom entry template. Like the Url template in a Request element, an entry template can contain placeholders enclosed in braces:

{guid} {title}

{description}

My Social Service

In this case, however, the values inside the braces are not parameter names, but XPath expressions. XPath (see https://en.wikipedia.org/wiki/XPath) is a language for selecting nodes from XML documents. So, for example, the id element in an entry template will usually contain an XPath expression that selects the content of some corresponding identifier element in the returned feed document. Simple XPath expressions look very much like file paths and work in much the same way: they describe the path from one node in an XML tree (the root node by default) to another node (or sequence of nodes). Vizrt has developed new extensions for XPath, as outlined in the table below. The extensions make possible replacing old strings with new strings and enable the capitalization of entire words, sentences or individual letters.

Xpath extensions

Extension Parameters

vizext:repla , , ce

Extension Parameters

vizext:Conv , Where operator is one of:“ToUpper”: Capitalize the whole ertCase text“ToLower”: Convert the whole text to lower case“CapSentence”: Capitalize only the first character in the sentence“CapWord”: Capitalize the first character in every word

The following is an example of using the ‘replace’ extension to replace spaces with underscore:

This is the first title This is the second title

//title[vizext:replace(., “ “, “_”)]

The result then is: This_is_the_first_title This_is_the_second_title

The XPath expressions that appear in entry templates don’t describe the path all the way from the root of the feed document but from a local root or context set by the Response’s Root element. The following example shows how it works.

An Example Response Suppose that a service returns an RSS feed that looks something like this:

... ... ... ...

And each item looks something like this:

Aww http://... some text ... Sun, 23 Jun 2013 12:53:25 -0700 some-long-id Aww some text ...

A. N. Other

You can then convert the feed to Feed Streamer format with the following Response configuration:

/rss/channel/item {guid} {title}

{description}

{media:credit[@role=’photographer’]} {pubDate}

The Root element contains an XPath expression (/rss/channel/item) that selects all the item}}s in the feed. The {{entry template is then applied to each of these items, with the item itself providing a local root (or context) for all the XPath expressions in the template. The result is a sequence of valid Feed Streamer items that look like this:

some-long-id Aww

some text ...

A. N. Other Sun, 23 Jun 2013 12:53:25 -0700

As you can see from the entry template shown earlier, some XPath expressions are rather more complicated than simple file paths (such as media:credit[@role=’photographer’], for example). There are lots of resources on the Internet for learning XPath. You could start here: http:// www.w3schools.com/xpath/.

 Note: The system will use the current time of the computer if a reader does not have a published date defined in the response. Each item will be updated in every read interval.

The syntax is that you precede the parameter with ^ sign to specify it refers to a request parameter and not an xpath reading from the response feed.

Using parameter values inside entry templates When defining a reader, the user can use a request parameter value in the response section of the reader. This feature adds the ability to use the request fields value in the response. The request section in the reader defines the fields that are used to define a source when adding a new source. It is possible to use parameter values inside an entry template by adding the '^' sign to the parameter name as follows: {^paramA} This instructs the system that a parameter from parameters section should be evaluated. Thus, both parameters and XPath can be used together in any order, as follows: {xpathA}{^paramA} Advanced use:

Assume that we have an entry nodes called: video_type, image_type, audio_type on three different templates, and we have a combobox parameter called {paramA} with following values: video, image, audio. To get those nodes, the expression should look like this: {{^paramA}_type}

The system will replace param with its value, and we will get a: {video_type} xpath variable that will be retrieved from our source feed element.

{xpathA} color:red}^paramA{color picture

color:red}^paramB{color {^xpathB}

{from} {creationDate}

10.1.3 Including Media Objects in Feed Streamer Atom Entries Many of the feeds returned by social media services include media objects such as images and video clips. These can be selected and included in your Feed Streamer items as described below.

Author thumbnail

You can include images using the thumbnail element, which belongs to the http:// search.yahoo.com/mrss/ (Media RSS) namespace. You can see how this is used in An Example Response. In the example, a prefix (media) is declared for the namespace in the entry element, and a media:thumbnail element is then included as a child of the entry element:

The thumbnail element’s url attribute contains an XPath expression that selects a URL from an appropriate node in the source feed.

 Note: The images you reference in this way will be displayed in the Feed Streamer as thumbnails, but you don’t necessarily have to pick thumbnail-sized images from the source feed. Whatever image you select is automatically scaled to the required size.

Video Clips and Images

You can include video clips using an Atom link element. The link element must be included as a child of the entry element and have the following attributes set:

• rel: Must be set to enclosure • type: Must be set to the correct MIME type for the video clip • href: Must be set to the URL of the video clip For example:

In this example, the href and type values are selected from the source feed using XPath in the usual way.

10.1.4 Including Geolocation in Feed Streamer Atom Entries Many of the feeds returned by social media services include geolocation information. These can be selected and included in your Feed Streamer items by including the following part:

LATITUDE LONGITUDE

This element adds two namespaces that have to be added to the entry element - xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml". An example taken from Instagram configuration:

{location/latitude} {location/longitude}

10.1.5 Including VDF payloads in Feed Streamer Atom Entries Viz Data Format (VDF) is a proprietary Vizrt data format used for transferring data between different Vizrt components and systems. A data set encoded in VDF is called a VDF payload (as opposed to a VDF model, which can be used to define the structure of the VDF payloads used in a particular application or context). You can find formal reference documentation for VDF on your Data Hub at:

http://data-hub-host-name:8089/doc/model.html

A Feed Streamer entry can include a VDF payload in its content element. You can use this payload to define a set of fields that will be used as input to a Viz Artist scene. The following example shows a content element that contains a VDF payload:

{location/@latitude} {location/@longitude}

This payload contains a single field called geolocation, but you can define payloads containing any number of fields. The payload is not made visible in any way in the Feed Streamer and will only be used if it is passed into a Viz Artist scene.

10.1.6 Reading JSON Feeds The Feed Streamer handles JSON feeds by converting them to XML so that they can be read using XPath in exactly the same way as XML feeds. There are a few small structural differences between JSON and XML that are “corrected” during the conversion if necessary. These differences and the corrections applied are described below.

Multiple Root Nodes A JSON document can have more than one root node, whereas an XML file must always have only one root node. The Feed Reader, however, actually does allow the generated XML to have multiple root nodes. If the result of the conversion is a sequence of entry elements like this:

... ... ...

You can access them by setting your Root element as follows:

/entry

Arrays JSON, unlike XML, supports arrays of values. Therefore, when the Feed Reader encounters an array in the JSON data, it converts it to a sequence of elements, and assigns the name of the array to every element in the sequence. For example:

{ "data": [ { "id": "187217284764371_208301655989267", … }, { "id": "100004487948773_192672864225644", … } ], … } gets converted to:

187217284764371_208301655989267 … 187217284764371_208301655989267

… …

If the whole JSON feed is an array (that is, the array occurs at the root level), then the predefined string root is used to name the root level elements. The following JSON feed, for example:

[ { "id": "187217284764371_208301655989267", … }, { "id": "100004487948773_192672864225644", … } ] would get converted to:

187217284764371_208301655989267 … 187217284764371_208301655989267 … …

Attributes and Namespaces JSON does not support attributes or namespaces. No correction is required here, it just means that the resulting XML never contains any attributes or namespaces.

Example Facebook graph search returns JSON data. The following query:

https://graph.facebook.com/search?q=vizrt&limit=2 will return something like:

{ "data": [ { "id": "187217284764371_208301655989267",

… }, { "id": "100004487948773_192672864225644", … } ], … }

The Feed Reader converts it to XML that looks like this:

{ "data": [ { "id": "187217284764371_208301655989267", … }, { "id": "100004487948773_192672864225644", … } ], … }

It can therefore be converted to a sequence of Feed Streamer entries with a Response element like this:

/data {id} …

10.1.7 Template Switching You can define Readers that contain multiple Entry templates, and switch between them depending on the content of the items in the feed. This can be useful for handling feeds that contain entries with variable structures. There are, for example, aggregation services that will monitor multiple social networks for you and generate an aggregated feed. The items in such feeds are not always converted to the same form, so you get a feed that contains differently formatted items. In this case the Feed Reader can test an identifying element or attribute in each item and then select the appropriate template to process it.

The following example shows a feed containing a sequence of message elements that have slightly different internal structures and therefore need to be handled differently:

1234 My Post

Some details

2013-07-30T15:30:43.794382Z 9876 A nice image http://images/nice.jpg 2013-07-29T12:35:01.937222Z

Each message element has a type attribute that can be used to identify the different message structures. The following Response contains a corresponding sequence of alternative Template elements for handling the different message types. Each Template element in the sequence has a pair of attributes called NodePath and NodeValue, and a template is only applied to an item if the node selected by NodePath matches the value specified in NodeValue. In this case, if a message element’s type attribute contains the value post, then the first of the entry templates shown below is used to process it. If it contains image, then the second entry template is used, and so on.

/feed/message

10.1.8 Define Different Roots per Template This feature enables the user to define different root paths, which are used in different reader templates according to a defined condition in the template, by specifying a parameter name and its value.

/entries /comments/comment /poll

Here is considered as a default root. If the conditions within the templates are all false or the alternating root is not found, the default root is used. On the other hand, defines alternating root paths for the reader. The template (reader type is used to define a new source) uses one of the root paths according to the template conditions. If a condition in a template is true, the matching root path is used for the reader and the appropriate fields are displayed.

10.1.9 Concatenating Selected Nodes In general, you want the Xpath expressions in your Entry templates to select single nodes in the source feed items. The Feed Streamer therefore ensures that this is the case by default. If an expression in an entry template returns a sequence of nodes, then the Feed Streamer will only keep the first node in the sequence and discard the rest. Assume, for example, that an incoming feed contains entries with the following structure:

123 2013-07-30T15:30:43.794382Z aaa bbb ccc ... ...

In this case, the XPath expression in the summary field of the entry template below

/messages/message ...

{infos/info}

... returns “aaabbbccc”. The Feed Streamer, however, only keeps the first of the three returned nodes, so the resulting summary element will only contain “aaa”. If you specifically want to select the content of one of the other info elements, you can do so by specifying the position of the required node using standard XPath syntax (infos/info[2] or infos/ info[last()], for example). Occasionally, however, you might actually want to keep the content of all the returned nodes. To do this, enter a single asterisk before the XPath expression. For example:

{*infos/info}

If you do this, then the Feed Streamer will keep all the returned nodes and concatenate them, inserting a pipe character as separator between each node:

aaa|bbb|ccc

 Note: {} is also used as a “wild card” character in XPath. If you need to use an XPath expression in which {} is the first character, then you must escape it with a backslash (}}) in order to prevent Feed Streamer from treating it as a concatenation instruction. The expression: {{{*[local-name()="thumbnail" or local-name()="enclosure"]/@url}, for example, must actually be written as { *local\-name\()="thumbnail" or local\-name\()="enclosure"/@url}in order to be interpreted correctly.

10.1.10 Reflecting Feeds The following parameter can be added in order to enable the Reflect Feed option in Feed Streamer. Setting the value to True will enable Reflect Feed (the Reflect Feed check box will be checked). Setting the value to False will disable Reflect Feed (the check box will be unchecked).

IsFeedReflection True

The following parameter determines if the reflection option is exposed in source settings so the user can modify.

IsFeedReflectionOptional True

10.1.11 Calculating Percentages for Concatenated Selected Nodes This feature allows users to automatically calculate percentages for concatenated numeric fields. The following is an example of a data feed for using this feature:

aaa 20 bbb 30 ccc 150

This feed contains a number of items, each of which contains a value. This feed contains the values 10,15 and 75. The percentage is calculated based on the values, which are contained within customized messages.

Resources/icons/MassRelevance.png http://tweetriver.com/{user}/{stream}/facebook_hashtag_counts.json {user} textbox vizrttests

{stream} Stream combobox /root/data {*//hashtag} {*//hashtag}

{*//data/counts/total}

Facebook Facebook {*//hashtag} {*//hashtag} {*//data/counts/total}

{url} {url} Feed Url textbox c:\temp\myitems.xml

/items {/items/item/name} {*/items/item/name}

{%/items/item/value}

10.1.12 Using the Value of a Parameter on Other Parameters The examples below contain two parameters - {user} and {FeedType}. Changing the value in the curled brackets will replace the value of that parameter throughout the entire XML. The first example deals with the case of a combobox where the options derive from a URL. The user can use the value of a textbox that defines either all of or part of the URL. Users with multiple accounts with third-party providers - and where the list of feeds is based on the account - can enter their account in a text box and that value should be passed to the source URL of the drop-down menu. For example:

{user} Account textbox massreldemo {stream} Stream combobox

In the second example, third-party providers have separate feeds for different types of data. A combobox will appear based on the feed type selected by the user, for example an RSS feed that has subtopics that will appear in a list in the drop-down menu. For example:

{FeedType} Feed Type combobox

Messages social

{ComboParameter} Feed Source combobox

10.1.13 Basic Authentication For feeds that require basic authentication, the user password combination is defined in the reader, enabling the system to get information from the feed. This is done by adding a node to the request node of the reader XML, as described here:

https://app.samdesk.io/api/v1/stories my_username my_password

10.1.14 Removing Expired Messages The XML file below ensures that all messages past the date field (in bold below) will be deleted. For information about configuring data and time format, please refer to the DateFormat section. The reader can be configured to include the expired extension as follows: xmlns:age="http://purl.org/atompub/age/1.0" [xpath to date] For example:

An entry with an expiration timestamp 2005-12-12T12:00:00Z

An entry with an expiration

 Note: Expired messages are deleted from the DataHub. Any deleted messages that were part of pages in a Trio playlist will therefore also be deleted from the pages. In addition, messages from inactive sources are not deleted regardless of their expiry time. There is also a 10- second delay after an expired message is deleted until it is completely removed from the DataHub.

10.1.15 Grouping Sources Grouping sources are defined by adding the group name to the reader XML file with the following tag: group_name

Here, group_name is any name the user wants to represent a number of readers. This should be done for every reader that will be part of the group “group_name”. Here is an example XML segment that illustrates this scenario:

Spredfast

Resources/icons/Spredfast.png http://api.massrelevance.com/search/search.json?filter.text={term}

 Tip: Read the Grouped Sources section for more information about adding grouped sources to the Sources list.

10.2 The Configuration File Format

This section contains a reference description of the Socialize.Plugins.XML_JSON.xml file format. The elements that may appear in the file are described in alphabetical order. The description of each element contains information about: • The purpose of the element • The element’s attributes • The element’s content model (what other elements and values it may contain) This section contains information on the following topics:

• Overview • Caption • DateFormat • Entry • Image • InitialReadLimit • Name • NameSpaces • Option • Options • Parameter • Parameters • Reader • RefreshRate • ReaderTypes • Response • Root • Template • Templates • Url • Value

10.2.1 Overview In general, the order of elements is not significant. The following content model diagram, for example:

... ... specifies that a Request element must contain a Url element and a Parameters element. However, these elements do not have to appear in the order shown. The following conventions are used in the content model diagrams: Table 2: Content Model Conventions

... Represents omitted content

? Preceding element(s) or attribute(s) are optional and may appear 0 or 1 time

* Preceding element(s) or attribute(s) may appear 0 or more times

+ Preceding element(s) or attribute(s) may appear 1or more times

[] Encloses alternatives

| Separates alternatives

text Text content

You will notice that some of the element names in the content model diagrams are links. This is just a convenience to simplify navigation between the diagrams. The descriptions assume that you are familiar with XML syntax rules and terminology.

The root element of the Socialize.Plugins.XML_JSON.xml file must be a Caption element.

10.2.2 Caption This element may appear either as the child of a Reader element or as the child of a Parameter element:

As the child of a Parameter element, it specifies the caption to be used when the parameter is displayed in a user interface component. If the Caption element is not specified, then the parameter is not displayed.

As the child of an Option element, it specifies the caption to be used when the option is displayed in a user interface component. If the Caption element is not specified, then the option’s value is displayed as a caption.

Content Model

text

10.2.3 DateFormat This element contains a date format specification that the Feed Streamer uses to parse dates in the source feed. If your Entry template contains a published element, for example, and you want to get the content from some date element in the source feed, then you need to: 1. Examine the format of the dates in the source feed 2. Include a DateFormat element containing a format specification that correctly describes the dates The date format specification can either be: • The string unix if the dates are standard Unix-style dates in seconds since epoch • The string unix_msecs if the dates are standard Unix-style dates in milliseconds since epoch • A .NET custom date/time format string as described in http://msdn.microsoft.com/en-us/ library/8kb3ddd4.aspx

Content Model

text

10.2.4 Entry This element is actually a template for generating Atom entry elements. Atom is the format used to represent feed items in the Feed Streamer. The template must therefore be a valid Atom entry element containing Xpath expressions that select data from the elements in the nodeset selected by the Root element. The XPath expressions must be enclosed in braces ({ and }). When a source is opened in the Feed Streamer, the XML or JSON document specified by the Name element is retrieved. An Atom entry based on this template is then generated for every node that the Root element selects from the retrieved document. The following example shows a very simple entry template that selects data from RSS feed items:

{title} {title}

{description}

My RSS Feed

In this example, both the id and title element values are copied from the RSS items’ title elements, while the summary element values are copied from the RSS items’ description elements. The author names are all hard-coded to “My RSS Feed”.

Content Model See the Atom specification at http://tools.ietf.org/html/rfc4287. Note, however, that the Feed Streamer does not make use of all the elements in an Atom entry. These are the elements that are used if present:

author/name contributor/name id title summary content link published

The Feed Reader will also make use of a thumbnail element belonging to the Media RSS extension (see http://www.rssboard.org/media-rss) if one is included in an entry. If you use this element then you must declare its namespace as well. For an example of how to use it, see Including Media Objects in Feed Streamer Atom Entries. Any other valid Atom elements in the entry will not be rejected, but will not be used by the Feed Streamer either.

10.2.5 Image The URL of an image to be used as an icon. The image is used in the Feed Streamer to represent the reader and any sources that are based on it. You can either specify a relative URL referencing a local copy of the icon you want (Resources/ icons/RSS-icon.png, for example) or an absolute URL referencing an image somewhere on the internet (https://upload.wikimedia.org/wikipedia/en/thumb/4/43/Feed-icon.svg/128px-Feed- icon.svg.png, for example). If you specify a relative URL then it is resolved relative to your Feed Streamer installation folder (usually C:\Program Files (x86)\Vizrt\Viz Feed Streamer).

Content Model

text

10.2.6 InitialReadLimit This parameter will limit the number items that are retrieved from the source for the first time:

100

Here, ‘100’ indicates that only the first 100 items will be retrieved in the case of a source that has hundreds or thousands of items. This is used in order to avoid reading old items that are part of the feed. Only new items will be retrieved after the initial 100 items are collected.

10.2.7 Name This element may appear either as the child of a Request element or as the child of a Reader element: As the child of a Reader element, it defines the name of the Reader - for example Flickr or MyCompany Blog. This is the name that appears in the Feed Streamer’s source editing dialogs. As the child of a Parameter element, it defines the name of the parameter - for example {keyword} or lang. The parameter it names is used differently depending on whether or not the name is enclosed in braces ({ and }) or not:

• If the name is enclosed in braces then the parameter’s value is used to replace any references to the parameter that appear in the request URL (as, for example, in http:// myservice.com/feeds/feed?kw={keyword}). • If the name is not enclosed in braces, then the parameter is simply appended to the request URL (http://myservice.com/feeds/feed?kw=trees&lang=en_US, for example)

Content Model

10.2.8 NameSpaces Declares namespace prefixes for use in XPath expressions. If you need to refer to foreign elements in either the Root XPath expression or in any of the XPath expressions in the Entry template, then you must: • Declare prefixes for the foreign namespaces in the NameSpaces element • Use the prefixes you have declared as necessary in your XPath expressions When writing an entry template, it is important to distinguish between the namespace prefixes used for foreign elements in the entry itself, and the namespace prefixes appearing in XPath expressions, which identify foreign elements in the source feed. For example:

/rss/channel/item {guid} {title}

{description}

{media:credit[@role=’photographer’]} {pubDate}

Here the namespace declaration is made twice: once in the entry element, because the entry contains a media:thumbnail element, and once in a NameSpaces element. This declaration is needed because the source feed contains elements from the same http://search.yahoo.com/mrss/ namespace and because we need to refer to one of them (media:content) in one of the template’s XPath expressions.

Content Model

Attributes xmlns:text: The text following the colon is the namespace prefix you want to use to reference the namespace, the value of the attribute is the full namespace identifier. You can repeat this attribute to declare several namespaces in one NameSpaces element.

10.2.9 Option Defines one of a set of allowed opt ions for a parameter. An option consists of a value (the actual parameter value) and a caption (the string used to represent the value in user interface components).

Content Model

10.2.10 Options Specifies a list of options (allowed values) for a parameter. The options are either specified in a sequence of child Option elements or by reference to an XML resource containing the allowed values.

Content Model

Attributes The following attributes together define a method of extracting options from an XML document.

SourceUri: The URI of an XML document containing the values to be used as options. If you specify a relative URI then it is resolved relative to your Feed Streamer installation folder (usually C: \Program Files (x86)\Vizrt\Viz Feed Streamer).

Root: An XPath expression selecting a nodeset in the document identified by SourceUri that is to provide the context for the expressions used in Caption and Value. The expression /datasources/ datasource, for example, might return a set of datasource elements from which option values and captions can be selected.

Value: An XPath expression that selects a value from each node in the nodeset returned by the Root XPath expression. The expression @url, for example, would selected the url attribute of each node. The selected values are used as option values.

Caption: An XPath expression that selects a value from each node in the nodeset returned by the Root XPath expression. The expression @name, for example, would selected the name attribute of each node. The selected values are used as option captions.

Username and Password: This is only relevant with SourceUri that adds an “Authorization” HTTP header to the external source request. When both the username and password are provided, the value of the header is a concatenation separated by a colon. For example, the header format is an encoding of the username and password concatenation, i.e. “Authorization: ([username attribute value]: [password attribute value])”. On the other hand, when only a password is provided, the value of the header is the password attribute value and the header format is “Authorization: [password attribute value]”. Parameters that get their value from external fields can also do basic authentication. In this case, the user will provide the required information when creating a source. For example:

{id} Story Name combobox

A combobox will re-evaluate its options after entering a value for a user field.

10.2.11 Parameter Defines a parameter to be included in a request URL. The parameter definition can include the information needed to display it in the Feed Streamer’s source editing dialogs.

Content Model

... ...?

...? ...?

Attributes

Visible: Specifies whether or not the parameter is to be displayed in the Feed Streamer’s source editing dialogs. The default is true.

Mandatory: Specifies whether or not the parameter is required. If you specify true, then the Feed Streamer will not allow users to Add a source without specifying a value for the parameter. The default is false.

Internal: If set to true then the value of the parameter will not be included in the request URL. The default is false.

10.2.12 Parameters Contains a sequence of Parameter elements, each of which defines a request parameter.

Content Model

...*

10.2.13 Reader Contains all the information the Feed Streamer needs to: • Request a feed from a particular online service • Generate the user interface components that will appear in the Feed Streamer’s source editing dialogs for sources based on this reader • Locate and extract the required information from the returned feed • Convert the extracted information into a sequence of standard Feed Streamer items

Content Model

... ... ...

Attributes Enabled: Specifies whether or not the feed reader is to be enabled. If this attribute is set to false then the reader will not appear in the Feed Streamer’s source editing dialogs. The default is true.

10.2.14 RefreshRate Alter the frequency a destination is refreshed in order to gather data faster or slower if pacing updates is desired. Use the following parameter to define how often to read from the source:

The default refresh rate is five seconds. Other time units that can be entered are 60m where ‘m’ stands for minutes, 1d where ‘d’ stands for day, and 1w where ‘w’ stands for week.

10.2.15 ReaderTypes This is the root element of the Socialize.Plugins.XML_JSON.xml file. It contains a sequence of Reader elements, each of which defines a custom feed reader.

Content Model

...*

Request Contains all the information the Feed Streamer needs to: • Request a feed from a particular online service • Generate the user interface components that will appear in the Feed Streamer’s source editing dialogs for sources based on this reader

Content Model

... ...

10.2.16 Response Contains all the information the Feed Streamer needs to extract the required information from a returned feed and convert it to an Atom feed, which is the Feed Streamer’s native format.

Content Model

... ? ...? [ ... | ... ]

10.2.17 Root An XPath expression that selects a nodeset in the XML or JSON document returned by a Feed Streamer source. The returned nodeset provides the context for all XPath expressions in a Options’s entry template. If, for example, the returned document is an RSS feed, you might specify /rss/channel/item to select all the items in the feed. If you need to reference namespaces in your XPath expression, use the Image element to declare prefixes for them.

Content Model

text

10.2.18 Template

One of a series of Template elements in a Response. Each of the Template element contains a different Entry template. The Feed Reader uses the values specified in the Template elements’ attributes as conditions for determining which entry template to use for each item in the source feed. For an example of how to use this element, see Template Switching.

Content Model

Attributes

NodePath and NodeValue: If the value returned by the XPath expression in NodePath is equal to NodeValue then this Template’s Entry will be used.

10.2.19 Templates

Contains a series of Template elements as an alternative to a single Entry template in a Response. For an example of how to use this element, see Template Switching.

Content Model

Type The type of user interface component to be used to present the parameter in the Feed Streamer’s source editing dialogs. The following values are allowed: • textbox: A simple text box. • combobox: A drop-down combobox offering a list of options. If you specify this value then the parent Reader element should also include an Options element. • format: Specifies where [longitude] is a placeholder for longitude and [latitude] for latitude

Content Model

textbox|combobox|uri|checkcombobox|checkbox

Attributes • uri: URI which is escaped to UNC if pointing to a file on a mapped drive. • checkcombobox: combo box where each item has a check box next to it. Selected items’ values will be concatenated, separated by comma. • checkbox: check-box control resulting True or False

Example of format option

{location} Location location longitude=[longitude]&latitude=[latitude]

Here, {location} in the URL will be replaced with the actual values, i.e. the relevant latitude and longitude coordinates.

10.2.20 Url The URL used to request a feed from an online service. The URL may include parameter- references enclosed in braces ({ and }). A parameter reference is replaced by the value of the referenced parameter when a source is created in the Feed Streamer. In the URL http:// myservice.com/feeds/feed?kw={keyword}, for example, {keyword} will be replaced by the value of the parameter called {keyword}. The parameters available for use in a Request’s Url are defined in a the Request’s Parameters element.

Content Model

text

10.2.21 Value This element may appear either as the child of a Reader element or as the child of a Parameter element: As the child of a Parameter element, it defines the default value of a parameter. If this element is omitted, then the default value is null. If the parent Parameter element’s Visible attribute is false then any value specified here is effectively a fixed value. As the child of an Option element, it defines the value of the parameter.

Content Model

text

11 Social TV REST API This section describes Feed Streamer’s API, which is a subset of the generic Atom based RESTful API of DataHub whose usage reference is available at http://:8089/doc. The solution uses four main entities for which designated atom collections are created and maintained: • Sources • Groups • Messages • Spaces • Pagination

A description of how these can be accessed and modified by clients is also provided, which is the same method employed by Feed Streamer and other parts of the solution. Only operations that clients are allowed to perform without interfering with the structures created and maintained by the Social TV solution are shown. For example, clients are not expected to create new entities, because they require internal knowledge that is only available to the built-in solution clients. Other operations might be accepted by the server but later provide some unexpected results.

 Note: Some parts of the HTTP response from the server were omitted for the purposes of improving readability.

11.1 Sources

11.1.1 URL http://datahub:8089/directory/title/Socialize/Sources/feed • Read sources • Delete a source

Read sources

GET /directory/title/Socialize/Sources/feed => SRC_21322b28-89cc-4fe9-8800-f994d43d03f2 Elections SRC_c207c900-7f3d-45cc-8324- a65b8b3d6949 Lebron SRC_4aae1cc0-d14a-49dc-9699-ebc2488c4425 Golden State Warriors

11.1.2 Delete a source

DELETE /directory/title/Socialize/Sources/ or

DELETE /directory/id/

11.2 Groups

11.2.1 URL http://datahub:8089/directory/title/Socialize/Groups/feed • Read groups • Delete a group

Read groups

GET /directory/title/Socialize/Groups/feed => GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30 Politics GRP_2d802dc7-a901-4431-ad2e- cb15ef5c7dc9 NBA GRP_9f56d7c2- d45d-4552-83d8-821e8d61451e EURO 2016

11.2.2 Delete a group

DELETE /directory/title/Socialize/Groups/ or

DELETE /directory/id/

11.3 Messages

11.3.1 Message Information Messages contain different information depending on the source they originate from. Different sources bring different a set of data fields, and might even use different fields for different purposes. This sample Instagram message contains most available fields:

4eb2b4110bdadad1deb668bbf8f9df20 #bono #cat #cats #britishshorthair #happy #sleep #çeşme #sun #summer #love #angel #baby #çeşme #drunkinlove #deephouse #deep #heard #ılovecats #friends #BestFriends

Bla bla

2015-07-29T10:07:54.000Z 2015-07-29T10:10:13.172Z Ahmet Tpr Instagram 38.425793766 27.167525763 0

Please refer to the Standard Field Identifiers section for more information about each specific field.

Retrieve messages with their content (payload) Some sources provide more data than is possible to represent in the standard atom fields. In these cases, the data comes in the message atom:content field, following Vizrt Data Format (VDF) specifications. By default, messages responses do not contain this part, unless the following argument is added to the request: inline_content=true. Read source messages:

GET /directory/title/Socialize/Sources/Lebron/feed => 44785c96566f6189348c3cdc8d666aee Boys 7 y LeBron $40.00 would like sold today can meet 5527ab39c2d4d8a6ac5722e961619f16 Are you a fan of Kobe, Lebron, Durant and Jordan? ...

This is a typical response that contains list of messages and will be referred to as [Messages] later in the doc.

11.3.2 Read group messages

GET /directory/title/Socialize/Groups/NBA/feed => [Messages]

11.3.3 Read source messages

GET /directory/title/Socialize/Sources/Elections/feed => [Messages]

11.3.4 Search messages

GET /search?q=lebron

This will return all messages where title, summary or author fields contain the text “lebron”. It is possible to specifically search for a certain field specifying the field name and colon, e.g /search? q=title:obama. Searchable fields are id, title, summary, author, contributor, updated, published and directory. The latter can be used to search for messages belonging to certain collections (groups or sources). The value should be the ID of the collection rather than its title. For example the request:

GET /search?q=summary:obama AND directory:SRC_21322b28-89cc-4fe9-8800-f994d43d03f2

Will return the message that their summary contains the text “obama” and that they are associated to the source whose atom>:id is SRC_21322b28-89cc-4fe9-8800-f994d43d03f2 (in this example it is the “Election” source). A field can be repeated multiple times in the search query, for example:

/search?q=summary:obama AND (directory:SRC_21322b28-89cc-4fe9-8800-f994d43d03f2 OR directory:GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30)

The search syntax supports parameters such as AND/OR and others. Please refer to Lucene query syntax for more information. Pay attention that quotation marks are required when the value contains a space, dash, slash or other special characters. In addition to these, the client can specify the desired order of messages by providing the “sort” request argument with value that is one of the searchable fields. Precede this with a backslash to indicate a reversed order. For example:

GET /search?q=summary:obama&sort=\title

In order sort the messages in their association order, the search term must include the term field, i.e. /search?q=summary:obama AND directory:SRC_21322b28-89cc-4fe9-8800-f994d43d03f2 AND directory:GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30 AND term:GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30 This requests searches for all messages associated to a group with the id GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30. They are also part of the source with id SRC_21322b28-89cc-4fe9-8800-f994d43d03f2, and the messages are returned in an order that can be applied during association.

11.3.5 Associate message(s) to a group

POST /directory/id/GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30/feed Content-Type: text/uri-list http:// datahub:8089/directory/id/3c4ebb361df40abd87594e4a5a4fc6f5 http://datahub:8089/directory/id/ 9ba7337faae315677b73f896a6c2a151

The request body contains a list of messages URLs. The same content type is used to associate to or un-associate from collections, and will be referred to later in the doc as [Message URLs].

 Note: Resources can either be accessed through their id based URL which is in the form http:// datahub:8089/directory/id/, or they can be accessed through their name URL, e.g. http://datahub:8089/directory/title/Socialize/Groups/Politics

Therefore, the above request is equal to:

POST /directory/title/Socialize/Groups/Politics/feed Content-Type: text/uri-list [Message URLs]

11.3.6 Associate message(s) to a group in a certain order It is possible to set the desired order of the messages relative to other messages by using the following request arguments “position” and “preceding”. For example, the following request will associate messages applying an order in which the associated messages come before a message whose atom:id is 3ca58c8994c782c96eae04fbf97d2065:

POST /directory/id/GRP_668ed8af-e6d0-4a0a-b1b2-2f7155a1e8cd/feed? position=3ca58c8994c782c96eae04fbf97d2065&preceding=true

The preceding argument can either be true or false, and is assumed to be false if not provided.

11.3.7 Unassociate message(s) from a group Same as above, with “remove=true” argument, e.g.:

POST /directory/id/GRP_5f7ef87a-847a-4228-8c9b-97b16b844c30/feed&remove=true Content-Type: text/uri-list [Message URLs]

11.3.8 (Un)marking message(s) as Favorite/Approved/Rejected Favorite/Approved/Rejected message attributes can be assigned in the same way we associated or un-associate to or from a source or group. For example, we can mark messages as favorites through this request:

POST /directory/id/SYS_FAVORITES/feed Content-Type: text/uri-list [Message URLs]

We can un-mark message as rejected by this:

POST /directory/id/SYS_REJECTED/feed&remove=true Content-Type: text/uri-list [Message URLs]

And we can approve messages through:

POST /directory/id/SYS_APPROVED/feed Content-Type: text/uri-list [Message URLs]

 Note: There is some logic that is maintained by Feed Streamer that does not allow messages to be both rejected and approved, or that automatically approves messages when they are associated to a group and so forth. This is kept by the Social TV client application and will not be applied when executed through this API.

11.4 Spaces

11.4.1 URL http://datahub:8089/directory/title/Socialize/Spaces/feed

Read spaces

GET /directory/title/Socialize/Spaces/feed => SPC_a5c7a8cc-4ec1-4388-8746-bf5373b04b6f Weekend Sports SPC_eec31892-7a24-4276 -9961-433163d88a06 Midnight News

11.4.2 Delete a space

DELETE /directory/title/Socialize/Spaces/ or

DELETE /directory/id/

11.4.3 Read space groups

GET /directory/title/Socialize/Spaces/Weekend Sports/Groups/feed => GRP_2d802dc7-a901-4431-ad2e- cb15ef5c7dc9 NBA GRP_9f56d7c2- d45d-4552-83d8-821e8d61451e EURO 2016

11.4.4 Read space sources

GET /directory/title/Socialize/Spaces/Weekend Sports/Sources/feed => SRC_c207c900-7f3d-45cc-8324- a65b8b3d6949 Lebron SRC_4aae1cc0-d14a-49dc-9699-ebc2488c4425 Golden State Warriors

11.4.5 (Un)Associate source to a space

POST /directory/title/Socialize/Spaces/Weekend Sports/Sources/feed[&remove=true] Content-Type: text/uri- list [Source URLs]

11.4.6 (Un)Associate group to a space

POST /directory/title/Socialize/Spaces/Weekend Sports/Groups/feed[&remove=true] Content-Type: text/uri-list [Group URLs]

11.5 Pagination By default, any of the above requests are limited to 50 items. When more items are available the element of the response will contain atom:link elements to next/prev/first/last pages, e.g.:

It is possible to get a number of items other than 50 by providing the “limit” argument to the request, e.g.:

GET /directory/title/Socialize/Sources/Lebron/feed?limit=3

Specifically for search queries, response contains totalResults element that holds the total number of items that result from the query.

12 Scene Design Scene design for Feed Streamer is very similar to standard scene design for Viz Trio, where control plugins are used to manage the transfer of data and items of data are identified by field identifiers. This section contains information about scene design issues that are specific to Feed Streamer: • Standard Field Identifiers • Scene Design Examples • Scene Design for Trio • Scene Design for Ticker • Social TV Plugins • Control Plugins

12.1 Standard Field Identifiers Most of the content of the messages in a Social TV feed can be accessed from the scene designs using the following standard field identifiers: • id: The Atom Id of the message. This is required when a payload is updated through the DataHub update service. • author: The name of the message author: for example, the username of the person who posted the original message in Twitter, Facebook etc. • thumbnail: An image associated with the message. Depending on the source of the message, it may either contain a picture of the author or a picture related to the subject of the message. You need to put an image in the container and also set the image location prefix in the image control plugin. • title: The message content. • summary: Some messages may include additional content in this field. Some RSS and Facebook items, for example, may include content in this field. • contributor: The name of the message’s source service/network. For example Facebook, Twitter or RSS. • image_url: The URL or path to image files that are part of the message. • video_url: The URL or path to video files that are part of the message. • audio_url: The URL or path to audio files that are part of the message. • media_type: The media item (e.g. video or image) if a message contains media. • enclosure: This field can contain a URL to an external website, or the URL or path to files that are part of the message but which are NOT image, video or audio files. • content: Some messages may contain extra non-standard information in this field, packed into a VDF payload document. For more about this, see Accessing VDF Payload Data. • geolocaiton: Some messages may include geolocation data. The format is on latitude and longitude. • feed: When moderating a source in Live Playout mode, always populate the ‘feed’ with the name of the current source. When moderating a group in Live Playout, populate the ‘feed’ with the name of the current group in the right-hand panel, and populate the ‘feed’ with the names of all sources this message belongs to, separating the source names with a comma.

 Note:

In general, designers should have a basic knowledge of the feed type they are designing scenes for, in order to decide which are the relevant fields for the desired scene.

12.2 Scene Design Examples An archive of scene design examples is provided when installing the Social TV Plugins, and can be found in

• 64 bit (x64) installer: C:\Program Files\Vizrt\Common\SocialTV • 32 bit (x86) installer: C:\Program Files (x86)\Vizrt\Common\SocialTV

12.3 Scene Design For Trio This section contains information about scene design issues that are specific to scene design for Trio: • Scene Presenting a Single Message • Scene Presenting Multiple Messages • Accessing VDF Payload Data

12.3.1 Scene Presenting a Single Message A scene presenting a single message can be achieved by using the Standard Field Identifiers. The following shows a scene tree in which the Standard Field Identifiers are used to control the message:

The resulting scene looks like this:

12.3.2 Scene Presenting Multiple Messages Scenes presenting multiple messages, are managed by adding the ControlList plugin to a parent container, and then inserting a series of subcontainers for the maximum number of actual items that will need to be displayed. You can optionally include a ControlHideonEmpty plugin in each of these subcontainers so that they will only be displayed if they contain data. For detailed information about the Control List and Control Hide On Empty plugins, see the Viz Artist User’s Guide. The following shows a scene tree in which the ControlList plugin is used to control multiple messages:

The resulting scene looks like this:

12.3.3 Accessing VDF Payload Data Some Feed Streamer items contain non-standard data that does not fit into the standard fields described in Standard Field Identifiers. In such cases, the data is delivered in the content field, packaged inside a VDF payload document. VDF (Viz Data Format) is a proprietary Vizrt data format used for transferring data between different Vizrt components and systems. A data set encoded in VDF is called a VDF payload (as opposed to a VDF model, which can be used to define the structure of the VDF payloads used in a particular application or context). You can find formal reference documentation for VDF on your Data Hub at:

http://data-hub-host-name:8089/doc/model.html

In order to access the data in a VDF payload document you need to use a ControlPayload plugin. The ControlPayload plugin unpacks the content of the payload document and makes it available as a normal set of fields to all the children of its container. The field names found in the VDF payload are used as field identifiers.

Poll Graphics A typical situation in which you might need to unpack payload data is the design of poll graphics based on data harvested from social media via Feed Streamer. Polls usually consist of questions with multiple choice answers and are usually visualized as pie charts or bar charts. It is therefore desirable to have the data made available in a form that is compatible with the visual data tool plugins. Poll data might typically arrive in a message’s content field, packed in a VDF payload document that looks something like this:

It’s Valentine’s Day, how you doin’? Hate it! Worst holiday ever|Love it! Wish it were every day|Thanks for the reminder, need to buy roses 238|189|46

The payload document contains three fields: • topic: the poll’s question • option: the multiple-choice answers • count: the number of results for each answer The scene tree shown below contains a ControlPayload plugin in which the Field Identifier property is set to content. The ControlPayload plugin is therefore able to access the payload document and make the three fields available to the controls in all its subcontainers.

The resulting scene looks like this:

12.4 Scene Design For Ticker Social TV scenes for Viz Ticker use the same Standard Field Identifiers as Viz Trio. General information about how to design ticker scenes is provided in the section ‘Design Conventions’ in the Viz Ticker User’s Guide.

12.5 Social TV Viz Plugins A set of Viz plugins are included with Social TV. These plugins are needed for integration with Viz Multichannel, as it is not yet directly integrated with Social TV. The plugins are not required for integration with Viz Trio, Viz Ticker or Viz Pilot, but they can be used in conjunction with these products, for example when an on-screen updated is required. Once installed, the plugins appear in Viz Artist in the Container Plugins tab in a Social TV folder. The Social TV Plugins are designed to work together with the Datapool plugins. The Social TV plugins share some Common Properties, and the unique details for each plugin are described in the subsequent sections:

• Common Properties • STV_GroupsReader • STV_HttpRecognizer • STV_MessagesReader • STV_PlaylistsReader • STV_SourcesEditor • STV_SourcesReader • STV_SplitAuthor • STV_TextHighlight • STV_WordCloud • VLC plugin

12.5.1 Common Properties Some properties are common to several plugins, so are described in this section. The plugins in this section are all intended to retrieve various kinds of data from the Data Hub and forward it to the DataPool. These plugins therefore all share the following common properties: • Data Hub Host: Host name of your Social TV Data Hub • Data Hub Port: Port number on which the Data Hub is listening. This is 8089 by default. • DP Field Name: Name of the DataPool field to which retrieved data will be sent. • Number of Records Field: The plugin keeps count of the number of records it retrieves from the Data Hub and sends the number to the DataPool along with the records. This property specifies the name of the DataPool variable to which the number of records is written.

• Post Update Action: An optional sequence of Viz and/or DataPool commands to be executed after the data has been retrieved. If you want to specify more than one command, then you must separate the commands with semicolons (;). In order to distinguish between Viz Commands and DataPool commands you must prefix Viz Commands by “0”. For example

0 RENDERER*STAGE START;

12.5.2 STV_GroupsReader

STV_GroupsReader retrieves all the groups defined in the Feed Streamer and forwards them to a DataPool field array.

Properties

The STV_GroupsReader plugin has the common properties described in Common Properties plus the following additional properties that allow you to filter the groups by name: • Filter by Name: switches filtering on/off • Include/Exclude Expression: specifies whether the groups specified in Filter Expression are to be included in the selection or excluded from it. • Filter Expression: specifies one or more group names. If more than one group name is specified in this field, they must be separated with commas (,). • Filter by Space: Switches filtering on/off • Filter by Space Expression: Specifies one or more Space names. If several Space names are specified in this field separate them with commas (,).

Example Here are some groups defined in the Feed Streamer:

In order to create a scene that looks like this:

The following scene tree must be created in Viz Artist:

12.5.3 STV_HttpRecognizer

STV_HTTPRecognizer recognizes and deals with HTTP links in text geometry. Messages from social media networks such as Twitter and Facebook may often contain links to other sites and resources. In many cases such links are not meaningful in a broadcast context.

This plugin recognizes such links and can hide them if required. It can also store the link URL in a Data Pool or shared memory variable.

Properties

The STV_HTTPRecognizer plugin has the following properties: • Hide Links: Specifies whether or not discovered links are to be hidden. • Variable: The name of the variable in which the URLs of discovered links are to be stored.

Example

12.5.4 STV_MessagesReader

STV_MessagesReader retrieves all the messages defined in the Feed Streamer and forwards them to a DataPool field array.

This structure is defined along with a number of other Social TV-related field structures in the configuration file

Windows 64-bit: C:\Program Files\vizrt\Viz3\config-SocialTV.dp Windows 32-bit: C:\Program Files(x86)\vizrt\Viz3\config-SocialTV.dp

Each message in the array has the following structure:

STV_Message = { string thumbnail; string author; string title; string category; string summary; string href; string contributor; string url; string image_url; string video_url; string audio_url; (??) string media_type; string geolocation; };

Properties

The STV_MessagesReader plugin has the common properties described in Common Properties plus the following additional properties: • DataHub Host: Host name of your Social TV Data Hub • DataHub Port: Port number on which the Data Hub is listening. This is 8089 by default. • DP Field Name: Name of the DataPool field to which retrieved data will be sent.

• Load Automatically: • If On, then messages are automatically retrieved at fixed intervals. An additional property field is displayed in which you can specify the interval (in seconds). • If Off, then messages are only retrieved when you click the Load button.

• Use Custom URI: The URI of the Data Hub • Group Name, Source Name, Provider Name: You can limit the selection to messages that: belong to specified groups, or come from specified sources or providers by entering strings in these fields. You can enter several values in each field if required, separated by commas. • Free Text Search: You can write a text search string in this field: the plugin will then only retrieve messages that match the string you enter. You can create complex search expressions by combining search strings using AND and OR operators. • Custom Sort: By default, retrieved messages are sorted by the order defined in the Feed Streamer client. When this parameter is enabled, a new parameter called Sort by becomes available that makes it possible to select from the following sorting options: Author, Contributor, Published Date, Summary and Title. • Sort Mode: This setting allows users to define items so they are sorted in Ascending or Descending order • Filter by: • All: will bring all the messages • Approved: will bring the Approved Messages • Rejected: will bring the Reject Messages

• Favorites: Retrieves only messages belonging to the Favorites group. • Show only geolocated messages: Retrieves only messages containing geolocation data. • From Message: The message item at which you want to start retrieving messages. • Number of Messages: The number of messages to retrieve. • Automatic Paging: If set to Off, then the plugin will retrieve messages from the same positions every time. If, for example, From Message is set to 1 and Number of Messages is set to 4, then messages 1-4 will be retrieved every time. If, however, Automatic Paging is set to 1, then the plugin will move on through the messages on each retrieval, selecting 1-4, then 5-8, then 9-12 and so on. • Paging Loop: When Automatic Paging is in use, this property determines what happens when all available messages have been retrieved. If it is set to Off, then no more messages are retrieved. If it is set to On, then the plugin returns to the beginning.

 Note:

When retrieving items from a group (or only approved items from a source) any Items added to the list after the initial loop cycle will not display until the next loop.

• Show Image Download Parameters: If you set this to On then you can define a default image to be displayed with messages that do not include a thumbnail image. • Images Folder: The folder location that images will be downloaded to • Read Content, Content Field Name: Set Read Content to On if you want the plugin to read content from a VDF payload embedded in the message. You must then specify the name of

the DataPool field to which the payload content is to be written. In order for the plugin to be able to read the payload you must have created a config DP defining the fields required to hold the payload content. • Use Proxy: Set to On if you need to use a proxy to download additional images that are not downloaded with the messages. Additional properties are then displayed in which you can set the proxy details. • Use Shared Memory: This will send all the data retrieved to a shared memory structure, in addition to Data Pool

Example In order to create a scene that looks like this:

The following scene tree must be created in Viz Artist:

Example with VDF Payload In order to create a scene that makes use of poll data embedded in VDF payloads, like this one:

The following scene tree must be created in Viz Artist:

12.5.5 STV_PlaylistsReader

STV_PlaylistsReader retrieves the list of pages in a Viz Trio or Viz Pilot/MOS playlist and forwards them to a DataPool field array. It is intended for use in interactive applications.

This structure is defined along with a number of other Social TV-related field structures in the configuration file Windows 64-bit: C:\Program Files\vizrt\Viz3\config-SocialTV.dp

Windows 32-bit: C:\Program Files(x86)\vizrt\Viz3\config-SocialTV.dp

The config file includes a base type of STV_MSE_Page. Each page in the array has the following structure:

STV_MSE_Page = { string Name; string Description; string Template; string Path; };

The fields contain the following information: • Name: The page name • Description: The description in the playlist (the description is defined in the ControlObjectPlugin at the top of the scene template). • Template: The description in the template

Properties

The STV_PlaylistsReader plugin has the following properties: • MSE Host: The Media Sequencer host from which playlists are to be retrieved • DP Field Name: The name of the DataPool field to which retrieved playlists are to be forwarded • Show Name: The name of a Viz Trio show from which the playlist is to be retrieved. If no name is specified then a Content Pilot/MOS playlist is retrieved • Page to Take: The index of the page to which a control button action is to be applied (see Control buttons below). Pages are numbered from 0 • Playlist: The name of the playlist to retrieve

• Group Name: The name of the group of pages to retrieve • Profile: The name of the profile to use. The profile you specify must have been defined in the Media Sequencer

Control Buttons The following control buttons are displayed at the bottom of the properties form: • Read Playlist: Reads the playlist • Take, Take Out, Continue: Applies the specified action to the page specified with the Page to Take property

Example By creating the following scene tree in Viz Artist:

Then using a Viz Trio playlist as follows:

You can produce the following scene:

12.5.6 STV_SourcesEditor

STV_SourcesEditor is a container plugin that enables creating sources in Feed Streamer and modifying existing sources’ parameters. Properties

STV_SourcesEditor has the following properties: • DataHub Host: Host name of your Social TV DataHub • DataHub Port: Port number on which the DataHub is listening. This is 8089 by default. • Source Name: Name of the source to be created or modified.

• Modify Global Parameters: Shows the global parameters common to all the sources. If this is set to on, the following parameters are visible:

• Active: The source is active if ‘on’ is selected, otherwise it is inactive. • Max Number of Items: This is the maximum amount of items the system should keep for this source. • Max Life Span (in days): The number of days the system should keep the items. • Reflection: When ‘on’, the system will replicate the situation in the incoming feed. For example, when reading an RSS feed, posts that are deleted from an the feed will trigger the corresponding item to be deleted from the source. • Auto Approve: If ‘on’, all incoming items will be automatically approved. • Source Type: This determines the type of source to be created. The options are Twitter, Facebook, Instagram and JSON/XML.

Twitter

• Search Term: The term the source searches for among tweets. • User Search: If 'on', the search will take into account the addressee (To User) and/or the author (From User) of the tweet. • From/To User: These parameters are related to the User Search. • Filter by Type: When ‘on’, the source will selectively filter those tweets by their attached media. • With Text: Related to ‘Filter By Type’. When ‘on’, the created source will only retrieve tweets with text. • With Image: Related to ‘Filter By Type’. When ‘on’, the created source will only retrieve tweets with images. • With Vine Video: Related to ‘Filter By Type’. When ‘on’, the created source will only retrieve tweets with Vine videos. • Filter By Geolocation: If ‘on’, the source will filter by geolocation.

• Only Geolocated: If ‘on’, all tweets containing geolocation will be included in the feed. • Location: This field contains the location from where to collect the tweets. If left empty, no tweets with location data will be collected. • Radius: This is the radius (in kilometers) from the location from where tweets will be collected.

Facebook • Search User or Page Name: Defines the term to search in Facebook, either for a user or page name.

• • Filter By Type: Allows filtering by Posts, Links, Photos or Videos. • Include Posts: Specifies that the resulting items should include posts. • Include Links: Specifies that the resulting items should include links. • Include Photos: Specifies that the resulting items should include photos. • Include Videos: Specifies that the resulting items should include videos. • Bring Only: Specifies whether to retrieve all polls or albums from a page. • Include Posts From: Allows the retrieval of all posts, only the page owner’s posts or the posts posted by other users on the page. • Profanity Filter: Specifies whether the source should filter profanities.

Instagram In this mode, STV_SourceEditor reads an existing source and modifies the tag to be searched. It only works in ‘Search Tag” mode. The ‘Tag’ parameter specifies the tag to be searched.

JSON/XML Many of the readers included in Feed Streamer are of the type XML_JSON. Examples of these readers are BBC, SpredFast, Flowics, and more. This mode only allows for editing existing source’s parameters; it does not allow for the creation of a new source. The plugin reads the source’s parameters before modifying those specified in the plugin parameters, as shown below.

Take the example of creating a BBC source that appears as such:

12.5.7 STV_SourcesReader

STV_SourcesReader retrieves all the sources defined in the Feed Streamer and forwards them to a DataPool field array.

Properties

The STV_SourcesReader plugin has the common properties described in Common Properties plus the following additional properties: • Filter by lets you choose the kind of filtering you require: • Title: filter by the name given to the source when it was created in the Feed Streamer • Provider: filter by the name of the source type on which the source is based, such as Facebook or Flickr

• Include/Exclude Expression specifies whether sources that match a search string are to be included in the selection or excluded from it. • Filter Expression specifies one or more text strings to use as filters. If more than one string is specified in this field, they must be separated by commas (,). • Space switches filtering on/off • Space Expression specifies one or more Space names. If more than one Space name is specified in this field, they must be separated by commas (,).

Example Here are some sources defined in the Feed Streamer:

In order to create a scene that looks like this:

The following scene tree must be created in Viz Artist:

12.5.8 STV_SplitAuthor

When STV_SplitAuthor is placed on a text container, the plugin recognizes the @ character from the text and lets you hide either the user ID or User Name of the author.

 Note: You must send text to the “author” property of this plugin using the ControlParameter.

An example Viz Artist scene is shown below:

The resulting scene, with user details hidden, is as follows:

12.5.9 STV_TextHighlight

Coloring text containing special characters When STV_TextHighlight is placed on a text container, the plugin recognizes certain characters and lets you change the color of any word containing that character (for example: #tags @User http://).

 Note: You must send text to the “text” property of this plugin using the ControlParameter.

An example Viz Artist scene is shown below:

The resulting scene, with important information highlighted, is as follows:

Emoji

The Emoji option allows users to visualize emojis in a text. All emojis are a list of characters that are replaced by images.

List of parameters: Disable/Enable Images: Default/Custom When using default the plugin will use the images located under: C:\Program Files\Vizrt\Viz3\plugin\data\TextHighlight\72x72 When using custom the user can define a path to their own images (Note that the custom path should be accessible to all machines running VizEngine, including Trio and Preview engines.) Word Folder: allows the user to define a folder of images containing words that should be replaced by emojis Ignore List: allows the user to define a list of characters that should be ignored when replacing with emojis Word List Separator: character to be used as a separator of the list of words to replace by emoji Word List: list of words to be replaced by emojis

TextFX

The Text FX option allows users to apply similar effects as Text FX plugins when using emojis. For more information please refer to section ‘TextFX’ in the Viz Artist User’s Guide.

12.5.10 STV_WordCloud STV_WorldCloud plugin allows users to read items from the DataHub that are compatible with the plugin. Examples are feeds from Never.no World Cloud, Spredfast Top Terms, etc. The plugin then visualizes the data in the form of a Word Cloud. The plugin must be placed on top of a text geometry.

The STV_WordCloud plugin has the properties described in Common Properties, in addition to the following properties: Parameters Font Type: (Regular)(Complex) Regular: treats fonts as Viz Fonts Complex: should be used when working with complex script fonts such as Arabic or Hebrew Load Automatically: if ‘on’, messages are automatically retrieved at fixed intervals. An additional property field is displayed allowing you to specify the interval (in seconds). If ‘off’, messages are only retrieved when the Load button is clicked. Group Name, Source Name, Provider Name: enter strings in these fields in order to limit the selection to messages that belong to specific groups or are from specified sources or providers. You can enter several values in each field separated by commas, if required. Free Text Search: You can write a text search string in this field: the plugin will then only retrieve messages that match the string you enter. You can create complex search expressions by combining search strings using AND and OR operators. Custom Sort: By default, retrieved messages are sorted by the order defined in the Feed Streamer client. In this parameter, it is possible to exchange the sort with something else, for example published to sort items based on published time in descending order (most recent first) and \published to sort items by published time in ascending order (oldest message first) Messages

All: will bring all the messages Approved: will bring the Approved Messages Rejected: will bring the Reject Messages Favorites: retrieves only messages belonging to the Favorites group. Area Width: width of Word Cloud visualization Area Height: height of Word Cloud visualization Margin: margin between words Layout: (Square) will arrange words in a square and (Round) will arrange words in a round layout Seed: will apply some randomization value to the layout of words Number of Words: limit the number of words to use in the Word Cloud visualization (will use the highest volume words) Color: when set to image will allow user to apply an image for coloring each word in the cloud Shared Memory: this will send all the data retrieved to a shared memory structure, in addition to Data Pool Scale Ranks: allows scaling words based on ranking Clip Ranks: allows clipping words with a value lower or higher than what is defined in the plugin

12.5.11 VLC plugin The VLC plugin is a media player plugin that makes use of VLC media player technology. The plugin can play any media that can play in the VLC player. A function plugin, VLC should be placed on a group container for playing the media over a rectangle or on a geometry object. The plugin requires a VLC player to be installed on the machine.

 Do not apply texture to a VLC plugin container.

VLC Plugin Parameters

• Media: Name of the media to be played. It can be a link, file or other formats supported by VLC player • Loop: When set to 'on', the media will play repeatedly

• Audio Enabled: When set to 'on', the sound from the selected media will be played during playback. When set 'off', the sound is muted.

 The VLC Player can only play out embedded audio in a clip directly through the MATROX card. This is supported in Viz Artist 3.7.2 and later.

• Volume: If Audio is enabled, this parameter will control the volume level. • Logging: The plugin will write log information into a file named vlc.log, residing in the Viz3 folder. • Set Clip Time: Set the clip playback time (in milliseconds). Default value will be the clip length. • Play on Load: If set to 'on', the clip will automatically play when loading the scene. When set to 'off', the clip will not play until clicking the play button. • Use Proxy: When set to 'off' no proxy will be used. When set to 'on', additional parameters will be enabled such as, for example: • Proxy Host: The name of the proxy machine

• Proxy Port: Proxy port, as defined on the proxy machine. • Proxy User: User name with permission to access the network via the proxy machine. • Proxy Password: Password for the proxy user. • Play: Play the media from the beginning. • Stop: Stop playing the media. The current frame will be displayed. It is not possible to resume playing the media after has been stopped. • Pause: Pause the clip at the current frame. • Continue: Continue playing the media from the current frame after it was paused.

12.6 Control Plugins For general information about how to use control plugins in scene designs, see Adding Control Plugins in the Viz Trio User’s Guide. You can also refer to the descriptions and examples of creating scene designs for Social TV Plugins in the Viz Artist User’s Guide.

13 Troubleshooting This section contains typical troubleshooting questions and answers that may arise while installing, configuring or using the Feed Streamer solution. If you do not find answers to your issues, please contact your local Vizrt representative and submit a Customer Support Request. This section contains information on the following topics: • Troubleshooting Tips • Known Limitations

13.1 Troubleshooting Tips

• Data Hub installation freezes for a long time • Cannot connect to Data Hub, or can’t see data in Feed Streamer • Feed Streamer is slow or unsuccessful when fetching images • New messages stop arriving • No messages ever arrived • When using STV_MessagesReader plugin, I cannot see the thumbnails • Feed Streamer and Data Hub run, and can define sources, but no messages arrive • Cannot login to Facebook, Instagram and Twitter on a Windows Server 2008 machine • I modified my plugin config file and cannot get new messages or add sources • Search on Moderation Panel using special characters doesn’t return expected results • Cannot create Trio pages • Data Hub service crashed and no space left on C drive • Database file getting large and filling hard drive space • Cannot add Twitter account (the IE window doesn’t appear) • Media files not saving in configured folder • Pusher service not starting • Ticker Feed Service does not install

13.1.1 Data Hub installation freezes for a long time It is a known issue that the installation of Data Hub freezes (see image below). Please be patient and it should eventually complete (after about 10 minutes).

13.1.2 Cannot connect to Data Hub, or can’t see data in Feed Streamer 1. Verify that the Data Hub host name or IP is properly configured in the applications. 2. In your web browser try to access the page: http://\[DataHubHost]:8089/search? q=socialize a. If this returns a feed with title “Open Search”, please contact Vizrt support (submit a Customer Support Request). b. If this returns a page with error information, please try to reinstall Data Hub. Contact support if the problem remains. c. Proceed to next step if you get a page not found error from the browser. 3. Verify that firewall allows HTTP connections to port 8089 of the Data Hub machine. 4. Check that the following services on the server machine are running, and try to start if not: a. Apache CouchDB b. CouchDB Lucene c. Vizrt Viz DataHub Note that Apache CouchDB has to be running prior to starting Vizrt Viz Data Hub. Try to Reinstall Data Hub if not all services can start. Contact support if the problem remains following the new installation. Contact support if all services are running but the problem remains.

13.1.3 Feed Streamer is slow or unsuccessful when fetching images If fetching images is slow, it is probably due to a slow internet connection. If fetching images is unsuccessful, there is probably a problem with the internet connection. Verify that the machine is connected to the internet (either directly or via a proxy). If the machine is connected to the internet via proxy, verify the proxy connection parameters in Feed Streamer Shared and Local Settings.

13.1.4 New messages stop arriving Restart the Data Pusher service on the Data Hub machine.

13.1.5 No messages ever arrived Verify that the Data Pusher service on the Data Hub machine is running. Verify that the Data Hub machine is connected to the internet (either directly or via a proxy). If the machine is connected to the internet via proxy, verify the Data Pusher proxy connection parameters in Feed Streamer Shared and Local Settings.

13.1.6 When using STV_MessagesReader plugin, I cannot see the thumbnails In the parameters of the STV_MessagesReader plugin: • Check the Data Hub Host and Port settings. The host name used should be defined in the “hosts” file or set in the plugin using the actual ip or machine name. • Check the Images Folder setting. Verify that the folder exists and that you have access to this folder from the engines. Verify that the image pointed to by your DataPool plugin (typically DataImage) exists in the folder.

13.1.7 Feed Streamer and Data Hub run, and can define sources, but no messages arrive If you are using Windows Server 2008, you need to upgrade to the latest version of Internet Explorer (IE9 or later). If this source is based on a custom created reader, try to create a source based on one of the pre- configured source types. Consult Vizrt support with the results.

13.1.8 Cannot login to Facebook, Instagram and Twitter on a Windows Server 2008 machine This is because Internet Explorer is defined with the maximum security settings. Change the security settings as follows: 1. Open the Server Manager Tool 2. Click Configure IE ESC in the security information panel 3. Turn off IE ESC for both Administrators and Users 4. Click OK 5. A warning that IE ESC was disabled appears the next time you open Internet Explorer. Select not to display the message in the future.

13.1.9 I modified my plugin config file and cannot get new messages or add sources After any change to config files you must ensure that the updated file is distributed to all client and server machines, and then restart the Data Pusher service.

 Note: When modifying the plugin config file, it is typically the XML file under the ‘plugins‘ subfolder.

13.1.10 Search on Moderation Panel using special characters doesn’t return expected results Terms that include the at (@) or hash (#) characters result in a case-sensitive search, thus you will find the messages that contained exactly the term written.

13.1.11 Cannot create Trio pages Feed Streamer only supports the 4-layer Sequencer Engine element structure, which means that with old Trio versions the show has to be created with variant/concepts option enabled.

13.1.12 Data Hub service crashed and no space left on C drive This is the procedure to move the database files to a location other than the default (C drive). You can choose a different location during installation, but follow this procedure if you wish to do so after installation. 1. On a drive that has enough space, create a new folder 2. Stop the Apache CouchDB service 3. Copy all files from C:\Program Files (x86)\Apache Software Foundation\CouchDB\var\lib\couchdb to the new folder 4. Edit C:\Program Files (x86)\Apache Software Foundation\CouchDB\etc\couchdb\local.ini and set database_dir to point to the new folder. 5. Add an entry below view_index_dir and point it to the same location 6. Start the Apache CouchDB service

13.1.13 Database file getting large and filling hard drive space Scheduled cleanups are performed automatically if the database file gets above a certain fragmentation size. It is also possible to force the cleanup in order to free up space, however DO NOT do this cleanup activity when in production. Depending on the size of the database the cleanup might take a long time (hours). To force a cleanup: 1. Go to the Feed Streamer folder on the server machine • Windows 64-bit: C:\Program Files\vizrt\Viz Feed Streamer • Windows 32-bit: C:\Program Files(x86)\vizrt\Viz Feed Streamer 2. Run the batch file: • compact.bat

13.1.14 Cannot add Twitter account (the IE window doesn’t appear) Check that the PC time and date are correctly set up.

13.1.15 Media files not saving in configured folder The WMI (Windows Management Instrumentation) Service must be enabled in order for media files to correctly store in the configured media folder. Note that WMI is enabled automatically on Windows 7 and Windows XP.

13.1.16 Pusher service not starting When the pusher service fails to start, verify that pusher console application is not running.

 Note: The Pusher Service will restart if it encounters an error. It will restart a second time in the event of a second error, but in the event of subsequent errors, it will quit.

13.1.17 Ticker Feed Service does not install

This service is a java jar file started from the installation path of FeedStreamer, normally C: \Program Files (x86)\Vizrt\Viz Feed Streamer\TickerFeedService.jar. If this service fails to start during the installation, please try this:

• On a command console, write "java -version" and verify that the response is something like java version "1.8.0_144". The service needs version 1.8 or above. • If there are several java versions on the computer, set the JAVA_HOME environment variable to the location of java 1.8. • On the command line, write "set JAVA_HOME" and check that it points to the right java version, for instance "C:\Program Files\Java\jre1.8.0_144". • If JAVA_HOME does note exist, set it:

• Run the FeedStreamer exe installer as administrator (right click > Run as Administrator), or if that fails, • Download the individual VizTickerFeedService.1.5.0.xxxx.msi and try that one. • If this doesn't work, check the system event logs for this event (View event logs > Windows Logs > Application) and export the relevant ones.

If the installation fails, the service can be downloaded and started manually from the console: • Download the package from here: http://package.vizrt.internal/Package/TickerFeedService/ 1.5.0 • Place the TickerFeedService.jar file somewhere on the disk • Open a console window and navigate to the location of the jar file • Start the service by writing "java -jar TickerFeedService.jar"

13.2 Known Limitations • Resending the current group to ticker carousel will not reset its messages number of runs. • After installing Feed Streamer 1.2 using the bundle installer, any files that were modified or added by the user will be copied to a folder named BACKUP_ (under the Feed Streamer folder). To retrieve any of the files, copy them back into the Feed Streamer installation folder.