Home Projects Jobs Clientele Contact


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

Re: Difficulty levels

sergey@total-knowledge.com wrote:
So basically you suggest having 2 DLs - Community and Author's, it has to
be 2 different attributes. Also we should have 2 types of voting(regular
and DL related)

What is regular voting? This issue has not been developed thus far. I think now, we need to discuss a set of points to be vote and put them all into "ballot". There is another question what is to be done with each single point-attribute after that. DL is to be set as part of an UMO DL mark.

I can see Authors set DLs for UMOs in their Course(they shouldn't
participate in DL-vote)

I am not sure (but am not insisting) this limitation is needed...

I can certainly understand Teachers who set DLs for UMOs in the Course
they teach(they participate in DL-vote, I'm sure they would prefer to just
reassign misplaced UMO to the appropriate DL within a Course).

Why? I see to DL as totally different things: Author's one defines relations between this Author's UMOs. Community set DL defines relations between UMOs of different authors, that's it.
Let's say a recreational Student desides to participate in DL-vote.

First of all it's hard to imagine why would they do it, it's not a popular
movie that everybody watched recently. Usually students don't care much
about course structure, if they don't like it, they vote by not buying it.
Second of all, recreational Student has to be somehow familiar with all
available DLs in the Course, their titles and meanings, among with DL-type
of voting concept.

I believe it is not just students who can vote. Teachers, Experts and probably others can do it. To this end, if we talk about community revolving around a market place, there must to emerge kind of communication environment, where people are interested in giving away their opinions and listening to opinions of others, arguing about the issue and settling the accounts by voting.

Third, we must collect fairly large amount of votes to downgrade/upgrade
UMO to another level. Some punk can mark every UMO in the Course as "too
advanced" or some geek may think it's just "too easy". We don't want DL
rating to be affected by this kind of people(btw, they are the ones who
usually vote, others tend to move right away to something that better fits
their needs).

It is a problem. But I incline to ignore it for now. Let it depend on those who do want to express their opinion.

Imho, Teachers are the only ones who interested in managing DLs, maybe we
can only count their vote for DL?

We have to discuss it. The issue does not look obvious.
Anyways, I disagree with the whole concept of voting for DL. My opinion is
-  let's do it and see how it works in real life.

Do what?

Once again, there are two unrelated issues in one here:

1. An UMO difficulty level  (DL) in the Repository, which is set by
community voting  (probably by  authors and students  - this is to be
2. This same UMO DL in the course or among courses by the same Author,
set by the Author.

This is why I incline to have two part DL mark: n-m, say n - stands for
the Repository DL, and m stands for the DL set by the Author.

n,m are integers, starting from 0.

We probably need to foresee a situation when somebody discovers a
problem, which is easier to solve then one of DL =0. Any suggestions
about that?

Let's leave it as DL=0. Maybe it's easier for him to solve it because he
dealt with same kind of problems many times already.

Regarding any additional functionality (like work flow) that can be
derived from DL, I would leave it for next UU versions.

Anatoly Volynets, Co-Founder


Anatoly Volynets, Co-Founder

Authoright © Total Knowledge: 2001-2008