Ability to Build (Create, Configure, and Maintain) a Class for existing Course

[GoogleCodeExporter]

Must be able to initialize a class associated with a Course within a Group.
Classes include Class Calendar, Exams, Assignments...Don to provide
complete list for Rel 1 

Original issue reported on code.google.com by jlb1...@gmail.com on 22 Feb 2008 at 9:53

[GoogleCodeExporter]

See issue ID #44 for this.

Original comment by don...@gmail.com on 25 Feb 2008 at 6:05

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

From the Facilitator's Workroom, a facilitator can select an option to "Create 
a New 
Class."  This can optionally require the approval of the Academic Dean or 
Provost, 
but it's not necessary.  Class creation is actually a "Wizard" type of 
mentality (to 
borrow Microsoft's terminology), wherein the facilitator is stepped through 
some 
screens that help with the entry of "required" information for setting up a 
class. 
The progression of screens will be:
1) Selection of the Course on which this class is based
2) Will this be a derivative course? If so, it will go down a diff path for 
setup... 
not for Release 1
3) Enter profile information for this class (Location, Student group (e.g. 
First 
Methodist Church of Cairo), Facilitator, etc.)
4) Course Calendar: Starting Date (note: the end date will be automatically 
determined by the system through setup of the calendar), Class Days, Blackout 
days.  
The facilitator may then press a button that will automatically populate the 
"real" 
calendar with the dates that are calculated from the "symbolic" dates from the 
course information from the course developer.  As the facilitator clicks on 
certain 
days, he/she may define them as blackout days or non-blackout days.  (Blackout 
days 
will include all non-Class Days and manually entered Blackout days. A 
facilitator 
would probably want to declare local holidays as Blackout days or he/she may 
want to 
blackout an entire week for a major holiday - e.g. the Feast of Tabernacles).  
The 
facilitator may then drag-n-drop assignments and notes from day to day, if the 
manually entered blackout days displaced a day.  
Once the calendar is modified as the faciltator desires, the system will 
calculate 
the end-date of the class, which will be saved in the class profile in the 
database.
5) Course Activities, Reading Assignments, Essays, Collaboration Assignments, 
etc., 
may be scheduled at this time.  The system will automatically present a list of 
all 
of the assignments (per the course design) and their "real" dates (per the 
course 
design) and allow the facilitator to indicate if assignments will be 
automatically 
issued or manually issued to the students.  If they are automatically issued, 
then 
the facilitator doesn't need to intervene.  If they are manually issued, the 
facilitator will be given the option to "Releaase" the issuance of an 
assignment, 
which would allow it to be held for various reasons.
6) Enrollment Management: This is NOT a required part of the classroom setup -- 
setup will complete successfully without it.  The enrollments can be managed at 
a 
later time from the Facilitator's Workroom.  
7) On the last screen, the facilitator will press the "Create Class" button on 
the 
last screen, which will process all of the class setup information.  From this 
information and the info in the course design, the Gradebook will be created. 
As 
students enroll (or enrollments are manually confirmed/approved), the student's 
User 
ID's will be added to the Gradebook.

At this point, the class is ready to run.  The class can be run from the 
various 
tools in the Facilitator's Workroom (e.g. Collaboration, Class Assignments, 
Student 
Information, Gradebook, etc.)

Original comment by don...@gmail.com on 25 Feb 2008 at 10:44

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by aarons...@gmail.com on 10 May 2008 at 4:18

• Changed state: Started
• Added labels: ****
• Removed labels: ****