...
Courses are created as a type "course". Here are some "brief" steps.
1. When creating the course site, there is a dropdown for the term. The user selects this term, which currently is controlled by the sakai.properties configuration file in the tomcat instance.
Problem: this data is not synchronized with external Banner data, so only one term may appear that may be applicable (e.g. dropdown says Summer 06, when really it should say Summer Session II).
2. User then is prompted for how the roster should be established. The user is then asked to select something like " 2005,FALL,SMPL,001,001" or "Choose user roster not listed from above". The user selects the roster not listed from above.
3. User is asked to fill in (textbox) the "Subject","Course", and "Section" for this course site.
Problem This is ad-hoc, and user's have limited space to add the course information. Again, this is entirely controlled by parameters set in the sakai.properties file.
4. The user is asked to add more rosters, and authorization person's name if necessary. Usually rosters are not added, and authorizer's name is something like kdalex@ucdavis.edu.
5. From here, the course site is created with a default tool set the user selects from.
6. After site is created, rosters are added to it (via MyUCDavis,etc)
Problem Rosters are still not dynamic, as providers have not been compeletely enabled
Current Batching Strategy
...
1. creates course site "skeleton" with the following attributes:
i. creates site id with a pattern of TERMCD and CRN. An example is 20061012345
ii. creates a site title (tab) with the pattern C (this is a MAJOR difference from the manual process)
iia. SUBJ COURSENUMBER SECTION TERMABBREVIATION TERMYEAR (e.g. BIS 001A 001 SSS WQ06)
iii. adds site information also (e.g. description, long description, etc)
2. adds tools and pages to the site (from a sakai.properties configuration)
3. creates the site so that providers can "kick in" and create rosters, roles dynamically