Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

  • Attendees (Jon, Scott, Thomas,Brian)
  • Absent: Lisa
  • Jon's Issue Summary (Con't from 4/25/06):
    • revisited: help/input loading new CM API impl with our course data. This would help the Gradebook export tests (since current plans will use CM to resolve course ID's for export) We should also consider taking some time soon to load the above data as an aid to the current provider work. The CM impl will be in 2.2, tested. So, this may be in line with Fall. CM API, loaded with data could be an innoucuous referent (data source) for the provider work, and may act as a context for calling the providers.
    • To what degree do we utilize the UUID in the new CM API? He mentioned that Scott,Brian, and Jon should be actively involved in this discussion.
  • Brian's Issue Summary:
    • Wanted to know if prefixing external data (currently UCD_ Materialized views) with the consumer of the service name (e.g SAKAI_)
  • Scott's Issue Summary:
    • what should we be preparing for in the batching of skeleton course sites, with respect to sectioning?
  • Thomas' Issue Summary:
    • None

ToDo:
Load new CM API with course data (revisited). Scott mentioned this could be made available by exposing our code mods in the provider so that other people can use this data. Thomas also suggested that we (and Berkeley for that matter) could utilize a XML loading utility for course test data.

  • No labels