Issue Details (XML | Word | Printable)

Key: CONTRIB-1604
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Anthony Borrow
Reporter: Ravishankar Somasundaram
Votes: 0
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Non-core contributed modules

Curriculum, through which course grouping, hierarchy and flow control can be maintained between modules within a course and between courses themselves

Created: 05/Nov/09 12:47 PM   Updated: 18/Nov/09 11:50 PM
Return to search
Component/s: Add a project here
Affects Version/s: 1.9.3, 1.9.4, 1.9.5
Fix Version/s: None

File Attachments: 1. Zip Archive curriculum.zip (276 kB)


Database: MySQL
Participants: Anthony Borrow and Ravishankar Somasundaram
Security Level: None
Affected Branches: MOODLE_19_STABLE


 Description  « Hide
Long awaited feature "Curriculum" for moodle 1.9.3,1.9.4,1.9.5.

Features:

Course hierarchy

1. There can be a tree hierarchy
2. There can be a parallel hierarchy
3. There can be a serial hierarchy

between courses inside the curriculum, the admin/teacher has the power to tailor the courses in any of above mentioned hierarchies.

Module hierarchy

1. There can be a tree hierarchy
2. There can be a parallel hierarchy
3. There can be a serial hierarchy

between Activity/resource inside a course or a curriculum,the admin/teacher has the power to tailor the activity/resource flow in any of above mentioned hierarchies.

Course completion:

Completion of a course for any student occurs on two ways,

1. Automatic
2. Manual

1. Automatic :

   Any student is marked as he completed the course if he completes the dependencies within the course,Once he completes this course automatically the other courses which are dependent on this course opens up

Note: if the teacher did not place any locks/dependencies within the course any student who just visits the course will be marked as completed immediately

2. Manual :

   A student take a course and even though he finished all locks/dependencies he will not be marked as he completed the course until the teacher manually does it using the participants page(which appears in the participants block).

And any student enrolled in a curriculum is enrolled in all the courses within the curriculum but denied access to courses as per the hierarchy structure designed by admin/teacher.

Teacher/admin has the facility to suspend the user for any single course or multiple courses in case he violates some rules for that course/curriculum itself.

Roles:

1. Curriculum wide (similar to site wide roles)
2. Course wide (similar to course wide)


 All   Comments   Change History   Version Control      Sort Order: Ascending order - Click to sort in descending order
Anthony Borrow added a comment - 18/Nov/09 11:50 PM
Thanks for your patience and also sharing this code with the Moodle community. OK, I see that this is a patch. Generally speaking, it is preferred that patches be maintained as a single patch file; however, we have also provided the file structure and patched files for a particular version of Moodle to make it easier to use for folks who do not know how to work with patch files; however, the question always remains for me whether those users should really be using patched versions of Moodle. In any case, would you be able to create a patch (i.e. diff) file (you can check out http://docs.moodle.org/en/Development:How_to_create_a_patch if you need guidance with that process). The issue is how the patch can best work with various specific versions of Moodle. For that reason patch files tend to be more effective and less likely to produce versioning problems. If you need help creating the patch file just let me know. In the meantime, I will try to look through some of the changes and functionality and give you some other feedback. Peace - Anthony