Iteration .01

Owned by James Renfro
Last updated: Sept 11, 2006Version comment
2 min read

This iteration began 8/20/2006 and ended 9/2/2006.

Here is a link to all the JIRA stories that existed under this iteration on 9/7.

Unresolved issues:

  • SAK-136 - Add Course title (from Banner) is the field presently mapped for course description information when provisioning sites. A course description (short and long) should be mapped from external data so that it can be referenced by certain course tools
  • SAK-130 - Add clustering support to infrastructure

Tracker Summary:

  • Scott: the development for Providers, Batching, and AFS Distauth was finished up in this iteration. This includes SAK-25, 119, 121, 140, 141, 146, 154, 155, 156, 157 – testing is mostly taking place in .02
  • James: mostly figuring out what to focus on, learning the ropes of Sakai – nothing substantive developed during this iteration. One perl script to allow quick switching between sakai/tomcat environments.
  • Thomas: Worked with Scott on batching SAK-119,140,146 (Black List/White List/Provider Id). Removed the "Powered by Sakai" image SAK-91.

Newbie's Guide

A quick explanation of what "providers" and "batching" means.

Providers refers to a set of API's in the ucd-enterprise-data-service project, interfaces under the edu.ucdavis.sakai.api.enterprise.manager package. These are: CourseManagementManager (SAK-157), GroupManager (SAK-156), and UserDirectoryManager (SAK-154,155). Together they coordinate the provisioning of external data into Sakai.

Batching refers to a set of classes that implement the QuartzJob batch/cron logic and that are fairly interdependent with the providers. SAK-119 (White List), and SAK-140 (Black List) allow and prevent (respectively) course sites to be created outside of the normal workflow. SAK-146 does batching that sets the provider ids, SAK-121 adds pages and tools for sites, SAK-25, 121, and 141 worry about how to handle the fact that whichever user creates a site ends up being a member.