...
Will need to schedule a patch to correct for this issue, plus some taking eval submission logic, and a template deletion error fix.
_*System patch and restart after fix has been tested is scheduled for Thursday, October 5th @
5pm*_.
QA testing on Friday, October 6th.
...
Update for patch for printable schedule pending; ColdFusion now loaded on media server.
Ray will be rescheduling CRON jobs to between 3am-4am followed by other update processes.
PROCESS ISSUES
Chris & Dave get calls from instructors asking that they add users into their courses, i.e., auditing and university extension students. There is No access via the provider since they are not enrolled and do not show up in Banner. Beau is concerned because there is no ability to audit or maintain these users over time.
Provision What will be the provisions for user model? Possibly For possibly expiring users? Issues w/The issues are twofold: 1) the manual process of adding users, and 2) users being in the system forever. Expiring student How do we handle expiring students who drop out of a class/school. KName What about kname changes?
Enrollment is based on checkbox in SiteInfo. Winter clean-up between Sakai and provider based on student role? Mechanism and maintenance list for users outside the provider? Issues of exposed materials to users who instructor has requested access tofor?
Desire Team desires to identify the difference between provider-added and manually-added users. Long term issues of access to CERE for ever-increasing pool of users. Cutoff point? X years?
Need to review and determine scope of issue before making decision for fixing.
Issues Ray suggests planning for a winter clean-up between Sakai and provider based on student role.
There are issues of new user information in CERE and CREST as well.Scheuling fo CRON jobs shifting to between 3am-4am followed by other update processes. CREST implementation of users uses termcode. Need to resolve story about users across various systems for consistent usage.