Home Projects Jobs Clientele Contact


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

Re: course <-> topic, take 3

Ilya A. Volynets-Evenbakh wrote:

Unit of content organization. It is umbrella under which sub-topics,
explanations, texts, tests, etc. are gathered.

Administrative entity that encompasses certain content structure
for purposes of linking it with students.

What this means to end user.

A. Course is non-shareable entity (this is a change from original spec).
This does _not_ mean its content is not shareable. Just the administrative

B. When user creates course, interface is such, that he sets up
features separately from content.

C. Interface to creating content of course can be organized in exactly same
way as interface to creation of any topic, as it really has all the same
as normal topic.
Could you mark necessary changes to specs below to reflect your your understanding, point C specifically?


[edit <http://www.total-knowledge.com/wiki/index.php?title=UU&action=edit&section=15>]
Necessary Features

   * Title

   * Author(s)

   * Choice of server:

Open Server or Proprietary one

   * Choice of access for students:

         o Free or Paid Course

[edit <http://www.total-knowledge.com/wiki/index.php?title=UU&action=edit&section=16>]
Optional Features

   * Topics.

   * Tests

   * Competitions

   * List of experts

[edit <http://www.total-knowledge.com/wiki/index.php?title=UU&action=edit&section=17>]

     Necessary Features

   * Title

[edit <http://www.total-knowledge.com/wiki/index.php?title=UU&action=edit&section=19>]

     Optional Features

   * Summary (Annotation)

   * Test

   * Explanations

   * Blocks of problems of different difficulty levels

[edit <http://www.total-knowledge.com/wiki/index.php?title=UU&action=edit&section=20>]

What this means for logical organization of functionality (Model layer).

Course becomes a direct derivative of topic: it basically has same
as normal topic (has problems, tests, subtopics, etc). Plus it has some
functionality: it takes care of students signing up for it, getting
grades (if we
ever implement this kind of thing), etc.
Doesn't hurt as soon as end-user finds course and topics where they belong: course is the face and topics are listed in the course content.

What this means on data layer:

Course becomes an additional set of data pieces that is associated with some
topics. In other words: each course has a TLT (top level topic), that it
is associated

I need clarification here. I understand that logically a course does have kind of TLT (say Geometry), but normally it does not have it structurally, right? And if you want it structurally, how would it look? My first impression is negative, but I'm ready to look into it.
 More then one course can have same TLT - this is how course
is implemented. Topic doesn't have to have direct relationship with course
(could be just a stand-alone object not yet used anywhere, could be subtopic
of some other topics).

try to keep all three layers in mind.
Did I fulfill the last requirement right ? :)


Anatoly Volynets, Co-Founder

Authoright © Total Knowledge: 2001-2008