[Building Sakai] Questions about Course Management

[Kevin P. Foote]

SIS is yes 'Student Information System' .. example Banner or other.

Quartz is the internal Sakai scheduler tool. You can do lots of fun
stuff with this :-)

Yes the basics of CM is getting your SIS data into Sakai. Writing custom
code that uses the CM API is a method of getting your data into Sakai.

I believe you will have better luck using the API but you can insert
data into what ever tables you want :) I forget I think there are about
3 or 4 cm tables.. (maybe more).

Like I mentioned before there is an OOTB hibernate based procedure that
uses a self created XML file to get an initial set of your course data
into Sakai. This is a very good starting point. 

- you create a similar structured XML file
- you tell the Sakai Scheduler (Quartz) where it is.
- you create courses using your consumed data.

This is shown in the wiki page you linked. Look closer at the 'tutorial'
section.

------
thanks
  kevin.foote

On Wed, 2 May 2012, Hai Vo Thanh wrote:

-> Hi
-> 
-> What is SIS? is it stand for Student Information System?
-> And what is "Quartz"?
-> Which files do i need to modify to do the thing "Implement the CM API" ?
-> Did you mean that what i need to do is pull data from SIS source and push it into sakai DB tables?
-> If yes, can i insert dirrectly data into Sakai table without caring about what CM API is?
-> I'm still very ambiguous :-(
-> Thanks and regards,
-> Hai
-> 
-> ________________________________
->  From: Kevin P. Foote <kpfoote at iup.edu>
-> To: Hai Vo Thanh <v0thanhhai at yahoo.com> 
-> Cc: "sakai-dev at collab.sakaiproject.org" <sakai-dev at collab.sakaiproject.org> 
-> Sent: Wednesday, May 2, 2012 8:02 PM
-> Subject: Re: [Building Sakai]  Questions about Course Management
->  
-> 
-> Hi, 
-> 
-> Just some thoughts. 
-> 
-> CM is more of an integration point than a "tool". 
-> 
-> In a programming sense CM allows a school to wire up (integrate) back end connections 
-> and processes to its current SIS (Banner, etc..) through database views or 
-> other such mechanics. This is done through the CM api which allows you
-> to pull from your known source (SIS) and place courses and enrollments
-> into a Sakai database location. These are then made available as
-> "course" to create within Sakai. 
-> 
-> There are a number of ways you can do all of this with the CM interface,
-> all the way from programming against the CM api to setting up a few
-> Quartz jobs. 
-> 
-> A simple solution available in OOTB (last I checked) is to have Sakai
-> consume a standardized XML file, via Quartz, which contains all your courses 
-> and enrollments. This should get you rolling anyway so you see how
-> things work a bit. 
-> 
-> HTH .. I'm sure others can chime in with more detail.
-> 
-> ------
-> thanks
->   kevin.foote
-> 
-> On Wed, 2 May 2012, Hai Vo Thanh wrote:
-> 
-> -> Hi all,
-> -> 
-> -> I'm not very good at coding, and new to Sakai. I've read through this article several times but still not get the point.
-> -> https://confluence.sakaiproject.org/display/SAKDEV/Course+Management+Integration 
-> -> 
-> -> 
-> -> Is CM a tool? I saw some sample code in "Development approaches" section that seem need to be checked out and build?
-> -> 
-> -> Which files do i need to modify to do the thing "Implement the CM API".
-> -> 
-> -> Currently, what i want is like the Sakai Demo: when creating a site, we have a list of previos students to add to new site,
-> -> and if we choose "Add course(s) and/or section(s) not listed above...", there will be a drop down list of subject, course, section
-> -> to choose.
-> -> 
-> -> Please help me to understand. Thank you very much. I'm usingSakai 2.8.1
-> -> 
-> -> Regards,
-> -> Hai