EditDigilink-Xtreme
backEditIntroduction
WORK IN PROGRESS - Please understand that we are actively rewriting much of our documentation and this page is currently "under construction"; if there's anything that you'd like to see added to and/or expanded upon, please let us know by
sending us a smile.
RadioTraffic converts to a specific Digilink-Xtreme log format.
EditStation Configuration
To configure RadioTraffic to work with Digilink-Xtreme, you will first need modify the station configuration to utilize Digilink-Xtreme as the automation system. In the administration module, open 'Stations'. Select the station you want to configure and double click. Once the station configuration is visible, select the 'Files' tab. Select the 'Product' to Digilink-Xtreme using the drop down selection tool. The 'Automation Log Path' is where RadioTraffic will export the log to, so set this to the file system folder that Digilink-Xtreme will pull the file from.
EditCart Numbers
Digilink-Xtreme limits cart numbers to 8 characters. If the cart number is missing, "*MISSING" will be used.
EditCategories
Categories are not used with regard to Digilink-Xtreme.
EditAutomation Commands
Automation commands are exported as cart numbers.
EditLog Notes
Log Notes are currently not exported.
EditPrograms
Programs are currently not exported.
EditAvails/Breaks
Avail markers do not export and are used strictly inside of RT as a means of scheduling.
EditLog Reconciliation
We also support automatic log reconciliation for the as-play file. To configure this feature, you need to determine where these files are located on your network and use that path to configure the "Aired Log Path". The filename to import should be named SpotLog.dig and you will need to use Digilink-Xtreme to make sure this file is up to date. RadioTraffic will look into this file and pull the information out for the particular log date being reconciled. If no spots exist matching the log date, no spots will be automatically reconciled.
The specific SpotLog.dig format that we currently support requires that:
- Cart # : Columns 4-11 (8 chars)
- Description : Columns 13-36 (24 chars)
- Time : Columns 54-62 (8 chars formatted as HH MM SS)
The other information contained in the SpotLog.dig file are not used by our system; we just need to know what cart number and time that it aired. We also use the description column if, for whatever reason, we are unable to match the cart number so that it gives you something more to diagnose with other than "just the cart number".
We are aware that there seems to be multiple ways to create the SpotLog.dig file; however, we currently have no information to share as to the specifics as to how these differences can be controlled. You will need to take care when creating the SpotLog.dig file so that it can be consumed by our system for the purpose of reconciliation.
You can also use the View->Raw Aired Log menu item in the log editor to verify that the SpotLog.dig file matches what we are expecting. This basically is a window into how we slice-and-dice the aired file for importing. If the cart number, description and time columns don't appear as a single column; it definitely is not going to be able to be utilized.
If anyone would like to share this information with us as to how to create the correct type of SpotLog.dig format, we will be more than happy to include it in this documentation.
EditFAQ
TODO Add any questions as they come up to this section.
EditAdditional Information
TODO What other tidbits of information might be useful related to this subject.