I want to assign daily bell work to my students. I do not want to set up an assignment for everyday of the class. Is there a way to create 1 bell work assignment and have them submit multiple submissions. Would it be able to record how many submissions a student submitted?
That is very helpful! Thank you so much!
On Fri, Nov 17, 2017 at 10:08 AM, Kelley L. Meeusen <instructure@jiveon.com>
Hi Melissa,
As long as the assignment does not have a due date then the students can submit as many times as they want.
After the first submission the button will read "Re-Submit Assignment".
While in Gradebook view for individual students look to the right and you will see "Submission to view", there you will see all the submission the students have done by with a date and time.
Hope this helped.
With the ability to duplicate assignments (this is a recent thing), creating one for every day is not nearly as hard as it used to be and should really be considered as the best solution for this. Have generic instructions that are not date or assignment specific and then copy the assignment and change the due and availability dates. If I had this everyday, I would duplicate them at the beginning of the course, then use my Google Sheet that allows you to bulk edit the dates: Adjust All Assignment Dates on One Page. It also allows you to change the name of the assignment. So I would create one for every day and then it's good to go. If you decide that there is no bell work for that day, just unpublish the assignment. If you find that students are messing with you by completing things early, then keep them unpublished until you're ready to turn them on. Another option is to make the available from date be really close to the end of the bell on the day. This can be accomplished by setting up formulas in the spreadsheet that calculate the availability based off the due date.
People are suggesting comments, but there are potential downsides to them that may be unacceptable.You should at least be aware of those going in. You may decide that they are acceptable. The bottom line is that this is not how Canvas is designed to work and so there are going to be trade-offs to get it to function in this way.
A student may resubmit an assignment unless there is an available until date, but it gets removed from their To Do list once they submit it the first time. Many students live and die by the To Do list. You would want to make sure that the location where they are to turn in the grade is prominently featured on your course homepage. If there is no due date, then it does not show up on the To Do list at all.
Both solutions require manual intervention on your part to determine the count. Either by inspection or by physically clicking on items.
Going back to it's really designed to have separate assignments, If you happen to be using a weighted gradebook with assignment categories, then you can put each of those assignments into their own group and make them worth 1 point. Make the overall assignment group worth 0% of the grade, unless you actually want to give them some credit for just turning things in. Then you can look at the gradebook and see how many times they turned it in by looking at their score for that section.
This does have the impact of filling up your gradebook with a lot of assignments. If you don't want that, then one of the other approaches may be better, but I think it's going to be more work in the long run.
I'd like to add my support to James Jones' suggestions here! To simplify grading for daily assignments, you could assign 0s to non-submissions and then set a default grade for the rest (How do I set a default grade for an assignment? ).
And to add to the disadvantages that he points out, though students can resubmit assignments to Canvas, and teaching team members can easily navigate to the earlier submissions, it's not nearly as easy for students to see those earlier submissions. When they go into grades to see feedback on the assignment, they see only the latest submission -- the earlier ones aren't visible.
Feedback provided as assignment comments in SpeedGrader will be visible, as would any rubric used. However, if feedback were provided using the annotation tools in DocViewer, it's likely that feedback would be invisible to students.
Another option would be to use individual graded group discussions for this purpose. Group discussions are visible only to group members. Using Canvas' group creation tool, you can automatically create groups equal to the number of students, and Canvas will place one student into each group. The advantage to this approach is that there is only one assignment created, but students can submit to it each day -- and if it's a group discussion, their contributions are visible to only themselves and the teaching team. All submissions would be visible (submissions would be replies to the original discussion) at all times, and there would be only a single grade for the assignment (rather than a grade each day). And I believe that James has a Canvas enhancement for counting discussions replies -- though I haven't actually tried it. (See How to Count Student Discussion Posts .)
Good luck!
Thanks for chiming in with the other issues. I knew there were more, but was having trouble thinking of them at the time.
A potential problem with the group discussions is that they can be posted to at any time and the counting is done for the discussion for the entire semester. A student could go in and post 20 replies in a single day and look like it was 20 days under this approach.
Oh, excellent point about piling on all the work at the end!
Hi Melissa Checketts
Yes, and there are two ways you can use it to count the numbers of submissions.
I hope this is helpful.