Step 3: Performance Date Pattern

Date of First Performance Enter the date of the First Performance (if no performances already exist,) or the next Performance (if you are just adding another performance).

The date that is entered here is not written in stone. It can be altered in the calendar by dragging a performance and/or it can be edited after the fact if you want to move a performance. It is meant to be used as a guide in creating all performances for the event.

Daily Performance Pattern

Weekdays Using the slider for each day, select the maximum number of performances (up to 10) that typically occur on each weekday

If you have multiple performances on a specific day of the week, select that number and additional performance times will appear on the right hand side. The number of performances is to be used as a general pattern when setting up the performances date and times.

Performance Times

Time slots If there is a day of the week that has more then one performance then you may set a matinee time as well as an evening time. These times are to be used as a general guide line when setting up an event. They can be changed at anytime after the performance has been created.

Performance Series Codes

Create Codes as Refer to Performance Codes for more information
Diataxis: 

Performance or Series Codes

The performance or series code provides quick reference to a performance(s) fpr an event. The content of the code should be reflective of an easy way to find the specific performance during the sales process. Performance codes can be up to eight characters or numbers.

It is important to know that each performance within the event code MUST be unique.
Comparable performances in multiple events can have the same series code so that you can manage or sell a subscription. Selling a subscription will sell all events (in the season package) with the same performance/series code.

If it is important to find a particular performance (1st Friday) for several events at the same time, each series should have the same code. This becomes very usefully when a patron is booking a season subscription and would like to attend the same time every month. Establishing a consistent nomenclature for the Event and Performance codes saves time during the sales process.

The following examples are recommended as an easy way for the sales person to verify that they have the correct performance. Codes should be in a week - day - performance format.

Week Long Performances

The following example would allow for easy comparison of week-long runs of shows.

1-SAT For the performance on the first Saturday.
2-SUN-M For the matinee performance on the second Sunday .
3-SAT-E For the evening performance on the third Saturday.
3-SAT-M For matinee performance on the third Saturday.
3-SAT-A For morning performance on the third Saturday.

Single Day Performances

If you do not have multiple performances per day the next example would allow for an easy comparison of the days of the week.

SAT-1 For the performance on the first Saturday.
SUN-1 For the performance on the first Sunday .
SAT-2 For the performance on the second Saturday.
SUN-2 For the performance on the second Sunday.

Multiple Performance Event/Play

If you have multiple performances per day the next example would allow for an easy comparison of the performances per day.

1-SAT-1 For the first performance on the first Saturday.
1-SAT-2 For the second performance on the first Saturday.
1-SAT-3 For the third performance on the first Saturday.
1-SAT-4 For the fourth performance on the first Saturday.

Single Performance for an Event/Play

If you have an event/play with only one performance, create the performance code as follows.

SHOW For the performance of a play where there will be only one performance.
CONCERT For the performance of a Symphony, Band or music.
GAME For the performance of a sporting type event/play.
DRAW For the performance of a curling event/play.
Diataxis: