Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MNet: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 3: Line 3:
* Documentation for end users is here [Moodle Network]
* Documentation for end users is here [Moodle Network]
* Some old documentation about the initial planning and dev
* Some old documentation about the initial planning and dev
** [Community_hub]
** [[Community_hub]]
** [Community_hub_technotes]
** [[Community_hub_technotes]]
** [Community_hub_progress]
** [[Community_hub_progress]]





Revision as of 22:22, 22 January 2007

Random notes for Moodle Network. Should get these organised...


To Do

Some immediate items that would add polish without major surgery

  • Exchange more enrolment info at log-entry exchange time on cron
  • Special default role
    • Add a new "remote student" role
    • Add a config var to enrol/mnet: "defaultremoterole" to use "remote student"
    • Add a config var to the courses table to optionally override defaultremoterole
  • Nicer CSS in the "my courses" listing in moodle homepage for remote hosts and remote courses. See course/lib.php print_remote_course() and print_remote_host().

Roadmap

A bit more work, and a whole lot more features. From easy to hard...

  • Better per-host stats and log views for administrators. This is relatively easy using data we already have.
  • In mod/forum craft a special URL for remote users so that the post URL is in the wantsurl parameter, so they can bounce-off their IDP in one go.
    • According to Jonathan Harker, this requires that we modify jump to accept the remote wwwroot as a parameter. Also: will this be safe enough?
  • Display aggregated calendar on the IDP
  • Exchange grades. Needs a bit of design.
  • Build a SCORM/IMSCP/MoodleZip repository scheme.
    • MartinL has some ideas on how to get this done in easy and super-scalable.