Roskilde University, Denmark

Owned by Former user (Deleted)
Last updated: Jun 10, 2005Version comment
2 min read

We are currently running a small-scale pilot of Sakai 1.0 with the following modifications:

  • Yale CAS Authentication implemented through custom developed CAS-enabled LDAP authentication server. Basically, authentication challenges get screened by the LDAP server (length and prefix) to discern between proper passwords and single use CAS service tickets. Only service tickets are used by Single SignOn, but the LDAP server is used by other services too. Login is redirected from the gateway to our Single SignOn page.
  • Portalino links to the Sakai instance, and everyone is able to add direct links to specific sites. Our plans for a Summer upgrade for Portalino will enable it to distinguish between user's memberships of courses so direct links to individual courses will be possible.
  • Our mailing list system has been modified to redirect mails to Sakai Email Archive for storing archives of sent mail and distributing mails to the site members. We would like to reverse this responisibilty so the emails get archived by Sakai but the distribution is handled by our mailing list system.

Our plan for this Fall involves an installation of Sakai 2.0 open to all faculties. We expect a slow adoption, but only time will tell.

  • We should have a new version of our Portalino presenting individual links of the enlisted courses for a given user. This will be our replacement of the Gateway / tabbed sites presentation of Sakai.
  • CAS Authentication will be continued without futher modifications.
  • We will have to provide a Course Provider based on our Dynamic Course Provider Use Case to authorize access to the individual courses. This will probably be on a daily synchronization basis.
  • We would like some kind of lazy initialization by cloning template courses. We have attribute-based metadata mapped in our Group Role Management System to tag specific groups as courses, special interest groups or commitees for selecting proper templates. We have identified sets of tools needed by courses - nonarchiving mailing lists (non-Sakai), archiving mailing list (Sakai with Email Archive as only tool) and a basic course (Sakai with Schedule, Syllabus, Resources and Email Archive - the two first auto-generated from our course description system). Pioneer maintainers can add more tools to this set.

User support-wise, we have made a joint venture with our pedagogical education center and have a bit of a wrestle with our staff educational department. We will also support early adopters with consulting service during the startup.