VetMed Developers Meeting
CERE Integration
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
...
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);
Status of taking the evaluation and presentation aspects of; Scott now working on taking evaluation portion, but will hand off to Phil; Scott will shift to working on the interface, i.e., viewing what evals are available. He will coordinate w/Chris for mockups of evaluation listings on user's MyWorkspace to linkto or access evaluation tool embedded in the course site.
Gradebook
Beau asking for patches from IET; no response?
School of Medicine (SOM)
SOM is working with vanilla Sakai and Ilios; what changes will they need to go for working design?
...
Production Deployment Issue
Curriculum manager role needs to exist for Erin; need to run all roles to CERE and reload courses; 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:
Will allowed changes made in CREST be will be updated to CERE right away?
Response: Changes in CREST will appear in CERE immediately. The batching process is to verify changes/cleanup.
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