Open iturgeon opened 5 years ago
We may be able to address this using play log context IDs. The way we're using those right now is by scoping attempt limits to context IDs - so a single widget with an attempt limit embedded in two different courses via the LTI can be played up to the attempt limit in both courses. The attempt limit is still being handled fully in Materia, though.
It probably wouldn't be too hard to enable an external tool setting an attempt limit or availability window on an embedded widget, but whatever it sets those to will be in effect for every other context.
Currently attempt limits and open/close dates are an instance-level thing, but if there's a possibility that one context's needs are different from another context's needs then we'd need to track them at the context level. That's potentially a lot of effort, though.
Picture this issue:
Obojobo Next embeds a materia widget. The instructor sets obojobo so it can be taken 3 times. They set Materia so that it can be taken 3 times.
Since those 3 times are not related: IE the materia widget could be played 6 times if they have this same obojobo module in 2 courses.
Investigate a way to let the thing that's embedding materia dictate how it's used.