Re: Logical relations between students/teachers/etc and groups, classes, and courses

["Alexey Parshin" <alexeyp@gmail.com>]

Ok, here is the first obstacle. If the course exists (and point to UMO base), and I have to add a topic to the course, do I:
a) find the latest unpublished TLT in the course, and connect a topic to it
b) assume that we only do such things on topic level. GUI offers a list of unpublished TLTs to connect to.
c) ?

Here is the second obstacle. If the course exists, and I have to grant a permission to a group to this course, do I:
a) find the latest published version of TLT and grant the permission to it (and to the whole tree, of course)
b) assume that GUI should offer the list of published versions of the TLT, and grant the permission to selected version
c) ?

2008/7/10 Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:

Alexey Parshin wrote:

2008/7/10 Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com <mailto:ilya@total-knowledge.com>>:

   Alexey Parshin wrote:
   > Object relations:
   >
   >    1. The central unit of hierarchy is Class. Class has a title
   and description.

   >        (There is still a question about title/description in
   preferred language, but that's a separate issue).
   >        Class may be connected to any number of courses, and vise
   versa (many to many r/ship).
   >        Class may include several groups with different group
   types (TEACHERS, STUDENTS, etc).
   >        Class also defines subscription rule that defines ether
   the class is free or has a price or a periodic payment.
   >    2. A course is defined as a record with a compulsory
   reference to TLT (Top Level Topic) version.

   >        Therefore, a course defines a version snapshot of the UMO
   hierarchy for the TLT.
   That's not what the original design had. Course is an object
   connected to TLT.

Do you mean that course is a UMO?

No.

-- 
Alexey Parshin,
http://www.sptk.net