Status Update
No update yet.
Comments
rp...@google.com
jl...@google.com
am...@google.com
ta...@finixpayments.com
In my opinion, at least one of the two should change with regards to the behavior of Excusing an assignment:
1. Any original score returned to the student should be erased from the submission entirely. This should make the returned grade empty/null, so the API response does not need any special indicator for an excused grade.
2. If a returned grade should still be associated with a submission (but not count towards the overall grade like the Google Classroom UI calculates), then this same flag/indicator should be exposed via the API so that a similar overall grade calculation can be performed from the API response.
ta...@finixpayments.com
Thanks for providing feedback around supporting excused assignments in the Classroom API! I've made a note of your comments and transferred them internally. Any updates about this will be communicated here.
am...@google.com
We are an SIS that consumes Classroom data via the API.
What we are observing:
- we don't get StudentSubmissions where student was never scored and was excused, so parents are confused thinking that work is not done when it should be excused when looking in our platform.
- When a student is scored, grades are synced, then excused, we don't get the update that the assignment was excused. So now the student has a score (0 or otherwise) that doesn't reflect what's in Google Classroom, creating discrepancies between Classroom assignment grades and SIS assignment grades.
ta...@finixpayments.com
Thanks for providing supporting feedback. I'd love to learn a bit more about your comment:
"we don't get StudentSubmissions where student was never scored and was excused, so parents are confused thinking that work is not done when it should be excused when looking in our platform."
Can you provide more information on the API call you are making here so I can try to figure out the issue? I'm not able to reproduce this at the moment; when reading student submissions by calling ListStudentSubmissions, I'm able to retrieve submissions that are marked as excused in the UI.
"When a student is scored, grades are synced, then excused, we don't get the update that the assignment was excused. So now the student has a score (0 or otherwise) that doesn't reflect what's in Google Classroom, creating discrepancies between Classroom assignment grades and SIS assignment grades."
Trying to understand this issue a bit further - if I understand correctly, there may be grade discrepancies between Classroom and SIS in the event that a teacher modifies a grade after the grades have been synced with the SIS. Do you have a mechanism today by which you monitor these types of grade changes? If not, is being alerted about excused assignments more important than other types of submission changes?
am...@google.com
We use a platform (Schoolytics) that mines the data from Classroom via the API to give parents and students updates and reports about their students' progress. Unfortunately, excused assignments (e.g. because the student was not yet enrolled at our school) are being misidentified as missing.
We use Aeries as our SIS and gradebooks.
ta...@finixpayments.com
However, I am not sure if there is some other situation when {} gets added to the `submissionHistory` as well and thus breaking this workaround. I did not encounter any other situation when this happens.
UPDATE: As noticed by 34...@gmail.com, marking solution as complete by the teacher also adds empty object which breaks this solution unfortunately.
Description
AI-212.5712.43.2112.8815526, JRE 11.0.12+0-b1504.28-7817840x64 JetBrains s.r.o., OS Mac OS X(aarch64) v12.6, screens 3840.0x1600.0
AS: Chipmunk | 2021.2.1 Patch 2; Kotlin plugin: 212-1.7.10-release-333-AS5457.46; Android Gradle Plugin: 7.2.2; Gradle: 7.5.1; Gradle JDK: version 11.0.12; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)Source: send_feedback_icon
IMPORTANT: Please read
To reproduce:
Make an app
right click the directory "app" -> new -> module
select templates "Android Library"
Add an empty compose activity in the new library
Configure gradle as usual
Build the project successfully
You can see that the basic compose activity is not able to "preview" any composable