Home Projects Jobs Clientele Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Implementing UMO Problem

Here is the possible solution. IMHO, an answer is the correct solution. We already have a table for solutions, "problem_solution". We may have a flag in this table, "ps_is_answer", and corresponding functions answer_{create,modfy,delete}. This provides us with the following extra functionality:

1) It's possible to have zero to several correct solutions
   For instance, for the problem with headache, the possible solutions are:
     - get the Panadol
     - get on the fresh air
     - cut-off the head
2) It is possible to have several solutions of the different type

I suspect that it is not necessary to create an answer at the moment when a problem is created. In general case, the problem may exist without an answer (solution).

2007/5/26, sergey@total-knowledge.com <sergey@total-knowledge.com>:
> There is a only one table, 'solution_type' to support that part. I don't
> have a clear understanding on how to define an answer at the moment. You
> can, for now, assume, that there is a field sp_answer text that contains
> an
> answer description. I'd add support for this field in study_problem and
> procs in about 4-5 hours (I need to logically finish class-related
> things).

No problem, I'll continue with other stuff.

> Please, give me your vision of answer presentation, if any, or we can ask
> Ilya and Anatoly.

Sure, here is how I understand it:
(ignore Objectives text area field).

> 2007/5/26, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>> I'm working on Problem functionality and I noticed that stored
>> procedures
>> problem_create()
>> problem_add_content()
>> problem_modify_content()
>> miss "Answer" field. Here is the link to the spesc:
>> http://www.total-knowledge.com/wiki/index.php/UU#Problem
>> Also these procs don't deal with difficulty levels and "required time to
>> solve" that mentioned in the specs.
> --
> Alexey Parshin,
> http://www.sptk.net

Alexey Parshin,

Authoright © Total Knowledge: 2001-2008