Overview

Class Offering is the process in which schools at Emory University, and the departments within schools, submit to the Office of the Registrar their schedule of classes for future semesters. These updates will be done in CourseLeaf/CLSS by the approved scheduler assigned to the department/school. This process takes place based on the CourseLeaf timeline. This document presents Emory University schools and departments with procedures required for a correct and complete submission of their course offering.

Applicability

This policy applies to all schools at Emory University using CourseLeaf.

Policy Details

Class Offerings must be submitted in CourseLeaf/CLSS no later than the date listed on the timeline for a semester. 

Class Offerings will be submitted and updated directly into CLSS. Approved schedulers will have an opportunity to submit and update classes for the assigned schools/departments during the Planning Phase. Please see the tentative time frames for the Planning Phase for each semester below:

• Fall: 1^st Week in September – Mid- January
• Spring: Mid-January – 1^st week in October
• Summer: Mid-November – Mid-January

After the Planning Phase and class offerings are in OPUS from CLSS, there will be a two week period when CLSS will not be available to schedulers.  This is called the Proofing Phase. During the Proofing Phase, the Registrar's Office will process workflow items (i.e. cross listings, room assignments, new instructors, credit hours, etc.).  After the Proofing Phase, CLSS will re-open and schedulers will be able to submit updates in CLSS.  This will be the Publish Phase for each semester:

• Fall: Mid-March – 1^st week in September
• Spring: Mid-October – Last week in January
• Summer: Mid-January – Last week in May

Schedulers will be notified of error causing items as they “Save Sections” and/or “Validate” classes within CLSS.

After the Publish Phase, CLSS will not be available. This will be the Archive Phase. During this phase, a semester will go into the Historical section. Class schedules may be viewed only but not updated in this phase.

Failure to adhere to this policy may cause delays in the process and/or a chance of incorrect data.

Here are some of the benefits of CourseLeaf:

• Seamless class scheduling experience for all scheduling units
• Faster scheduling of classes and integration into OPUS
• Schedule building based on up-to-date OPUS data
• Schedule of classes will be available to students faster – regardless of the student’s career
• Potential planning tool for multiple term schedule building
• Room scheduling can begin earlier and with less impact from schedule adjustments
• Better validation and integrity of class data in OPUS
• Create a unified method for the timing and availability for schedule of classes for students

CourseLeaf will NOT:

• Integrate with R25/25Live for room scheduling
• Be a mandated schedule planning tool
• Solve the issues of course demand, faculty availability, etc.
• Be available anytime for all terms.  There will be strict cut off times/blackout dates where CourseLeaf will NOT be open for updates.

CourseLeaf will roll out in three phases:

Phase I

Phase I schools that are currently using CourseLeaf for class scheduling.

• Emory College
• School of Nursing
• Goizueta Business School
• Laney Graduate School

Phase II

Phase II schools are scheduled to "Go Live" in January 2018 for the Fall 2018 scheduling period.

• School of Theology
• School of Public Health
• Oxford College

Phase III

Phase III schools (pending)

• School of Law
• School of Medicine

There are two types of Modes

• Design Mode – Data is NOT exchanged between CLSS and SIS (OPUS). All scheduling changes made in CLSS, at this point, will only be stored in CLSS and NOT updated in SIS (OPUS).
  • Schedulers will only be able to make updated to their Scheduling Units. They will have “view only” access to other Scheduling Units.
• Refine Mode – Data is exchanged between CLSS and SIS (OPUS). Any changes, new sections, or deletes to existing sections that are successfully saved in CLSS, will updated in SIS (OPUS).

A Phase in CourseLeaf CLSS identifies the distinct time periods of the scheduling cycle.

Below are the four phases the we will have at Emory:

• Plan – Departments/Schools put their initial schedule together: securing faculty to teach, setting enrollment capacities, times, determining cross-listings, preferred locations, etc.  All fields are editable by schedulers since it is the low risk phase.
• Proofing – Administrators only will have access to enter cross listings, assign rooms, process workflow items, make any necessary updates, etc.  Schedulers will NOT be able to make changes during this phase.
• Publish – Departments/Schools make final scheduling updates right before the schedule goes live for students to see in the class search.  This phase also covers the registration period, meaning certain fields like the following should NOT be changed without notifying the enrolled students first:  meeting patterns, cancellations, credit hours changes, changing from non-writing to writing or vice versa, and location.  Publish phase will have more restrictions as to what fields schedulers may edit.  The above fields are higher in risk of effecting student schedules and should not be edited, if at all possible.
• Archive – All scheduling changes cease in CLSS.  This phase indicates the end of the scheduling cycle.  All schedulers are prohibited from making adjustments to class schedules.  Any class scheduling changes at this point will go through formal workflow process before being approved and updated in SIS/OPUS.

• Fall 2017 and Spring 2018 Timeline (PDF)
• Summer 2018 Timeline (PDF)
• Fall 2018 and Spring 2019 Timeline (PDF)

Rules are a set of guidelines set by Leepfrog and Emory in CLSS to better assist you in correctly submitting your schedule of classes into OPUS. Rules can be set at the section level or the scheduling unit level. Rules can vary between Modes and Phases.

Please note, some Rules are in place for all schools in order to facilitate transmission to OPUS, and some are school specific and may not pertain to all schedulers.

There are three types of messages that you will receive, if there are errors once you "Save Section" or "Validate".

Error - "An Error indicates that the section or scheduling unit may not be saved as is. The error description will give the rationale and possible solutions to the error. The Save As-Is or Start Workflow buttons will not be available if there is any error present. To save the section, correct the error then attempt to save again."

Warning - "A warning indicates that the section or scheduling unit may be saved, but caution should be taken before completing the schedule. The warning description will give the rationale and may list possible issues that may arise from this section. The Save As-Is Button will appear if the validation only required a warning and not a work flow or error. Warnings do not require any further work flow or approval to be saved."

 Work flow - Work flow indicates that the section or scheduling unit may be saved as is but approval or additional work by the Registrar's Office will be required to complete the entry of the class or schedule into OPUS (i.e. Cross-listings). The work flow description will give the rationale. In Design mode, all work flow takes place at one time for the entire scheduling unit. In Refine mode, each section will have to go through work flow on its own.

List of Rules Currently in CLSS

Below is a list of current Rules in CLSS. The Phase and Modes are listed by each rule. This shows which Mode and Phase a particular Rule is in affect. Also, if a rule is violated, the "On Failure" column shows the error type you will receive.

Text entered in the “Comments” box will go into Workflow for the University Registrar’s office to process. Below is a listing of key words to be used when submitting requests using the comment box.

If you experience any issues while working in CLSS, please submit a ticket by clicking on the link at the top of the page in CLSS (as pictured below). Our office will be notified when new tickets are submitted and will work as quickly as possible to resolve the issue. The amount of time needed depends on the type of issue reported. Please allow at least two (2) business days to resolve issues. When the issue is resolved, you will be notified via email. If the issue takes longer than two (2) business days to resolve, you will be notified of the status via email.

Email us at registr@emory.edu