Celebrate Excellence in Education: Nominate Outstanding Educators by April 15!
Found this content helpful? Log in or sign up to leave a like!
There seems to be a few questions here about the definitions for what workflow_states for different contexts actually mean. I get this question a bit when providing data to people and it can be hard to find the actual information. Because the data uses different language to the UI it would be good if we could get some kind of legend for how the values map to the LMS
Does a resource exist where these are all defined so I can confidently advise what they mean?
Here's all the definitions of the workflow_state parameters for the "courses" table:
-Brent Rasmussen
A.T. Still University | LMS Administrator | brasmussen@atsu.edu
Similarly, the definitions for Submissions are also a little hard to interpret, particularly unsubmitted. Our Canvas Data Technical Consultant (Mark Valentine, wonderful!) told me that all assignments created unsubmitted submission records when they are created, as they assume that all assignments will have submissions from every student (adorable). Then when a student submits something that record is changed to submitted, when graded it's changed to graded. Deleted is if the student drops the course or something.
Cheers!
"Adorable" 🤣- reading this made my Saturday morning more enjoyable.
I've always found it hard to nail down workflow_state definitions for CD. I often have to go into Canvas and see what it aurally looks like in the UI to try to piece together definitions so I can reliably create reports that show what I want them to show.
To participate in the Instructure Community, you need to sign up or log in:
Sign In