Banner Access Issues

Scott brought up the issue of access to Banner production data again, so most of the discussion revolved around this issue (plus other notes at the end.) The issue is broken down into 4 key components which are noted as separate Jira issues:

Coordination with Banner team:

More formal arrangement needed to encourage better connections/relationships with Banner team. Brian noted that Banner resources are stretched thin due to the Banner 7 update. The update will affect My and Sakai in that password change tfor systems access needed for hight security which will be managed by DC. Documented table structure changes do not appear to affect current integration code.

Test Plan for Course Management API:

Issues with lack of access to realtime data affects both sakai and Breeze. Key issues in sakai at this time to be put into a test plan and coordinated with Banner team on test scenarios and implementation deadlines.
Known test requirements at this time include:

Add/drop of users in courses (per Brian, we can mimic this now by manipulating the UNEX table)
Update instructors
Add/Remove sections
Add/Remove courses

Will need to test against dev and test versions of mView by coordinating scheduled tests with Banner contact.

Deadlines for mView Access

Currently, we have a dev version of mView, but for proper testing sakai will need a test mView which can be manipulated to mimic production and a production mView for final testing prior to production release of sakai in Fall 2006 (or possibly this summer.)
Brian suggested talking to Sandra about scheduling deadlines with the Banner team to implement test and production mView releases to the sakai team. This affects Breeze production releases as well. Communication with the Banner team would help to verify if our test plans are adequate and to find out what their issues might be.

Breeze - Banner production access

Breeze is a production application which requires access to user enrollment and drop/add in Banner. Currently using a web interface for user data, the long-term plan is to access the data via sakai's webservices. Access to production data is needed now and implementation of webservices depends on sakai maturity, so Breeze access to Banner data is tightly coupled with sakai planning.

Other Issues

DC Note: Thomas mentioned that Patrick of DC stated in the Monday afternoon meeting that he's ready to move the database from bricker to rack mount.

EID Note: Thomas discussed the EID mechanism, which Glenn updated in February, has providers for the user name, but post v2.2, EID's will generate UUID override. Neither state is desirable for us. Thomas suggested reviewing the original requirements to see if they are counter to UCD needs.

Next Version Upgrade: per Scott, we need to move to the v2.1.2 release because the course management api changes are needed for Scott's provider. Thomas concurred after short discussion.

SVN Problems: Brian noted that Emily found issues in svn releases are related to failures of mod auth Kerb. The misses occur due to the need to make full round trip and the webdav client doesn't note errors/missed files. No fix right now, but Emily will investigate further.

Browser not supported