MELA Meeting Minutes 2003 - 2017

o Snapshot will then control this user/course in future runs.

 Use a different data source key if snapshot should not update or remove the record. Jennifer asked if I do this and want to take him out in the future, how do I do that. Stacey said that you can change data source keys, but this has not yet been reviewed. At this time if you wanted to remove the student, you would need to change the data source key for that specific record. Stacey asked that when changing data source keys, to provide the information to Usha & Roger. There is a way for you to do this on your own, but we will need to provide more information. You will not get separate user files unless you run separate enrollments.  Records added through the GUI automatically go in the SYSTEM Data Source Key Follow troubleshooint steps & checkpoints  To speed troubleshooting, include specific information such as ID Mgr user ID, pass, and course ID  If the issue is software related, contact Presidium  Examples: grade center, course copy, couse import/export, system slowness, software error messages, password reset  Presidium will escalate issues to Bb ASP as appropriate  If the issue is snapshot related, contact SBCJC  Examples: EK1/EK2 correction, ID Mgr restart, escalation of snapshot errors after troubleshooint, domain configuration changes  SBCJC will escalate and prioritize issues to Bb ASP

Escalation & reporting: 

Upcoming Changes: 

EK1/EK2 Correction Tool  Currently completing design, to be developed and tested in July  Deploy early Aug.  Deployed to System Admin  What Usha and Roger used on behind the Bb in the past  Service Pack 2  Updates outcomes system only  Required to complete outcomes system design and deployment

 Install on staging mid-July (possible available on July 21 st )  Install on production early August (possibly August 7 th )  Need to schedule production installation date (downtime required) – plan on approximately 14 hours.  Bb has released another service pack, Service Pack 3, which impacts some parts of the LMS.  Will need to take system down  Install software  Usha will reload and verify customization and identity manager  Testing system twice, once on staging, once on RAC staging environment which is a close clone to production.

184