Difference between revisions of "Glossary of Terms - Schedule Evergreen"
From Help Wiki
(Tag: VisualEditor) |
|||
| Line 8: | Line 8: | ||
</div> | </div> | ||
| − | ====Activities==== | + | ===='''Activities'''==== |
Activities are the parts of an event where space can be assigned. In an offering an activity can have classroom(s) assigned to it. Some examples include Physics Lecture, Seminar, Lab. In a conference an activity might have a keynote, this would be an activity within the event of the conference, but it may also have a life outside an offering. Other examples include: a meeting, or project time in the digital editing suites. | Activities are the parts of an event where space can be assigned. In an offering an activity can have classroom(s) assigned to it. Some examples include Physics Lecture, Seminar, Lab. In a conference an activity might have a keynote, this would be an activity within the event of the conference, but it may also have a life outside an offering. Other examples include: a meeting, or project time in the digital editing suites. | ||
* Activity Time (i.e. individual occurrences) - Each instance of a recurring activity has an activity time that defines the start and end of the activity. If an activity happens every Monday at 9:00a.m. during spring quarter then the an activity time describes each meeting time. Therefore, Monday week one of spring quarter would be represented by a single activity time. | * Activity Time (i.e. individual occurrences) - Each instance of a recurring activity has an activity time that defines the start and end of the activity. If an activity happens every Monday at 9:00a.m. during spring quarter then the an activity time describes each meeting time. Therefore, Monday week one of spring quarter would be represented by a single activity time. | ||
* Subscription - Users may subscribe to an activity. In the case of activities associated with offerings these may be driven by course registration. In the case of activities associated with departmental areas, these may be determined based on who is a member of the organization. For an offering, is populated by program/course enrollment. | * Subscription - Users may subscribe to an activity. In the case of activities associated with offerings these may be driven by course registration. In the case of activities associated with departmental areas, these may be determined based on who is a member of the organization. For an offering, is populated by program/course enrollment. | ||
| − | ====Events==== | + | ===='''Events'''==== |
An event has a definable start and end date that can be a single activity or that can tie together multiple activities. Think about conference events where one event can have multiple meeting spaces. Each event has an event type which further defines how these events are labeled created and subscribed to. | An event has a definable start and end date that can be a single activity or that can tie together multiple activities. Think about conference events where one event can have multiple meeting spaces. Each event has an event type which further defines how these events are labeled created and subscribed to. | ||
* Owners – The user associated with the request of the event. | * Owners – The user associated with the request of the event. | ||
| − | ====Request==== | + | ===='''Request'''==== |
Scheduling requests can be made for each activity. The request indicates a desire to schedule or reschedule spaces. It may have a series of scheduling needs which identify the resources required for a particular activity. | Scheduling requests can be made for each activity. The request indicates a desire to schedule or reschedule spaces. It may have a series of scheduling needs which identify the resources required for a particular activity. | ||
* Need - The scheduling needs required to make an activity happen. Typically this is based on the type of activity that is being requested. Needs start out as being associated with a request, but eventually become part of the request for a space. | * Need - The scheduling needs required to make an activity happen. Typically this is based on the type of activity that is being requested. Needs start out as being associated with a request, but eventually become part of the request for a space. | ||
* Resource - A possibly movable thing (or person) that can be requested with some subset of spaces. Examples include the grand piano that gets moved between the recital halls in the com building or the Science Instructional Tech that gets assigned to support a lab. | * Resource - A possibly movable thing (or person) that can be requested with some subset of spaces. Examples include the grand piano that gets moved between the recital halls in the com building or the Science Instructional Tech that gets assigned to support a lab. | ||
| − | ====Space Groups ==== | + | ===='''Space Groups''' ==== |
A collection of spaces and | A collection of spaces and | ||
resources for the purpose of controlling attributes that define how the space gets scheduled. Note that space groups are typically organized around the | resources for the purpose of controlling attributes that define how the space gets scheduled. Note that space groups are typically organized around the | ||
kinds of spaces that they are, but this does not imply that spaces must be grouped in this way. Each space group belongs to a scheduling center. | kinds of spaces that they are, but this does not imply that spaces must be grouped in this way. Each space group belongs to a scheduling center. | ||
| − | ==== Scheduling Center==== | + | ==== '''Scheduling Center'''==== |
Scheduled spaces are divided among scheduling centers, which determines which office or area is responsible | Scheduled spaces are divided among scheduling centers, which determines which office or area is responsible | ||
for the scheduling of these spaces. For these reasons permissions are associated with each scheduling center. | for the scheduling of these spaces. For these reasons permissions are associated with each scheduling center. | ||
Revision as of 14:12, 24 July 2018
Activities
Activities are the parts of an event where space can be assigned. In an offering an activity can have classroom(s) assigned to it. Some examples include Physics Lecture, Seminar, Lab. In a conference an activity might have a keynote, this would be an activity within the event of the conference, but it may also have a life outside an offering. Other examples include: a meeting, or project time in the digital editing suites.
- Activity Time (i.e. individual occurrences) - Each instance of a recurring activity has an activity time that defines the start and end of the activity. If an activity happens every Monday at 9:00a.m. during spring quarter then the an activity time describes each meeting time. Therefore, Monday week one of spring quarter would be represented by a single activity time.
- Subscription - Users may subscribe to an activity. In the case of activities associated with offerings these may be driven by course registration. In the case of activities associated with departmental areas, these may be determined based on who is a member of the organization. For an offering, is populated by program/course enrollment.
Events
An event has a definable start and end date that can be a single activity or that can tie together multiple activities. Think about conference events where one event can have multiple meeting spaces. Each event has an event type which further defines how these events are labeled created and subscribed to.
- Owners – The user associated with the request of the event.
Request
Scheduling requests can be made for each activity. The request indicates a desire to schedule or reschedule spaces. It may have a series of scheduling needs which identify the resources required for a particular activity.
- Need - The scheduling needs required to make an activity happen. Typically this is based on the type of activity that is being requested. Needs start out as being associated with a request, but eventually become part of the request for a space.
- Resource - A possibly movable thing (or person) that can be requested with some subset of spaces. Examples include the grand piano that gets moved between the recital halls in the com building or the Science Instructional Tech that gets assigned to support a lab.
Space Groups
A collection of spaces and resources for the purpose of controlling attributes that define how the space gets scheduled. Note that space groups are typically organized around the kinds of spaces that they are, but this does not imply that spaces must be grouped in this way. Each space group belongs to a scheduling center.
Scheduling Center
Scheduled spaces are divided among scheduling centers, which determines which office or area is responsible for the scheduling of these spaces. For these reasons permissions are associated with each scheduling center.
Schedule Evergreen Topics
- Schedule Evergreen Overview
- Glossary of Terms
Get Help
Submit a technology support request
No account or having problems logging in?
Request help as a guest
