Back History
Network Show

<div id="Text">
==Network Show==

This window contains the configuration details for a particular network show and is accessed from the [EZ-NET] window.

[image||{UP}NetworkShow/NetworkShow1.png]

The above screen shot represents the default view of the network show.  

Across the top of the window you will see the name of the network show and the current status.

There are three tabs ("Scheduling", "Copy" and "EzScript").  

[anchor|#copy]
===Copy===

By default, the "Copy" tab is selected displaying the list of [Copy] associated with this network show.  This provides you the ability to make changes to [Copy] in the event of changes occurring after the schedule was imported.  (See [CopyList].)

===Scheduling===

[image||{UP}NetworkShow/NetworkShow2.png]

In the less often times that you need to integrate [EZ-NET] differently than the defaults provided, you can utilize the "Scheduling" tab to control the behavior of how [EZ-NET] will integrate into your existing [Log] pipeline.

'''Defaults'''

* '''Avail Type'''{br}By default, [EZ-NET] automatically creates a unique [AvailType] so that you can utilize these in [Templates]/[Formats] to pre-assign (pledge) the placement that you are contracted to do so.{br}{br}If, however, you'd like to "mix" network spots with your regular spots, you can do so by selecting a different (non-default) [AvailType].{br}{br}((('''CS''' ''DO NOT CHANGE THIS without significant consideration.  Changing the [AvailType] value to something "you already have" may save you some time and effort in the beginning, but you will lose much of what EZ-NET has to offer in the way of saving you time and effort every single day by not using the [AvailType] created specifically for this show.  In other words, investing now in modifying your [Templates]/[Formats] to use the [AvailTypes] created for this show will save you countless hours going forward by effectively removing any work related to "scheduling" these shows on [Logs], each and every single day.  With that stated, when choosing a different [AvailType], you should really consider configuring the "Show separation (optional)" section; otherwise, you may end up with undesired separation since, by default, [EZ-NET] doesn't need to worry about this because of the dedicated [AvailTypes] that it utilizes.''))){br}{br}
* '''Start/End Time'''{br}Some shows provide the additional option to "override" the start and end time; this is primarily used to support networks that do not specify the start and end times.
** '''Cumulus'''{br}In addition to the default configuration options, Cumulus contains the ability to specify a start and end hours.  This is necessary because the Cumulus network does not provide this information, so you are required to do so.

'''Show separation (optional)'''

* '''Type'''{br}The type of separation; Minute (default) - Will enforce a customer separation for n number of minutes where n is the value specified in the Amount field, Break - Will enforce a customer separation for n number of breaks where n is the value specified in the Amount field.
* '''Amount'''{br}The number in this field is used by the Type to determine the actual amount of separation.

((('''CS''' ''When leaving the [AvailType] to the default created and leveraging this on [Logs]/[Templates], you should really consider leaving the separation type set to None in order to get the best possible results.'')))


[anchor|#ezscript]
===EzScript===

====Variables====

It is possible to apply ''EzScript'' during the import process in order to affect the behavior of how RadioTraffic will translate the schedule provided into a schedule that will be used.  The ''EzScript'' related to this show (if any) is located on the ''EzScript'' tab.

The following variable(s) are available:

* '''mergedayparts'''{br}{br} Normally we import the schedule "as-is".  If the network has defined the schedule in such a way that the times are pretty specific (especially true with regards to ''pledge times''), RadioTraffic will import this so that the times are pretty specific (again, "as-is").  If you wish to override this behavior, you can specify the '''mergedayparts''' variable in the script and set the value to something other than zero.  This will cause the import process to ignore the specific dayparts defined, determining the earliest and latest times and use those results to determine the overall start and end time of all of the scheduled items.{br}{br}Examples:{br}{br}mergedayparts = 1{br}{br}LET mergedayparts = 1{br}{br}((('''CS''' Currently, the ''mergedayparts'' variable is only enabled / available / active when importing schedules from Premiere Radio Networks, Westwood One, United Stations Networks, ESPN, Compass Media Networks and ADLarge Media and is available as of version 1719. The usage of the LET keyword is optional.)))

* '''forcewholeday'''{br}{br} Normally we import the schedule "as-is".  If the network has defined the schedule in such a way that the times are pretty specific (especially true with regards to ''pledge times''), RadioTraffic will import this so that the times are pretty specific (again, "as-is").  If you wish to override this behavior, you can specify the '''forcewholeday''' variable in the script and set the value to something other than zero.  This will cause the import process to ignore the specific dayparts defined, utilizing midnight to midnight as the overall start and end time of all of the scheduled items.{br}{br}Examples:{br}{br}forcewholeday = 1{br}{br}LET forcewholeday = 1{br}{br}((('''CS''' Currently, the ''forcewholeday'' variable is only enabled / available / active when importing schedules from Premiere Radio Networks, Westwood One, United Stations Networks, ESPN, Compass Media Networks and ADLarge Media and is available as of version 1752. The usage of the LET keyword is optional.)))


====Exclusions====

It is possible to apply ''EzScript'' during the import process in order to affect exclusions to reduce what is actually imported.  The ''EzScript'' related to this show (if any) is located on the ''EzScript'' tab.

The ''EzScript'' is built in such a way that you will define, on a per day of the week basis, what will be excluded.  Some examples include:

* Set Tuesday Exclude Times ("7:05", "8:05", "17:05")
* Set Wednesday Exclude Breaks ("Hr1Br1", "Hr1Br2")
* Set Thursday Exclude Hours (10, 11, 12, 13, 14, 15)
* Set Sunday Exclude All

By default, all exclusions are "off".

The ''day of the week'' after the word ''Set'' is optional.  If not included, whatever is excluded is applied to all days of the week.

The ''Set'' statement is pretty flexible and supports several optional target types (''Times'', ''Breaks'', ''Hours'', ''First'', ''Last'' and ''All''). The definitions for each are:

Set ''DayOfWeek'' Exclude Times (''"time"'',''"time"''){br}
Set ''DayOfWeek'' Exclude Breaks (''"value"'',''"value"''){br}
Set ''DayOfWeek'' Exclude Hours (''number'',''number''){br}
Set ''DayOfWeek'' Exclude All<!--Set ''DayOfWeek'' Exclude First ''number''{br}
Set ''DayOfWeek'' Exclude Last ''number''{br}-->

''DayOfWeek'' is the day of the week to apply the exclusion; valid values are ''Monday'', ''Tuesday'', ''Wednesday'', ''Thursday'', ''Friday'', ''Saturday'' and ''Sunday''.  This keyword is optional; if excluded, the ''Exclude'' is applied to all days of the week.

The ''Times'', ''Breaks'' and ''Hours'' versions must contain parenthesis around a "list of stuff".  The actual list can be "empty"; which would cause that particular day of the week to be reset to the default for the particular target type.

The individual items, if specified, for ''Times'' must be a comma-separated list of __'''quoted times'''__.  The actual format of these times follows the same rules for the rest of the software.  (See [Common|Common UI Behaviors].)

The individual items, if specified, for ''Breaks'' must be a comma-separated list of __'''quoted values'''__ that matches how the network is specifying "breaks" (usually referred to as "pledgetime").

The individual items, if specified, for ''Hours'' must be a comma-separated list of __'''non-quoted numbers'''__ that are between 0 and 23 (24-hour format).

<!--The ''First'' and ''Last'' versions require a number starting at 0.  If 0, this resets the specified day of the week for this target type back to the default.  Any other number will, during the processing of the import, remove the first/last n (where n is the number entered) items from the beginning/end of the day of the week being processed.-->The ''All'' version is included to make it easy to completely ignore a particular day of the week altogether.

If any syntax errors exist, a message stating so will be presented during the running of the ''EzScript'' (during the import process).  Use the errors to assist in correcting any problem in the ''EzScript'' and try again.

If a particular exclusion is attempted against a show where the pledge time column doesn't "make sense", the exclusion is ignored.

((('''CS''' It is now possible to use the "Verify..." button to review the syntactical correctness of the script; this tool simply reviews the correctness of the "words" and overall "punctuation".  This tool does not, in any way, guarantee any sort of successful (or failure) result of the actual execution of the script.)))

<sub>''EzScript'' is powered by ''ShinyScript'' from Shiny Stone Digital and Design.</sub>

</div>
<DIV class=transcludedpage>
  <div id="Side">{toc}

{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
{br}
</div>
</div>

<SCRIPT type=text/javascript> 
   var navItem = document.getElementById('ManualTab');
   navItem.className = 'active';
</SCRIPT>
RadioTraffic.com

Software and services for the radio industry.

Network Show
