To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/sakai-dev/7A7042C9-FC4D-4A19-81BC-CC6F79154FA8%40umich.edu.
You received this message because you are subscribed to the Google Groups "Sakai Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-user+...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/sakai-user/CAMddi3154zwR6q60buvnjMVq951C-AZXCwJzk5%3DaArMYdRuTfQ%40mail.gmail.com.
-1
The proposal would induce a significant behavioral regression for instructors at my institution who use one course site for a given academic term with multiple (usually two) sections/groups of students. E.g., one group meets M W F and the other T H, where each group has distinct due dates, necessitating separate assignments in the Assignments tool, discussion activities in the Discussions tool, and assessments in the Tests & Quizzes tool.
So that the Gradebook (at least from the instructor’s perspective) does not grow inordinately large (and item titles unnecessarily long with group name identifiers), we have advised instructors to make use of a single gradebook item to be used by multiple assignments, each representing the same activity though distributed to a distinct group. This simplifies the Gradebook size (and the titles of items), which makes managing Gradebook for instructors significantly less cumbersome.
I also recognize that this technique cannot be extended to T&Q currently (though that would be nice), Lessons graded questions and comments, etc. However this technique is currently used by instructors for activities administered through Assignments and Discussions.
Furthermore, there is the matter of the danger of using Gradebook’s Course Grade > Set Zero Score for Empty Cells feature when multiple gradebook items are not relevant for all students in the course site. More about this issue where the aforementioned technique is used as a mitigating measure is detailed here: https://kb.plu.edu/137719.
All this said, if the proposed behavior change moves forward, I request that it not be backported to Sakai 23. It’s much easier to introduce such behavior changes to users during communication campaigns for a new version of Sakai, when announcements of several feature enhancements coincide with feature changes that some otherwise perceive in a negative light.
Thanks,
Sean