Script Upload To Website

Burli includes an export feature for sending completed broadcast scripts to a website or other FTP location. This is NOT formatted export of fully-formatted HTML pages, but export of existing script data in a configurable text format to a pre-defined location.

Scripts can be exported as plain text to a web server or any FTP location.

Because almost all news websites today are produced using some sort of a content-management system (CMS) or scripting engine which imports, formats and refreshes web content, Burli does NOT export completely-formed web pages. There is simply no point. Instead this system creates plain-text, custom formatted files that almost any CMS will import with ease.

How it works

  1. Burli asks the user which stories from a given script it should upload (default is all).
  2. It then creates a single plain text (.txt) file containing the text from each of the selected items, in order, with a separator (by default ——–) between each.
  3. The resulting file is then FTP’d using Burli’s own FTP client to a pre-defined location as specified in main.ini.

User interface

To use the feature, a user right-clicks the tab for an existing script, then chooses ‘Export to’ menu option (see image above), then chooses ‘Web server…’. A dialogue box appears:

Web Server script upload screen.

The stories in the left-hand list come from the source script in the order they appear in the script. By default they are all checked. The destinations in the right-hand list are derived from pre-configured settings. By default none are checked.

After the user presses OK, Burli displays its Task Information dialogue box to show the upload progress — on a fast broadband connection the upload time will be almost instantaneous and the information may disappear before you can read it.

Configuring text output and destination

The destinations the user sees in the right-hand list come from settings the System Administrator places in the file main.ini. The settings go in a new section of the file called Web Export. The section can be placed anywhere in the file.

Destination[x]=[friendly name]~[ftp server]~[ftp username]~[ftp password]~[ftp path]~[filename]

[x] is a sequential number, starting at 1
[friendly name] is the descriptive name for the destination, and is displayed the dialogue box above (e.g. ‘1700 radio news’)
[ftp server] is the host name or IP address for the FTP server
[ftp username] is the username to login to the FTP site
[ftp password] is the password to login to the FTP site
[ftp path] is the path on the FTP server where to store the file
[filename] is the filename in the destination FTP path
[startstring] is a string (one or multiple characters) that defines the start of text within a script to be excluded from the upload
[stopstring] is a string (one or multiple characters) that defines the end of text within a script to be excluded from the upload
[separatorstring] is a string that defines the text that separates each story in the single file that is uploaded – note, may contain [cr] to represent carriage return, and [lf] to represent linefeed

Here is an example:

Destination1=1700 ~/usr/local/www/vhosts/news/htdocs/misc/~1700Bully.txt
Destination2=1800 ~/usr/local/www/vhosts/news/htdocs/misc/~1800Bully.txt

Multiple Simultaneous Uploads

If the users selects multiple destination files, Burli will initiate a separate instance of the FTP upload engine. Therefore, it is important to ensure that the FTP server will accept multiple simultaneous connections from the same username and password. If it cannot, users will have to upload to the destinations one at a time