[Building Sakai] Course Management : CmSynchronizer JOB : File Size

[Thomas Amsler]

> Thomas, those are a bit out of date. Are you more interested in how the XML
> is created in the first place?

We are generally interested in how institutions populate the Sakai
internal CM tables.
- What modifications are mode to the synchronizer sample code?
- What modifications are made to the CM Hibernate Impl?
- How are the Sakai internal CM tables populated with the initial
large data set?
- How frequent CM tables are synchronized with SIS data and how long that takes?
- How well does the XML sync approach work?
- How well does the custom scripting sync approach work?
- Has anybody attempted to load data from SIS-DB to Sakai-CM-Tables
directly in SQL?

We have experimented with XML as well as custom groovy scripts that
use the CmAdmin API.


>
> The central change is that CourseWork / Sakai is now receiving events for
> changes in the upstream course data. The necessary hierarchy info,
> departments, subjects, administrative areas, are built up as the changed
> documents are consumed.
>
> This allowed us to drop the requirement for the RIC feed.
>
> However on human use terms the RIC feed was a great support resource as it
> is the only online quickly grep / searchable document of Stanford's course
> offerings. I believe it was still being generated.
>
> I left Stanford about a year ago and formed an LLC. I then embarked on a
> long project for Stanford. That project's now wrapped up, and I'm sniffing
> around.
>
>
>
>