You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we allowed the WWKenya team to classify on the main workflow (not a specific copy) to ensure classroom contributions count to the research outputs, we came across an issue where changes to the default workflow in the lab may not propogate to the education API and thus student assignment classifications may not count correctly to the assignments.
Specifically in the past we explicitly specified a workflow_id (normally cloned so it’s not on the main research workflow) in the education API and used this to wire the front and backends for contributions.
However to support the WWKenya use case of classifying on the live reasearch workflow means we don’t specify a known workflow for the PFE wiring. Instead we use a default to allow research teams to switch this up as they see fit but still allow the student classifications to land on the ‘correct’ live one.
However the education api system links via the workflow id for tracking student / classroom contributions. Thus if a project is using the ‘classify on the live system’ setup and the research team switch workflows after creating an assignment the contributions won’t be counted correctly (the submitted classification workflow id differs from the one in the education api
So the body of work we need to support this is to switch to tracking contributions via the student assignment id vs workflows as the student assignment id doesn’t change and correctly links back to the assignment id (classroom).
We’d need to then provide this value to the front end to include in the submitted classification metadata so it makes it back to the education API.
We also need the education API to reflect on this value when deciding to include contributions for a student / classroom.
I believe the relevant code that needs to change is here but it’ll probably need to be thought about in context of the other data workflows as it may be a conflicting change vs ‘normal’ classroom data flows
When we allowed the WWKenya team to classify on the main workflow (not a specific copy) to ensure classroom contributions count to the research outputs, we came across an issue where changes to the default workflow in the lab may not propogate to the education API and thus student assignment classifications may not count correctly to the assignments.
Specifically in the past we explicitly specified a workflow_id (normally cloned so it’s not on the main research workflow) in the education API and used this to wire the front and backends for contributions.
However to support the WWKenya use case of classifying on the live reasearch workflow means we don’t specify a known workflow for the PFE wiring. Instead we use a default to allow research teams to switch this up as they see fit but still allow the student classifications to land on the ‘correct’ live one.
However the education api system links via the workflow id for tracking student / classroom contributions. Thus if a project is using the ‘classify on the live system’ setup and the research team switch workflows after creating an assignment the contributions won’t be counted correctly (the submitted classification workflow id differs from the one in the education api
So the body of work we need to support this is to switch to tracking contributions via the student assignment id vs workflows as the student assignment id doesn’t change and correctly links back to the assignment id (classroom).
We’d need to then provide this value to the front end to include in the submitted classification metadata so it makes it back to the education API.
We also need the education API to reflect on this value when deciding to include contributions for a student / classroom.
I believe the relevant code that needs to change is here but it’ll probably need to be thought about in context of the other data workflows as it may be a conflicting change vs ‘normal’ classroom data flows
education-api/app/operations/kinesis/count_classification.rb
Line 34 in 6f80e45
The text was updated successfully, but these errors were encountered: