Table des matières
Commands Related to Courses and Categories
VMoodle: Moodle Virtualisation
Five commands are currently offered for the mass handling of the educational offer in a network of virtualised Moodles:
- Creation of a course category
- Change of the visibility of a course category (by identification number)
- Deployment of a course archive
- Change of visibility of a course (by short name or identification number)
- Destruction of a course (by short name or identification number)
Category creation
Category creation is the first of the group
Step 1
It asks you to enter:
- A category definition as a path of visible names separated by /: e.g. “Miscellaneous/Sandboxes”
- an IDNumber that will be given to this category
- an initial visibility through a checkbox.
Step 2: Selecting the institutions the command is sent to
- by selection list (a few bugs to fix on the name filter)
Step 3: Launching the command
Optional step 4: Replaying the command on a new batch of institutions
Changing the visibility of a course
(to be completed)
Deploying a course
Course deployment assumes the archive is available in a known path. It is not easy to know where a backup file is physically located in the Moodle file storage. The feature is currently intended for exceptional deployments that require putting the files on the server in a directory that is easy to access and readable by all the platforms.
Course deployment is the third command of the course group
Step 1: It asks you to enter
- The full name of the new course
- The short name of the new course (must not be already used)
- The identification number (for later reference, must not be already used)
- The full physical path of the archive on the server (up to .mbz)
- The initial visibility state through a checkbox.
Step 2: Selecting the target Moodles
Pay attention to the quantity selected and to the size of the course to deploy!
If the course is large, deploying to too many institutions can have a serious impact on the overall performance of the platform, or even make the server give way and fail. For a small course, batches of 15 to 20 institutions can go through; for a large course, you will have to be more careful. Resistance to the processing load depends on the overall power. As deployments are launched by MNET calls, the deployment load is spread over the installation in the case of a clustered installation.
Step 3: Launch the command
Optional step 4: Replaying the command on a new batch of institutions
Changing the visibility of a course
(to be completed)
Destroying a course
(to be completed)