Development:Certificate Module

Note: This article is a work in progress. Please use the page comments or an appropriate moodle.org forum for any recommendations/suggestions for improvement.

This page will show the new features and the plan to implement them in the Certificate module for each Moodle release.

Changes planned for Moodle 1.8 contrib branch

The basis

Point to decide: Before start. Where will be develop the 1.8 version:

• a) These will be developed under HEAD and backported to 18_STABLE once finished.
• b) These will be developed directly under 18_STABLE, meging to HEAD while advancing.

Every one of the features described below will have its own bug created in the Tracker. With links from here for easy location.

The ordered list of features

(each one will be marked with Not done!, In progress!, Done!, with the name of the developer assigned between brackets.

1. Update the module install.xml and create the upgrade.php file (confirm save->savecert is the first change to be added for 1.8!). This will provide cross db installation and upgrade of the module.
2. Split conditions to allow certificate to a new fieldset.
   • Conditions will be:
     • a) % of total grade raised.
     • b) 1...n quizzes grades raised.
     • c) 1...n surveys filled by the student
   • With:
     • All the specified quizzes must be passed (logical AND between them). (b)
     • All the specified surveys must be filled (logical AND between them). (c)
   • Finally:
     • Then (a OR b) AND c will be checked to allow display/download.
3. Define n texts, with position and size to be inserted in the certificate ordering them by y,x descending. Fieldset can be hidden/showed like the user profile form.
4. Upload (to moddata/certificate) and define n images, with position and size to be inserted in the certificate ordering them by y,x descending. Fieldset can be hidden/showed like the user profile form.
5. Find a better solution for the preview certificate feature. Analyse the XHTML strict object alternative.
6. Allow to configure if the student/mainteacher/admin should receive one email with the text: Mickey Mouse accessed the certifacte on XX/XX/YYYY".
7. Coma separated list of email addresses to be informed about certificate accesses.
8. Roles, accessibility ...
9. Rework backup/restore to handle everything above.