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 5 Next »

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:

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:

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:

  1. Add/drop of users in courses (per Brian, we can mimic this now by manipulating the UNEX table)
  2. Update instructors
  3. Add/Remove sections
  4. 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.

  • No labels