Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.9, 2.2
-
Fix Version/s: DEV backlog
-
Component/s: Course
-
Labels:
-
Affected Branches:MOODLE_19_STABLE, MOODLE_22_STABLE
Description
There should be a way to organize course resources/activities into course sub-pages. A course sub-page would include the basic course interface with the sidebars and topic outline boxes, but the topic contents would be unique to that sub-page. The sub-pages would seamlessly inherit all of the course's roles/enrollments and groups by using the same course ID as the main course page.
I tried using meta courses to pull this off, but it just wasn't a complete solution, since groups weren't inherited and grades were inconveniently separated. The sub-pages would simply be extra pages of topics within the same course, with no need for duplication in the database. It would allow more organizational freedom for courses with a lot of content.
A bit of background: I'm developing the Moodle site that will run the official prep course for the California High School Exit Exam (CAHSEE). This site targets students who are having difficulty passing the exam. Many of these students also have difficulty using computers and get overwhelmed by the giant page of course materials. The course creators strongly wish for the ability to create separate pages of course materials for each section of the course, since each section also contains several topics, each with its own resources and activities. This is all too much to reasonably fit into a single course page, yet the meta course system isn't adequate to address our needs. A course sub-page system would be a much more elegant solution, and I believe others would equally find it useful for very large courses.
At Godalming College we are very interested in the idea of course sub-pages, some of our courses are now very long and real organisational problems have arisen when one course is shared by up to 11 teachers.
We have looked into several ways of getting around this problem. One fix was to use resource pages (as presented by the OU at MoodleMoot 07) however the version available is not compatible with our database setup. We have also looked into using a tab system however none of the versions found seem to robust enough.