We’re back from our summer break and returning with a use case example: when to use GSelector’s dayparts versus hour restrictions. We know that we can always isolate scheduling attributes, but what if we wanted additional control over a specific period? For this video, we outlined examples of both dayparts and hour restrictions and when to get more granular. In addition, we provided unique scenarios to implement better scheduling practices.
Starting with dayparts, users can define their dayparts via Setup | Dayparts. Per the example provided, a user wanted to block a collection of songs from specific dayparts, some of which expand across hours included in another daypart. You can define you dayparts from the Definition subtab, as well as combing similar dayparts by repeating Group names. If you had a second group of dayparts that were treated differently than your primary dayparts, you may want to investigate utilizing Regions. For example, “If ‘Happy Birthday’ plays Friday at 3pm, do you care if it plays again at 3pm Saturday? What about Saturday at 3pm versus Sunday at 3pm?” Once you’ve defined your dayparts, assign them via Setup | Dayparts | Assignment.
If you’re looking to isolate songs across hours included within multiple dayparts, then switch to the Hours workflow via Setup | Hours or simply use the quick Hour Restriction workspace to add, edit or delete hour restrictions. For example, if you wanted to ban a song or sweeper from 9am – 5pm (“At Work Only”), then you could create an hour restriction, banning all hours except 9am – 5pm.
Once you have defined your hour restriction or dayparts, now it’s time to assign a scheduling technique to an attribute. Either block the attribute all together via Goals | Balance | Attributes | Select your daypart and ban the attribute or isolate songs/links via the Library | Browse List and use the Multi Song Changer to apply an hour restriction to a selection of songs. Since we’re applying scheduling techniques, why not get creative and utilize advanced scheduling techniques like the Clocks Constraints or Content? From Clocks | Constraints, create a new constraint that will ban or only schedule a certain attribute. Or use Goals | Content to define an attribute’s minimum schedule or maximum. This way, you don’t have to constantly update your hour restrictions or Multi Song Changer grouped songs, instead, once you add a new song with the defined Content attribute, GSelector already will handle the heavy lifting for you.
If you’re looking for additional “Back to Basics” videos, don’t forget to check out our extensive list of videos and how to’s via the RCS Live Archive: https://www.rcsworks.com/rcs-live . There are videos breaking down multiple GSelector techniques, as well as how to add songs, edit clocks, and more. If you want to ask your questions live in real time, don’t forget to tune in Thursday at 11am ET on your platform of choice: Facebook, Twitch, Twitter Live or YouTube!