...
Coordinating various processes running/updating to CERE
Keith - Wrapping up current features on CREST
Scott - Batch processing for checks against CREST to update schedule data in CERE;
Group Discussion: Consider logging and every .5 hrs to determine impact on performance; initial changes more frequent than later methods; unsure of performance of CRUD during batching - generation of orphans? race conditions? both processes using web services
...
SOM is working with vanilla Sakai and Ilios; what changes will they need to go for working design?
Production Launch Schedule
CERE updates : done weekly on Tuesday at 5pm
Rick - There are 73 trained faculty ready to use CERE; 25-27 instructors teaching in the fall;
Beau - Schedule data not available yet on production, next week's update is target date - may not require restart though;
Notify . Okay to notify faculty during training sessions
Ready for Jan to notify all faculty?that production is ready for them to access.
Schedule update to CERE training server this coming Friday - ; next training session is on Wednesday of next week First deploy with all data & roles fully set
ALERT!!
Need
Production Deployment Issue
Curriculum manager role needs to exist for Erin; need to run all roles to CERE and reload courses
Curriculum manager role needs to exist for Erin
Schedule for ; first deploy with all data & roles fully set.
Schedule final role update and course reload for today - Rick/Dave to check out production this afternoon.
Tomorrow, Thursday 17 - notify Jan to announce availability to all faculty (if all goes well)
Training
Rick - questions from faculty:
Allowed Will allowed changes made in CREST be will be updated to CERE , changes right away?
Response: Changes in CREST will appear in CERE immediately - . The batching process is to verify changes/cleanup. Although
Note: there may be a caching problem on the sakai side.
Scott - Issues management process? Reporting mechanism?
Existing issue tracking in SVM HelpDesk system
Dave/Rick to report to jira if issues cannot be resolved via user education
...