inducer
Discussion: flow for a subset of participations
There is a situation when only a subset of students were required to finish a flow individually. In this case, the grading/by-opportunity view should only list that subset of participations, instead of all participations of the course.
The filtering criterion can be roles, or ptags. And I think this can be done through adding a few fields in the GradingOpportunity data model, e.g., restricted_to_roles_all, restricted_roles_any, restricted_to_participation_tags_all, and restricted_to_participation_tags_any.
Is this a grade book thing to you? Or a flow thing? Or both?
FWIW, I'm not sure I'm super in favor of bolting some ad-hoc rule system for who needs to submit into the data model (because the data model is hard to change, much harder than the flow language). Instead, I'm debating whether we should create an auxiliary m-to-n table of "assignments", connecting submission entities (cf. #742) to grades or flows. A good question is when those assignments should be created.
Currently, it's only about grade book (by-opportunity only).
Is this a grade book thing to you? Or a flow thing? Or both?
That sounds more reasonable. Because currently a flow can be used only once by a single grading opportunity. If we want that flow to be used again by another gopp, we need to have a duplicated version of that flow.
Instead, I'm debating whether we should create an auxiliary m-to-n table of "assignments", connecting submission entities (cf. #742) to grades or flows.
Do you mean that If there were the assignments, the flow rules should be moved elsewhere, That will be a huge change.
A good question is when those assignments should be created.
That sounds more reasonable.
Not sure what you mean. What sounds more reasonable?
Because currently a flow can be used only once by a single grading opportunity. If we want that flow to be used again by another gopp, we need to have a duplicated version of that flow.
I disagree, cf. what I proposed in #742.
Do you mean that If there were the
assignments, the flow rules should be moved elsewhere, That will be a huge change.
No. I thought we were discussing something to describe which participant should attempt a flow. That's distinct from "being allowed to", i.e. the flow rules.
I mean the submission entity idea you proposed in #742 .
What sounds more reasonable?
I mean your proposal can solve that issue.
Because currently a flow can be used only once by a single grading opportunity. If we want that flow to be used again by another gopp, we need to have a duplicated version of that flow. I disagree, cf. what I proposed in #742.
That makes sense.
I thought we were discussing something to describe which participant should attempt a flow. That's distinct from "being allowed to", i.e. the flow rules.
A simpler workround might be adding a participation tag filter in the gradebook, if we are not expecting the submission entity in a near future.
I view the submission entity bit as orthogonal to this, as submission entities (as I see them) have nothing to do with the grade book. They would simply submit the same grade for everyone that's part of the submission.
I'm not opposed to allowing the grade book to filter by participation tags, though.