Banner Access Issues
Scott brought up the issue of access to Banner production data again, so most of the discussion revolved around this issue. The issues is broken down into 4 key components which are noted as separate Jira issues:
...
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 2.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 2.1.2 release because the course management api changes are needed for Scott's provider. Thomas concurred after short discussion.