...
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 issues issue is broken down into 4 key components which are noted as separate Jira issues:
...
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:
...
EID Note: Thomas discussed the EID mechanism, which Glenn updated in February, has providers for the user name, but post 2v2.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 2v2.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.