VetMed Developers Meeting
...
CERE Integration
Coordinating various processes running/updating to CERE
Keith - wrap Wrapping up current features on CREST
Scott - batch Batch processing for checks against CREST to update schedule data in CERE; consider
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
Scott, Chris, Keith -
Discussion of changes to information sharing btwn between systems
. Data from CREST to CERE does not have the concept of sections
; Scheduling data may differ btwn between course and labs.
Resolution Possible resolution of sessions based on student group?
May have issues with users in multiple 299's; not an imminent problem but needs to be addressed down the road.
Checking for batch run is a field by field comparison - need to verify; Ray will check out new code on my this afternoon;
Decision: Run process every .5 hrs on 15 and 45 after the hour; modify based on logged responses, if needed
EVALS
...
Scott - Phil is almost done w/template generation (authoring);
Taking Status of taking the evaluation and presentation aspects of; Scott now working on taking evaluation portion, but will hand off to Phil; interface ie Scott will shift to working on the interface, i.e., viewing what evals are available now on Scott's plate; . He will coordinate w/Chris for mockups of listing evaluation listings on user's MyWorkspace to linkto or access eval evaluation tool embedded in the course site.
Gradebook
...
Beau asking for patches from IET; no response?
School of Medicine (SOM)
SOM - is working w/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 ; 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.
Faculty Support
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.
Scott on caching issue: Content changes are not displayed unless browser is updated or flushed; sakai caching issue in development as well - unknown caching location; propose issue to sakai-dev