How the Optimizer uses the partition preferences of events
Event partition preferences
When the Optimizer processes location requests, it looks at the partition preferences of the organization sponsoring each event and restricts its search to those locations in the specified partitions containing the location feature requirements specified for the organization, if any.
However, if an event is imported into the Series25 environment from your SIS with its own partition preferences, those partition preferences override the partition preferences of the event’s sponsoring organization.
| Defining event partition preferences in your SIS doesn’t guarantee placement in the preferred partition(s) If no acceptable location is available, the Optimizer turns its search to the partition preferences of the event’s sponsoring organization |
How the Optimizer processes event partition preferences
When the Optimizer encounters an event requesting a location within specific partitions, it follows this process:
• It restricts its initial location search to the partition(s) specified.
• If it can’t place the event in any of those partitions, it searches for locations in the preferred partitions of the event’s sponsoring organization.
For example, an event...
• Requesting a location
• Preferring a location in the Butler Classroom Complex partition or the Cary Commons partition
• Sponsored by the Computer Science department
Would cause the Optimizer to...
1. Search for available locations in the Butler Classroom Complex and Cary Commons partitions.
2. If one or more locations are available at the required date(s)/time(s) in the preferred partitions, place the event in one of the locations.
If no locations are available in the preferred partitions at the required date(s)/time(s):
• Search for available locations in the preferred partitions of the Computer Science department.
• If there are locations available at the required date(s)/time(s), place the event in one of the locations.
If there are no locations available at the required date(s)/time(s), report the event as not placed.
When the Optimizer encounters an event requesting a location that also has preferred campus partition(s) and a preferred location, it follows this process:
• It initially ignores the partition preferences of the event and attempts to place the event in its preferred location. (The preferred location doesn’t need to be in any of the preferred partitions.)
• If it can’t place the event in its preferred location, it attempts to place it in one of its preferred partitions.
• If it can’t place the event in any of its preferred partitions, it searches for locations in the preferred partitions of the event’s sponsoring organization.
For example, an event...
• Preferring to be placed in location BCC200
• If BCC200 is not available, preferring to be placed in the Butler Classroom Complex partition or the Business Admin Quad partition
• Sponsored by the Computer Science department
Would cause the Optimizer to...
1. See if BCC200 is available for the event.
2. If BCC200 is available at the required date(s)/time(s), place the event there.
If BCC200 isn’t available at the required date(s)/time(s):
• Search for available locations in the Butler Classroom Complex and Business Admin Quad partitions.
• If one or more locations are available at the required date(s)/time(s) in the preferred partitions, place the event in one of the locations.
• If no locations are available in the preferred partitions at the required date(s)/time(s), search for available locations in the preferred partitions of the Computer Science department.
If there are locations available at the required date(s)/time(s), place the event in one of the locations.
If there are no locations available at the required date(s)/time(s), report the event as not placed.
