Note: You are currently viewing documentation for Moodle 2.9. Up-to-date documentation for the latest stable version of Moodle may be available here: Community hub.

Development:Community hub: Difference between revisions

From MoodleDocs
m (Reverted edits by Dougiamas (talk); changed back to last version by Helen Foster)
Line 3: Line 3:
[[Image:Community.png]]
[[Image:Community.png]]


Some notes on required parts ...
==Moodle Network notes==


==A. Registration system for hubs==
::After talking with MartinD about this in MoodleMootNZ'06, I am working on a "Moodle Network" model that supports the "Moodle Hub" as well as a more P2P layout. In fact, the choices of hub vs network model can be mixed and matched. Each node can configure a list of other nodes it knows about (and trusts!), and set what it offers to each of them. --[[User:Martin Langhoff|Martin Langhoff]] 13:11, 20 July 2006 (WST)
 
We can extend the current site registration to let Admins publish more information into a central directory:
 
===A1. New registration form===
 
The existing registration form can be extended so that admins can choose to send in more info about their sites, including:
# Lists of courses, each one with:
## Name
## Description
## Availability (public/private)
## Cost (and currency)
## Audience:  educators / students / admins  (use legacy name of role?)
## What else?
# Mnet registration details, enough to let someone else log in to this site
# Overall information about the whole site, such as a custom description etc
 
If any of these are set, then that Moodle will automatically inform moodle.org later when this information is updated, and possibly send a heartbeat ping every week or so (so that we can delete Moodle sites that miss two weeks).
 
 
===A2. Moodle.org directory===
 
A new directory system on courses.moodle.org will allow you to browse/search the available courses/hubs around the world, via two methods:
# A web interface, with clickable links to the sites so that users can log in manually.
# A web services interface, designed to be used by other systems directly
 
Both interfaces will provide the same data.
 
==B. Community link from every Moodle==
 
Every course will have a "Community" button that links to a script in Moodle that lists available community hubs (list downloaded from Moodle.org) with searching by site name, course name, subject name, teacher name (perhaps), tags etc.
 
Requires:
# Adding button to course, with capability to view it (default on)
# Adding new Moodle script to browse/search hubs (using web services to call Moodle.org), and join sites or link to courses as necessary
# Moodlerooms hub to be the first one in the browse view, and have preferential treatment in searches (bold text etc?)
# Public Mnet sites allow immediate single-sign-on
 
==C. Hub as repository==
 
Courses and other places in Moodle have a "Search for template..." button, which pulls up the normal file picker to look for template files.  The community hubs that have been configured appear as just another repository, and show a kind of iTunes-like interface to browse/search for content and select one for download.
 
# Special new file types for Moodle files eg .mcoursebackup .mforumbackup which are all really .zips
# Special repository plugin in the client Moodle that displays a nice interface in an iframe, based on data retrieved via mnet services from the hub.
# Special module (activity module) in the server Moodle that manages uploaded files with ratings, comments, tagging, workflow etc.
# Course page to unpack returned file and "restore" it to the current course.
 
!! D. Hub as portfolio
 
Courses and other places have a "Save.." button which calls standard portfolio interface.  Any configured mnet hosts will appear as a plugin there as well, so it will be possible to push the course as a zip to the external system (the special activity module in a course of your choosing)


Here are my technical notes on how the internals would work...


* [[Community hub technotes]] - getting it done


== See also ==
== See also ==


* [[Community hub technotes]] - relating to MNet developments in Moodle 1.8
* [[Community hub BEST]] - pictures and notes about the BEST Bulgarian project


[[Category:MNET]]
[[Category:MNET]]


[[ja:コミュニティーハブ]]
[[ja:コミュニティーハブ]]

Revision as of 06:59, 16 November 2008

The Moodle Community hub is a future project which will allow more interaction between teachers building courses and teachers using them, courses and user data can then be stored in a repository as shown below:

Community.png

Moodle Network notes

After talking with MartinD about this in MoodleMootNZ'06, I am working on a "Moodle Network" model that supports the "Moodle Hub" as well as a more P2P layout. In fact, the choices of hub vs network model can be mixed and matched. Each node can configure a list of other nodes it knows about (and trusts!), and set what it offers to each of them. --Martin Langhoff 13:11, 20 July 2006 (WST)

Here are my technical notes on how the internals would work...

See also