[Building Sakai] SIS Integration

[Kara Stiles]

Hi Louis,

You have a few options here.

1. You could create a new role specifically for that site (called student1
or something), and then make all "non-registered" users have the student1
role.  BUT...this process does not scale, so if you have many courses that
need to have multiple sections in them, do not choose this option.

2. Your institution can opt to alter its method of SIS integration at the
technical level to include section support

3. (easiest method, but requires maintenance) You can create a course site
manually using the Site Setup tool, and have the site you manually created
be the "main" site (instead of using an SIS created site), and then you can
just merge all your users into the manually created site. Those users will
never be deleted from the manually created site, but updates to rosters
("adds") will either need to be processed manually, else you'll have to
perform the import from site>merge users function on some regular basis to
make sure the "adds" get "added."

I hope this make sense.  If you have more questions, you can reach me at
kstiles at rsmart.com

Thanks,
Kara

On Fri, Jan 28, 2011 at 12:00 PM, Algaze, Louis J <ljalgaze at nps.edu> wrote:

>  Hello,
>
> Does anyone know if there is a Sakai property which will prevent the
> dis-enrolling of students using the rSmart’s SIS integration job in the Job
> Scheduler?  Or is there a file we can modify to prevent the disenrollment?
>
> We are attempting to set up the creation of courses and enrollments using
> an export from our student management system.  We have been going on the
> path of rSmart’s SIS Job (vs. Exploring using the web services) but have run
> into a snag.  We have classes and segments where Math 101 is a class and a
> segment is an offering of that class; MWF 12-2 With instructor Smith.  We
> are able to get an export from our student management system with one
> segment per line so one Sakai site is created per segment and appropriate
> students are enrolled in each segment.
>
> The issue arises where an instructor (but not all of them) want to use a
> single Sakai site for several segments.  The instructor can Import from Site
> and Merge their Users knowing that they will need to manually manage
> enrollment afterwards.  But the next time the script is run the merged users
> will be dis-enrolled.
>
> I tried creating two site properties, both named externalSiteId but Sakai
> did not save the new one.  I even tried one with different capitalization or
> with a externalSiteId2, both cases the site was not recognized by the job.
>
> Any suggestions are appreciated.
>
> Thank you,
>
> Louis Algaze
>
> _______________________________________________
> 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/20110202/0db4e85d/attachment.html