1. There are many different "solution" types. Teacher-verified is only
one of them.
(all others are actually verified automatically, immediately upon
I just updated that page with some specifics on what each solution type is.
2. Teachers are tied to a course. This means we'll have to build fairly
query to figure out who the problem solution for teacher-checked problems
gets submitted to.
3. Remember - we store all solutions submitted to problems forever
(regardless of their current access to given problem)
Can you explain how you are addressing (or plan to address) all of above?
Alexey Parshin wrote:
> The problem is solved, if solution is presented and signed by some
> While placing the signature is trivial (another table with id and two
> references, to solution and to teacher), we still have to think on how
> to enforce the "teacher" role. Is it one of the ACLs for the problem?
> 2006/11/3, Ilya A. Volynets-Evenbakh < email@example.com
> OK. This looks very good to me. Even better then what I had originally
> in mind
> (Per-object notifications, that would be sent to all authors in
> case of
> object change). Per-object per-user preferences are certainly better!
> Now, another thing that Sergey brought up, and which wasn't
> answered yet:
> >> Also how do we know if a problem was "solved"/"not yet solved"
> by student?
> Alexey Parshin,
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
Authoright © Total Knowledge: 2001-2008