...
View tool looks at course-related data and facility scheduled data which will replace existing view (course only) in release of 2.0 release.
EVALUATION - Phil, Scott
Issue found prior to deploy - recent deployment, but not addressed yet. Issue is limited in scope .
Instructor and affects the instructor question level - if . If the instructor is changed during the eval evaluation form creation process, the screen does not update automatically. Only the instructor of record gets instructor-specific questions, so changing the ior questions need to be reassigned to the new ior upon update (currently not re-assigned to new instructor automatically.) . Other instructors get brief rather than detailed questions on the evaluation form.
Needs 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. Testing
QA testing on Friday, October 6th.
Ray Will will contact Roger McDonald and Jan and ask them to complete creation of their evaluation forms by Friday, October 6th; plan to release evaluations for students to take on by Monday, October 9th.
Auto-generation of Evaluation tool on students menu?
Scott will implement via Java in Sakai w/to upload with the Thursday patch or in Sakaiscript (not required as a patch release.)
Need Final housekeeping on evaluations - need to delete unwanted templates from database.
SYSTEMS - Beau
Beau - Update for patch for printable schedule pending; CF 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 students and university extension students. No There is no access via the provider for manually added users since they are not enrolled . Do and do not show up in Banner. No 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 class/school. KName a class? 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.