Posted by akmalfikri on February 18, 2011 at 7:28am
I want to create a programmes and courses catalogue. To achieve this I am thinking these steps :
- Create a content type which contains the programme's details and named it Programme, eg. Bachelor of Engineering.
- Create another content type which refer the programme as a parent and named it Course, eg. Electronics Lab.
- Add another reference where the course have dependencies with another course, eg. Electronics Methodologies (a dependency of Electronics Lab)
Is there any module for this or any other way?

Comments
Try Organic Groups
Try Organic Groups. Each group can be a department. Then figure out how to do sub-groups. I was thinking of just making departments have links to each class which is essentially it's own group, but each class group only has links from the parent department group.
some initial thoughts
The book module (part of core) and node hierarchy (http://drupal.org/project/nodehierarchy) module create parent-child and sibling relationships between nodes. As for dependencies, maybe the node reference field will do the job.
of course your solution is going to be influenced by the version of Drupal you want to use and your willingness to wait for a module to be ready. node hierarchy isn't D7 ready yet. Node reference didn't get pulled into D7 with CCK so you will need http://drupal.org/project/references
i hope this gives you some options
take a look at the drupal commons distribution
take a look at the drupal commons distribution. I think you'll find it's a great starting point.
Although Commons uses organic
Although Commons uses organic groups and is nicely configured, its interface and features are geared towards community interactions and collaborative work.
If this requirement is for a university setting (or the like), sequencing is going to play a part in organizing the parents and the children. OG nodes are not hierarchical by nature. Also, unless there is a need for access management, the added layer of access management might be a distraction.
Don't get me wrong. Commons is great and OG is one of my favorite modules. I am just not sure about in this scenario.
Node Reference
I think that you can try Node Reference.
I recommend you this tutorial http://mustardseedmedia.com/podcast/episode37 .
;)
A. Campillo
Yeah sounds to me like you
Yeah sounds to me like you want a quasi relational database created via Views / CCK Node Reference. I'd build in D6 as Views and CCK / node reference are all stable and D7 you'll still have to wait a bit. You'll be able to upgrade in a few months if you really want to but that'll get you off the ground quickly.
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
Finally I got this working. I
Finally I got this working. I use CCK and Views for this thing to work and fortunately the site is using Drupal6. The steps are :
So the user must create core courses first before creating other smaller courses and programmes.
Some questions though :
Views is your friend
Views is your friend again.
CCK & Views
We did something similar (not exactly the same) at U of Maryland for the Dept of English.
http://english.umd.edu/academics/courses
We created a content type for a course schedule and connected them to a faculty profile and externally to the University's course scheduling system (Testudo).
Carl Bice
operations director
........................................
LMD
Brand Architects | Innovative Creative
grow
........................................
301.498.6656 ext 234
516.318.9245 (cell)
301.953.0321 fax
[[
How did you import the data
How did you import the data into the UMD English course listing? Was this manually entered or did you somehow import it directly from your course scheduling system?
We worked on a similar
We worked on a similar project for McGill University's online course calendar. Here's an example of a program page, with expanding blocks that show the courses offered in that program: http://www.mcgill.ca/study/2010-2011/faculties/music/undergraduate/progr....
The node relationships were a bit tricky since there are usually sets of courses that students have to choose between. We used a content type for course, program, and 'course set'. Each program includes node references to a list of course sets and each course set includes node references to a list of courses.
In McGill's case, the content was imported front their internal Banner system.