[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Re: Course<->topic relationship
Why don't we forget about course at all, treat _single_ top-level topic as
course, add some former course properties to "topic" and let "topic"
deside whether it's top level topic or subtopic.
> Looking at data model, it seems that somewhat cleaner way to design
> things is to make a _single_ top-level topic for a course.
> Reasoning:
> We will have subtopic lists, dependencies, etc. functionality in topic
> class itself. Also problems and tests belong to topics, not to course.
> Thus, course will be purely administrative unit, with no real content,
> that links to top-level topic, which will drive the rest of learning
> process.
>
> Objections?
>
> --
> Ilya A. Volynets-Evenbakh
> Total Knowledge. CTO
> http://www.total-knowledge.com
>
>