For my school I made this http://web2py.com/d2l/static/mCMS-mWIKI.pdf
It is not a full LMS and I am not releasing it quite yet because (as it is) it requires Desire2Learn. Yet I learned something from the process... D2L seems to use the following model: There is a main program that only manages groups, memberships and roles. A class is a group. An instructor and a student are members of the class with different roles. For each group it also maintains a page layout which is a collection of boxes. Each box could be an iframe of an ajax callback. When a member of the group enters in the page, the page contains a JS object with the ID+name of the user, the group, and the role. Each box can grab this info form the page DOM, verify the info using a central authentication system and a web service (is this user logged in? is this user really a member of this group and this role?) and then any IO form the browser and the box becomes independent on everything else. This means every box can be implemented as its own application. I will refer to this feature as "boxable" This model allow to build components (CMS, WIKI, Grading, Quizzes, etc.) as separate applications that work with or without the LMS. They can also work with multiple LMSs. So... we have some components already: - PyForum - InstantPress - Survey - CMS (I have) - WIKI (I have) - Integration with Big Blue Button (I have ~) We need - Gradebook - Assessment (with SCORM) I we can make all our apps "boxable" (perhaps using a the same naming convention of "D2L" which I know and I can explain) than we have components that are apps, can be used independently. Can be used with our own LMS, can be used with other LMSs (for example D2L). Massimo On Oct 21, 9:19 am, blye <blyen...@gmail.com> wrote: > btw gratitude Massimo for your great creation > > In the developing world, on the brink of a huge uptick in broadband > users, such an app would be very very useful > > I second what Tom in Ireland says > I see an LMS as a balance of user data / > admin(collaboration,enrolment) data / course and resources data. > I have been working (slowly :-/ ) with a web2py LMS version, > Phase 1 - actually a constellation of CRM, blog, forum, collaborative > learning chat, supercharged links list, gallery, resources upload/ > download, groups for collaboration. > Phase 2 - teacher/course/resources - still in formation, needs to be > very multimedia (video,podcast etc ) and collaborative. > Phase 3 the Admin/collaboration Phase - many to many interaction of > student with 'course' resources and each other. > Phase 4 - 'Course' administration, presentations and assessment > options. > > I have been thinking about SCORM, a 'protocol' for the creation and > transfer of computer administered assessments. It seems to be a > distant cousin of XML. What do the web2py maestros think of it. An on- > line testing, agile and flexible) would be an awesome addition to some > of the good ideas above.
