What is the Seasons Feature?
The Seasons feature allows you to define registration periods and skip dates for sessions.
How Seasons Work
Seasons can be set at three levels: district, school, and provider. District and School Seasons will be applied automatically if certain criteria are met. Provider Seasons need to be selected manually for each session. This article focuses on district and school seasons.
- District Season: Applies to all schools, if enabled.
- School Season: Applies to all sessions at the school.
Priority of Seasons
- District Seasons will override the school Seasons if schools are set to follow District Seasons on the "My schools" page of the district dashboard.
Single Season Application
A Season's skip dates and registration start/end dates will apply to a session if all of the following conditions are met:
- The Season's start and end dates overlap with the session's start and end dates.
- The Season's registration start date (if any) is before the session start date (not the same day).
- The Season's registration end date is before the session end date (not the same day).
If the above three criteria are all met, we say the session matches with the Season, the Season will apply to all matched sessions automatically.
Note: Registration and session date comparisons are not exact due to time zone differences. If the dates are close (within a day), the match could go either way. Therefore, we recommend setting the registration and session dates more than a day apart.
Multiple Seasons Application
When a session matches multiple Seasons, the Seasons are merged, and the merged Season is applied to the session.
Merging Seasons means:
- Combining all skip dates.
- Using the earliest registration start date.
- Using the latest registration end date.
However, only matched Seasons will be merged for a session. For example, if a Season's registration end date is after the session's end date, the Season will not be merged.
Example: If a session matches with both Season A and Season B, a merged season will be applied.
Season A |
Season B |
Merged Season |
|
Skip dates |
Jan 1 |
Feb 15, Feb 16 |
Jan 1, Feb 15, Feb 16 |
Registration start date |
Jan 1 |
Feb 1 |
Jan 1 |
Registration end date |
Mar 2 |
Apr 15 |
Apr 15 |
Example: Spring Break Season and School Year Season
Let’s imagine you are setting up a Season for spring break, and don't want the school year Season to be merged and applied to spring break sessions. Please
- Ensure the School Year Season has a registration end date after spring break ends.
- Ensure the Spring Break Season has a registration start date after the start dates of all the year-long sessions.
This setup will ensure that the Year Long Season won’t match the spring sessions.
If the School Year Season includes spring break days as skip dates, and is intended to remain open for registration, if its registration close date is left blank, its skip dates will be applied to the spring break sessions. Setting the School Year Season’s registration end date close to the end of the school year will prevent the School Year Season from applying to spring sessions, allowing the Spring Break Season to apply instead.
If you have any other questions, please feel free to reach out to our support team. We can be reached at support@6crickets.com, or you can contact us via online chat through our website.
Comments
0 comments
Please sign in to leave a comment.