VetMed Developers Meeting
VM 081606
Coordinating various processes running/updating to CERE
Keith - wrap up current features on CREST
Scott - batch processing for checks against CREST to update schedule data in CERE; 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 systems
Data from CREST to CERE does not have the concept of sections
Scheduling data may differ btwn course and labs
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;
Run process every .5 hrs on 15 and 45 after the hour
EVALS - Scott
Almost done w/template generation (authoring)
Taking the evaluation and presentation aspects of; Scott working on taking, hand off to Phil; interface ie viewing what evals are available now on Scott's plate; coordinate w/Chris for mockups of listing on MyWorkspace to linkto or access eval tool embedded in course site.
Gradebook - Beau asking for patches from IET
SOM - working w/vanilla Sakai and Ilios; what changes will they need to go for working design?
CERE updates: Tuesday at 5pm
73 trained faculty ready to use CERE; 25-27 instructors teaching in the fall; Schedule data not available yet, next week's update is target date - may not require restart though;
Notify faculty during training sessions
Ready for Jan to notify all faculty?
Schedule update to CERE training this coming Friday - next session on Wednesday of next week
First deploy with all data & roles fully set
ALERT!!
Need to run all roles to CERE and reload courses
Curriculum manager role needs to exist for Erin
Schedule for today - Rick/Dave to check out production this afternoon
Tomorrow - notify Jan (if all goes well)
Rick - questions from faculty
Allowed changes made in CREST will be updated to CERE, changes will appear immediately - batching is to verify changes/cleanup. Although 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
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