array(1) { [0]=> string(108) "
  • [[#cite_ref-0|↑]] This has nothing to do with parent-child relationships of UMOs
  • " } UU - Total Knowledge
    Total Knowledge Projects Jobs Clientele Contact


    Personal tools
    From Total Knowledge
    (Difference between revisions)
    Jump to: navigation, search
    (Proprietary Server)
    (Dialogue of Texts)
    Line 409: Line 409:
    * As list of "points", with references to places in each text where these points are discussed
    * As list of "points", with references to places in each text where these points are discussed
    * As interleaving texts, for cases where arguing texts are organized similarly enough for that to make sense.
    * As interleaving texts, for cases where arguing texts are organized similarly enough for that to make sense.
    === UI and workflow ===
    One possible way to present DoT editing is the following:
    * User creates list of relevant texts
    * User is presented with a double-pane window, selected text on one side, output on the other
    * User selects a quote in the text
    * User clicks "Add" button
    * The quote appears in the output pane, marked with the origin (Text name, possibly specific colour)
    * User can add own comments to the quote. They appear on the margins.
    Workflow for the DoT studying:
    * User is presented with the page of "Quotes".
    * User can click on any quote to see whole original text, in order to see the quote in context. The text is automatically scrolled to the quoted place.
    * User can expend any quote in-line, in any direction. Such expensions are marked visually (e.g. by different colour)
    * The DoT authors' comments appear on the side, as pop-ups while user scrolls the text, or on the margins, if there is enough room.
    == Text In ==
    == Text In ==

    Revision as of 05:53, 29 August 2014

    Universe University. Specifications for Web Based Educational Environment



    The Goal

    Universe University aims to answer the most pressing challenges to modern education. Nowadays, the core demand to educational systems is to provide for development of independent and critical thinking, creativity and responsibility. We believe these goals sound good for anybody today but real construction and technology of the modern schools go back to 17th century and can effectively provide only informing and training. All the rest is up to a teacher. Our understanding is that modern school has to be reconstructed entirely so that priorities could be switched. The whole educational process must aim directly on thinking and creativity. Students must enjoy and be interested in the subject itself vs. worrying about credits and other superficial reasons. If this happenes then information and skills, or generally speaking, knowledge of traditional type will be acquired as a side effect and in much better degree.

    Educational Principles

    There are two major principles contemporary education should be based on: dialogue and problem solving. Correspondingly we want these to be implemented within Universe University in different ways.

    Dialogue will be provided in the following features of the environment.

    1. First, directly through different communication tools, which can be used in conjunction with work on studies or course development. We intend to build organic system of all suitable communication protocols to be embedded in the Universe University: message boards, chat rooms, etc.
    2. Second, we offer special feature for course structure, which allows one to create what we call "parallel explanations" for each single topic. That is, an author may use absolutely different explanations for a single fact, including those, which interpret it in opposite directions. Such an approach was traditionally considered unacceptable, because a traditional course is built sequentially. However, sequential courses do not awaken thinking this way. If a student encounters different explanations for a single fact, this will rise questions, which is the first step in thinking.
    3. Generally, Universe University offers an environment to built courses of "open source" type. That is, different people may participate in a course construction, bringing in different approaches, stand points, understanding of a subject, and so forth. This alone develops definitely dialogic environment, attitudes and mood. On the other hand, those authors, who are not inclined to do work in cooperation with others, have at their disposal tools to do it alone.
    4. Universe University is supposed to offer various tools for feedback on courses, single topics, problems, problem solutions, authors, and so forth, which is also a normal dialogic form.
    5. One more tool featuring dialogue in UU is also unique, though functionally very simple component, which is called "Dialogue of Texts". Dialogue of Texts is not a course, or is not included in a course, neither does it includes courses. It is exactly, what it called: dialogue of texts, a collection of texts contradicting each other and having some specific features. This work of high level experts, scientists, scholars implies the same idea: to provoke thinking.

    Problem solving feature will be provided with the following tools of the environment.

    1. Each single topic of a course can feature blocks of problems of different levels of difficulty.
    2. A problem consists of a "problem statement" and a "solution control definition". Solution control definition determines exact way of providing student with an interface to enter his answer and the way to determine if the answer was correct. We plan on providing following solution control definition types initially: single answer, multiple choice, solution template, semiotic model
    3. We also plan to implement the generator of formalized classes of problems/exercises to ensure training of any level of perfection, whenever a course author finds it necessary.
    4. A course may include built in testing, rating and work flow based on the pace of problem solving.
    5. UU allows to conduct cross-course problem solving based contests and rating system.

    User Manageable Objects - UMOs

    User Manageable Objects (UMO) are main building blocks of UU. Courses, topics, problems, etc. are all types of UMO. UMO is the object which can be studied. UMOs may be constructed from other UMOs (depending on type). For example, a topic consists of sub-topics, explanations, problems, etc..

    Common UMO Features

    Common UMO Properties

    Every UMO has a set of standard features, such as UMO author, UMO type (see below), UMO version (an integer number of version), a date when UMO was created, and an optional date when UMO was published. The create date, UMO type and author are filled in once when UMO is created, and never modified. A publish dated is set when UMO is published, and locks UMO in published state. A UMO description is optional, and may be omitted. That is to a contrast from UMO title that must exist and be non-empty.

    Some of the UMO properties, like title and description, may exist in several languages simultaneously. Such properties are stored as content records. When UMO is created, at least one content record is created, to hold UMO title and description in this UMO default language. There is no limit to a number of content records, however only one content record per language can be created.

    Available UMO Types

    • Course
    • Dialog of Texts
    • Topic
    • Explanation
    • Problem
    • Game
    • Exercise
    • Link to

    UMO Sharing

    • Same object can be used in multiple other UMOs without limitations (depending on UMO types).
    • Same object can be worked on by multiple users - depending on its author's assignment.
    • A course can be copied by a user for business purposes. In this case only proper attribution required (see Licensing).

    Stamp of Authenticity

    • It says, what this object is in terms of authorship:
      • An original + who is the author or
      • One derived from someone's original + who is the author and other info about the original + who is the editor or
      • A borrowed object + who is the author and other info about the original
    • It includes the time stamp of its creation.

    Object Versioning

    Every UMO may exist in several versions. A version is created when there is a need to create a modified version of existing UMO. The new version of UMO derives the original UMO version' title, content records, and administrators and editors groups. The user that creates a new UMO version becomes that UMO version' author.

    Let's say user X creates object O. The user Y uses O in his course. Now X changes O. Will the course include edited version of O, or original one? Ideally it should be up to Y to decide that. This leads us to the concept of object versioning. i.e. each change to an object creates a new version, and old one stays. When linking objects to each other (e.g. adding problem to topic) author decides which version to use.

    Optional Features

    • Properties

    Properties can be created for any UMO for storing some special UMO information that may be represented as pairs of names and values. Every property has a type and a string value. Property type defines property name and a type of UMO the property can be used with. Properties can be used for searching.

    • Keywords

    Keywords are made of UMO content title and description. This is completely automatic process that runs when UMO content is created or modified. Keywords are indexed so keyword-based searches are very fast.

    • Work Flow (Prerequisites and possibilities) - for next version!!!
    Each UMO can include or be included in a work flow:
      • Each UMO can say which other objects can be useful if acquired by a student beforehand, shortly - are prerequisites to study or exercise this one.
      • Each UMO can specify possibilities for further studies this object brings in.
      • Each UMO can be completed by a student
      This property will be tested by dependent objects to implement the work flow.  
    • Faculties/Objectives

    Each UMO can say what student faculties or other the UMO author's objectives it was created for.

    • Outside References

    Each UMO can refer a user to outside (not UU bound) sources related to the object.

    • Statistics
      • Usage in other UMOs
      • Usage by students
      • Usage by authors
    • Rating

    Each UMO can be rated by users


    Course is a UMO which represents collection of other UMOs, and which allows classes to be signed up to it. The only way to study an UMO in UU is to sign up for some class, which is signed up for a course, which contains the said UMO.

    In all other respects, course behaves just like a regular Topic#topic.


    Topic is main structural object of a course. It allows course authors to organize other UMOs for presentation to students. Topic can contain subtopics, explanations, tests, exercise problems, etc. Basically any UMO except for course can be linked as a child to a topic.

    Required properties

    • Explanations

    A topic can be published if at least one explanation is supplied by the author

     Each topic can have number of explanations. In this case, each explanation has some
     unique number, which reflects order to show explanations in explanation list for the
     topic. This number (together with difficulty level of explanation) will also affect
     which explanation is shown to a student by default.
     Note that both sequence number and difficulty level of given explanation are
     tied to the topic that includes said explanation, not to explanation itself.

    Optional Features

    • Summary (Annotation)
    • Test
    • Blocks of problems of different difficulty levels


    An author may write his own explanations or include chunks of classical texts. He may neatly explain some subject, ways of problem solving or make a discourse around a topic, research his subject instead of explaining. A author may make just one explanation for a topic, which is traditional way to build courses. However the app allows to build unlimited number of parallel explanations.

    This feature may be used to provide:

    • Any number of short or detailed explanations, so that a student could use that one he needs.
    • Different approaches for the same subject to provoke dialogue between students and critical thinking.

    Necessary Features

    • Title is <the same as of its Topic>dot<Specific title>
    • Number, starting with 1, incrementing by 1
     Number is really associated with Topic, not with explanation, as an explanation
     can be shared between different topics.

    Optional Features

    Text of the explanation


    Necessary Features

    • Problem statement,
    • Solution and
    • Answer.
    • Choice of solution control
      • As of today, 5 solution control methods are being developed:

    1. Single Answer

    Student is presented with a problem statement, and a single one-line field,
    where (s)he has to type his answer in. Student's answer should match the correct
    answer (match can either be case-sensitive or case-insensitive, and it could be
    simple text, or a regexp)

    2. Multiple Choice

    Student is presented with a problem statement and a set of choices.
    Choices can be either radio button set (in case only single answer is
    allowed) or a check-box set (in case more then one answer could be
    correct). In case of multiple correct answers, problem creator may
    specify whether all answers have to be checked for solution to be considered
    correct, or if any of them will suffice.

    3. Template

    Student is presented with a problem statement, and a problem solution
    with blanks, which (s)he has to fill in. Each blank should match.

    4. Generator driven full control:

    a) Semantic Model
    b) Custome/Language Driven Control

    5. Human controlled

    A student solves a problems and passes the solution in a required form to the teacher
    that, in turn, passes comments to the student.
    • Level of dificulty

    It is a number, starting with 1, incrementing by 1, but can go in opposite direction as well: 0, -1, etc.

    Optional Features

    • Required time to solve

    Work Flow - This is in discussion and to be implemented in the next version if any (see Optional Features)

    The Idea

    There must be an ability for an author to implement some educational scenarios comprising instructions or procedures to folow by a student or group of students. It can be based on different psychological foundations or just an author's experience.

    Forms and Features

    1. A work flow can be implemented in a form of:

    • A flow-chart or
    • Pseudocode, consisting of sequences, choices and cycles of actions to do or
    • Just a set of rules
    • It can be "virtual". That means it is invisible, may or may not contain controlling feature and controls a sequence of UMO offering to students so that they get aquired in certain order, but the order is not controlled by students.
    • A work flow also may include means of control whether a student or group of students follow the work flow.

    Relationship with other UMOs

    • Work Flow can be attached to any object
    • Work flow can organize any objects, including courses


    • Test can be attached to any other UMO.
    • A test may include undetermined number of:
      • Problems,
      • Exercises,
      • Games
    • There can be Test Templates, for example:

    5 randomly generated problems would represent a particular test.

    For test problems only time allowed should be specified.

    "PASSED" or "NON PASSED" grade should be assigned.

    Points for "PASSED" grade should be specified for each test.

    In order to get "PASSED" grade 6 times allowed to take a test.

    The rate score ( RT ) should be assigned to each student after successful completion of test. (based on the time deduction principle, 10 sec = 1 point)

    RT is a function of only time specified for the test.

    In the case a student has RT not equal to zero, the system will let him/her to solve the general problems to improve their regular rating.( but only within this particular topic)


    General Idea

    A competition can be set on any UMOs of the same type

    All Features are Necessary

    • Type of Competition in Terms of Time:
      • Continuous (e.g. problem of the day)
      • Real time
      • Long term rating (e.g. chess style mastership)
    • Types of Competition in Terms of Participants:
      • Competitors of the same type (individuals, classes, schools, etc.)
      • Competitors of mixed types (say, an idividual challenges a research lab)
    • Rules

    Homework - To be discussed and implemented in the next version

    • A homework can be comprised from any UMOs?
    • A homework can be attached to any UMO?

    Exercise / Games

    A game or exercise may be included by the author in the course or topic for different reasons. It is not controlled in any way.

    Through Problems

    An UMO of the course level. They are problems of different level of difficulty, collected on any bases.

    Necessary Features

    • Author - the person to start the collection.
    • Basis for collection
    • Problems in

    Through Problem can be created if at least one problem is supplied.

    Problem In

    • Necessary Features
      • Number, starting with 1, incrementing by 1
      • Links to previous and next if any
      • Presenter - the person to present the problem into collection
      • Author - the author of the problem, if available

    Dialogue of Texts

    Dialogue of Texts (DoT) is an UMO of the course level, that is a course independent object. They are classical texts compiled accordingly (see features)

    Necessary Features

    • Basis for collection
    • Author - the person to start the collection
    • Interconnected text list
    • Text In

    DoT can be created if at least one text is supplied

    Content of DoT

    Dialogue of Texts is organized set of texts cross-referenced on basis of arguments. Each dialogue has set of "points", and each text is broken into sections, that refer to these points. Dialogue can be presented to user in following ways:

    • One text at a time, annotated with links to relevant "points"
    • As list of "points", with references to places in each text where these points are discussed
    • As interleaving texts, for cases where arguing texts are organized similarly enough for that to make sense.

    UI and workflow

    One possible way to present DoT editing is the following:

    • User creates list of relevant texts
    • User is presented with a double-pane window, selected text on one side, output on the other
    • User selects a quote in the text
    • User clicks "Add" button
    • The quote appears in the output pane, marked with the origin (Text name, possibly specific colour)
    • User can add own comments to the quote. They appear on the margins.

    Workflow for the DoT studying:

    • User is presented with the page of "Quotes".
    • User can click on any quote to see whole original text, in order to see the quote in context. The text is automatically scrolled to the quoted place.
    • User can expend any quote in-line, in any direction. Such expensions are marked visually (e.g. by different colour)
    • The DoT authors' comments appear on the side, as pop-ups while user scrolls the text, or on the margins, if there is enough room.

    Text In

    • Features
      • Presenter
      • Author
      • Number, starting with 1, incrementing by 1
      • Links to all related texts in the Dialogue

    "Link to" is an UMO (see below)

    Link To

    It is an object featuring:

    • Two linked texts
    • Their relationship, such as:
      • Contradicts
      • Develops
      • Complements
      • Repeats
      • Mocks
      • Custom


    Just a piece of text loosely associated with a UMO

    • Necessary Features
      • Subject
      • Text body

    Custom UMO

    A user can create a custom UMO, which cannot be structured, but can have all general UMO features. Custom UMO can be included as a child in any other UMO

    • Necessary Features
      • Name (Category)
      • Description
      • Child UMOs

    Custom UMO can be created if at least two child UMOs are supplied.

    Generic System Functions


    Universe University has to be accessible and functional on different languages. There are two important aspects of localization to consider

    • Localization of user interface
    • Localization of content

    Locality to use when rendering objects and UI to users will be negotiatable using standard HTTP content-negotiation protocol, but will be forcable through personal user settings.

    User Interface Localization

    We will (probably) use gettext system for translations. .po files will be (as everything else in our Open Source application) pubic, and translations will be contributed by interested users.

    Content Translations

    There will be special role: "translator". This person will be listed as such for given object (along side with authors). Translator will have full editorial access to translations of object for his language, but will have no administrative rights. There will be standard set of tools for creating and editing tranlations of object.


    • Translation of an object is translation of text of all core object data into a given language. Specifically, that does not include any dependant objects.
    • Main object language is language in which original object is written, and in which new versions can be created.

    Translation vs. Versioning

    Object tranlation does not constitute a separate version. When translations are added/removed/editied, they are implied to be a minor edit. Translations will have their separate "publish" flag though, to avoid making an unfinished translations visible, when working on an object which main language was already published.

    Editing Translations

    When editing a translation, a separate, temporary copy is created, and that copy is the one that work is being done on. It can be saved across editing sessions. Once it's ready, translator will "publish" it, at which time this copy will replace any existing translation for given version of given object in given language.


    A Host of an instance of the Universe University has tools to develop and enforce certain policies regarding contents and other features of courses and other objects created and offered to the general public at the Hosts' servers.

    UMO Access System

    ACL Group

    Access to objects in UU is granted to "ACL Groups". ACL Groups is just a group of users. Membership in ACL groups is controlled differently, depending on what the group is used for.


    Class is a special object, which is used to give users ability to study courses. Class itself doesn't support versions. It has three groups associated with it:

    • Administrators
    • Teachers
    • Students

    When class is signed up for a course, class'es "Students" group gets Study access to the whole course UMO structure (that is all subtopics, explanations, problems, etc.). In order to pass the class, a student must pass all the UMOs that class is connected to.

    Access Types

    Different groups may be granted different permissions on different UMOs.


    Members of a group with EDIT access to an UMO can perform following actions:

    • Create new versions of the UMO
    • Modify unpublished versions
    • Link other UMOs as children
    • Publish UMO


    Members of a group with TRANSLATE access to an UMO can create new translations for that UMO, as long as version in unpublished state exists.


    Members of a group with VIEW access to a UMO can get a preview of the UMO. What is displayed depends on type of the UMO.

    • #Course and #Topic will show up with tile and annotation (and possibly list of child objects)
    • #Problem will show title and (possibly) problem statement
    • #Explanation will show ... well... Explanation...


    Members of a group with TEACH access to a classe can "teach" it. This means following actions are allowed:

    • Has access to check class' students' solutions of "human-controlled" problems
    • Marked as a teacher on all course-related communication tools.
    • Marking someone as teacher, automatically grants them moderator power

    in all course-related communication tools for this class.

    Administer Class

    Members of a group with ADMIN access to a class can perform following actions:

    • Add more class admins
    • Add users to the class' teachers group
    • Control how students are signed up for the class
    • Manually sign up students to the class


    Members of a group with STUDY access to a #Class can have following properties:

    • can "Study" any UMO which belongs to courses which the class is signed up for
    • are marked as students in all class-related communication tools


    Authorship and appropriate credit concepts are extremely important. UU handles it in the following way: Each UMO has authorship info associated with it. By default author list is comprised of all people who made any modifications to an UMO. However, in some cases it is not the right thing. For example, someone may decide to publish someone elses text book as a course on UU. In such case the published is [b]not[/b] the author. To accomodate this, UU allows UMO administrator to specify author list manually (once it's done, author list has to be kept up to date by hand).

    There is still access to lists of app people who did modifications to UMO, as well as separate lists for translators.

    In addition, there will be "history" page, which shows UMO modification history, along with contributors to each modification.


    a) An author can set up payment for a students on per course basis with a drop-off grace period. b) In this case the author has choice of payment to UU either

    • Flat rate per course, or
    • Flate rate per student, or
    • Commissions

    c) No other transactions (except for sponsorship) are possible respecting Open Server

    d) Flate rate service charge is added to any author on Proprietary Server

    Variants for subscription management

    • Regular Revisions (say every 6 mo)
    • Price, picked by subscriber

    Structured Shared Repository

    • Is a very special feature of the UU. It is the repository of all created objects ever.

    UMO gets automatically from a course into the Repository or can be created specifically for the repository depending on its author.

    • A UMO can get in one out of three storages:
      • Featured Storage
      • General Storage
      • Disagreement Storage


    All of above repositories will be presented to user as catalogues. Catalogues themselves are browse-able tree-like sets of categories [1] based around subject matter and also based on UMO authors. While browsing, user is allowed to filter out visible objects based on following criteria:

    • Available translations
    • UMO types
    • Ratings (TBD)
    • Creation time
    • Last update time

    User will also be able to specify any combination of the following sort criteria (both increasing and decreasing):

    • Alphabetical topic
    • UMO types
    • Rating
    • Creation time
    • Last update time

    Catalogue Administration

    Administration of catalogue categories is performed by users from a special "catalogue administrators" groups. Each category in catalogue has such an administrative group associated with it. Members of group controlling higher-level category are automatically allowed to any category in the sub-tree.


    Math (user1)
     +-Algebra (user2)
     +-Geometry (user3)
    • user1 will be able to administer any of listed categories.
    • user2 will have only access to Algebra
    • user3 - only to Geometry

    Following administrative tasks will be allowed:

    • Hide category from catalogue
    This will hide the category from catalogue and from UMO author UIs for association of UMO with categories. Any sub-categories of the hidden category are also hidden, recursively.
    • Unhide hidden category.
    Any sub-categories are also unhidden, recursively.
    • Remove UMO from category
    This one is for moderating categories (e.g. if UMO is being spammed to too manu
    categories in catalog, which it doesn't belong to)
    • Search UMOs by category or combinations of categories.
    Category search by the parent category also includes any sub-categories for this category.
    For instance, in the example above, search results for search by the category Math would also include UMOs from Algebra and Geometry categories.

    There will also be an external tool (probably command-line) for permanent removal of categories from the database. It's intended for use by UU instance administrators, in cases where a category was created erroneously.

    1. This has nothing to do with parent-child relationships of UMOs

    Featured Storage

    This is repository of shared objects with high ratings. Formulae for object ratings are TBD. Following categories are available. Each category may have its own separate rating formula.

    1. Classical problems
    2. Border line subject-to-subject problems
    3. Classical texts
    4. Border line science-to-life problems
    5. Games
    6. Teaching techniques
    7. Work Flow
    8. Explanation
    9. Exercise

    General Storage

    Items from the General Storage move up into the Featured storage by getting rated.

    Disagreement Storage

    Stores submissions disapproved by the Masters Board

    Masters Board

    It is a wikipedia-type board comprised from authors and experts to determine where a UMO belongs. Reviews automated submissions and special submissions.

    Problem Generator

    Problem Control Tools

    • Single Answer
    • Multiple Choice
    • Template
    • Semantic Model
    • Custome/Language Driven Control

    Editing Tools


    • Templates exist for any UMO development and described in the Page Flow section
    • Developing directions (links)
    • More complex/hard to guess problems (links)
    • Easier problems (links)
    • Off topic gigs (links)
    • Images, diagrams, charts, other graphics
    • Videos
    • Sound

    Possibility to link any unit to any course

    (For Open server only)

    Each entity in course can be included into any other course or linked to some other places, subject to attribution to authors and sources.

    Tools to make turning multiple courses into one easier

    (For Open server only)

    May include tools for analyzing tree structures, and pointing out similarities to authors, etc.

    Locking-unlocking for editing

    Simple features to make sure no conflicts are created during simultaneous work on courses.

    Object versioning

    Every object will have versioning history. Version is created every time an author indicates that this text is ready for inclusion. Until that time any changes are saved, but are not visible to anyone but authors.

    Other users of the object get notified the object has changed. They can choose to upgrade the object or leave it as is.

    If a user of a object edits the object or builds a new one upon the used one it is up to this user to consider himself an author or an editor. In any case everyone using the original object gets notified and the new or edited object bears its history: which object it is built upon.

    References to external sources

    Rating System


    1. Voting: on courses, problems, authors, messages, etc.

    2. Functional: on people, participating in through subject chess mastership type rating

    General user rate formula

    It is a function of:

    1. Fact of growing

    2. Level of difficulty of problems

    3. Frequency of participation

    4. A single problem solving time

    5. Rating of courses taken

    6. Other factors

    Specific user rate formula

    It is a function of:

    1. Should be around 50 for every topic in the course.

    2. Points for the problem - N (m, k, l, p), where m - the level of the course ( 0 < m < 3); k - the number of the theme within the course; l - the level of the problem ( 0 < l < 4 ); p - the number of the problem within the course ( 0 < p < 50).

    3. Correspondence: 0 < N ( m, k, 1, p) < 40; 40 < N (m, k, 2, p) < 65; 65 < N ( m, k, 3, p) < 90; 90 < N ( m, k, 4, p ) < 100.

    4. Rating RG is a function of average amount of:

    5. Points of the last five problems chosen,

    6. Overall points,

    7. Deductible points,

    8. Levels of courses and problems taken,

    9. Communication,

    10. Activity.exercise

    Communication Tools

    We intend to use all available Open Source communication tools

    List of tools

    • Blogs
    • Forums
    • Wikis
    • Chat Rooms
    • Mailing Lists
    • Message Boards
    • Other

    Object Rating

    E-Bay style rating of any UMO

    PHP-doc style comments

    Each entity in course can have set of publically viewable notes attached to it, that anyone can add to.

    ?The notes are moderated by?

    Default Tools

    1. UU level mailing list, forum and wiki.
    2. Each course generates mailing list, forum and wiki for students
    3. A course, when started or got completed, sends message on UU mailing list and UU forum


    • Each UMO bears publically accessible statistics of:

    1. Visiting

    2. Attendance

    3. Revenues

    4. Rating

    5. Participations/Results in/of within/out UU contests

    6. Usage in other courses

    7. Usage out of UU

    Group Admin. Tools

    • This section supposed to be developed (but is not yet) in order for UU to be used by groups and organizations of any type.
    • We need some form, posiibly wiki, to get requests from organizations about this section

    Search Engine & Lists

    1. All items in the lists below go with related "demographics"

    2. All lists are cross referred

    3. Lists

    • All objects
    • All courses, including languages
    • All topics
    • All problems
    • All languages
    • All course subjects
    • All authors, teachers, experts, students, etc.
    • All schools w. their level of participation
    • All groups w. their level of participation
    • All of the above associated with a user

    Business Assumptions

    Open Server

    1. The general condition to use the Open Server is that courses and any other objects created here fall under Authoright license.
    2. Specifically this means all courses created at the Open Server can be copied and offered to the audience on any conditions with the only requirement for proper attribution to the authors and original source.
    3. Any other objects from a course or General Repository can be used to create another course.
    4. Authoright driven references get technically implemented and enforced by the application.
    5. Using Open Server for creation of a course is free.
    6. However, offering a course for payment results in certain payment to the host.
    7. A course or any other object created at the Open Server cannot be tacken away except for those cases when its contents or any other feature contradicts the law or the Host policy. The decision to remove an object from the Open server is at the Host's discretion entirely.

    Proprietary Server

    • An author can create here a "closed source" course, which means that neither course, nor any of its object can be used by another author.
    • The Proprietary Server is a paid service.
    • If an author copies a course from the Open Server on the Proprietary one this does not affect in any way the prototype or its usage on the Open Server. All proper attributes are required like in all other cases.
    • The same applies to any object created at the Open Server and copied to the Proprietary Server: free usage of the prototype on the Open Server goes on unaffected.
    • Any object created at the Prprietay Server can be removed by its author at his own discretion.