[Building Sakai] Implement CourseManagementService ???

[John Bush]

You can do all that with the SiteService.  I'm not sure why you want  
it to be a tool?  Is there some sort of UI you are imaging?  Sakai's  
has a job scheduler built on top of quartz.  If you don't have a UI,  
its a lot easier to use that mechanism to simply schedule your job  
(nightly, hourly, whatever) which could then create the sites and  
memberships for you automatically.

John Bush
Development Manager
rSmart




On Jun 28, 2009, at 8:44 AM, Phuc Bui wrote:

> Dear,
> Unluckily, we do not very good at web services and do not know about  
> Quartz :(
> I think implementation CourseManagementService is quite complex to  
> us. Now I do not know how to implement ???
> So I am considering a way to write a tool for admin that’s  
> responsible for :
> -          Create a course site with data given by external database  
> (academic term, course information…).
> -          After creating a course site, we add users to that site  
> (all students and instructors will be registered as Sakai users  
> before).
> I think the advantage of that way is that: instructors do not worry  
> about how to create a course site, everything is done automatically.  
> They just enter website and choose their course site then do their  
> job.
>
> So I would like to ask whether it is possible or not ?
> If it is, which API can be used to create a course site, and add  
> available Sakai users to a course site ?
>
> Thanks for your replies,
> Phuc Bui
>
> From: John Bush [mailto:john.bush at rsmart.com]
> Sent: Sunday, June 28, 2009 2:16 AM
> To: Phuc Bui
> Cc: 'Sakai Mailing List'
> Subject: Re: [Building Sakai] Implement CourseManagementService ???
>
> You don't necessarily need to implement the  
> CourseManagementService.  The CourseManagementService is useful if  
> you want instructors or admins to have flexibility in how you map  
> courses into sites.  If you want to enforce a strict mapping, you  
> can simply provision the sites and enrollments yourself using a  
> quartz job or web services.  For example, your external system could  
> dump its notion of course, enrollments, even users into files which  
> are then read by a quartz job that leverages the Sakai api's to  
> create the sites, memberships, and users as you see fit.   Most of  
> our clients do things this way, only a few need the power of the  
> CourseManagementService.
>
> John Bush
> Development Manager
> rSmart
>
>
>
>
> On Jun 23, 2009, at 8:52 AM, Phuc Bui wrote:
>
>
> Dear all,
> Our problem is that:
> We just want to create sites for courses which are registered by  
> other system. I mean our university will offer courses that are  
> available to register (to enroll) then student will enroll these  
> courses.
> Then administrator will create sites with that data (we implement  
> the simple model 1 course – 1 site).
> Generally, I want the result as Sakai demo data. When I select an  
> Academic Term, it will display list of course offering of that term,  
> when I select a course offering, I will have available members  
> (instructor and students) who have registered for that course  
> offering.
> Now, I am in a mass, I do not know how to do and where to begin.
> As my older question, I know we have to implement interface  
> CourseManagementService but how about other interfaces in Course  
> management system (CourseManagementAdministration , AcademicSession,  
> CourseCanonical, CourseOffering, Membership ….) ?
> Then we have to implement CourseManagementGroupProvider
>
> Would you please tell me the steps to implement  
> CourseManagementService ?
>
> Thanks a lot
> Looking forward to your replies
>
> Phuc Bui
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090629/9bc5c9bd/attachment.html