This week, we’re going to take a look at a simple, but often overlooked, option for scheduling. When you create any content item, there is a field for “Suggested recurrence”. This field controls the default recurrence schedule for that item. Check out the image below:
If you’re not familiar with recurrences or how they work, check out this post on using recurrences to manage a content’s schedule.
So let’s take a look at the following scenario: You have a new content item for an upcoming holiday party. That content is going to be used in multiple templates and players in your network tree (possibly by multiple users). But you know when you are importing the item that you want it to stop displaying on the screens after the holiday party is over.
Here’s where you can use the suggested recurrence to your benefit. Rather than changing the schedule every time your drag this item into your network tree, you can change that schedule one-time, during import or in the Content bin, using the suggested recurrence. Then, every new instance of that item that you add to a template will have that recurrence by default.
A couple of important notes:
Changing the Suggested Recurrence does not affect the schedule of existing instances of that item. So you’re not going to screw up anyone’s existing scheduling by playing with this feature.
It is still possible to manually change the recurrence of a new instance of the item after it is scheduled. So in our holiday party example above, you could manually change the recurrence in one of your screens to keep playing after the holiday party.
That’s it. #DoYouFWI?