Not sure which to use.. nodereference vs taxonomy, and permissions
I'm a bit confused which to use, and whether I should consider both.
The site I'm building has many departments. E.g:
Department A
- intro
- news
- staff
- about
Department B
- intro
- news
- staff
- about
- gallery
-----------
but they could share a common thread in that each department has the same submenu structure but there might be some departments who will have a specialty item in their submenu e.g: a gallery for example (Dept B ).
Added to that is the matter that each department will have a editor, of which he or she should only be able to edit or see the content relative to his or her department once logged in. ( Dan assigned to Dept A, can only edit and see Dept A content and news ) For this I thought I would create each user per department, create content and assign each user to his or her department. I would install the workspace module to group all the content each user has created for easy access.
What route would make sense to take ?
I think I'll be going with
I think I'll be going with nodereference and create a content type for each of the possible subdepartments, e.g:
Create intro page
Create news page
Create staff page
Create about page
Create gallery page
and reference them to each department.
Whats you thinks ?
_
I set up departments as groups with http://drupal.org/project/og. I then use content types and taxonomy to categorize the content for each group.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
@worldfallz, thanks, I have
@worldfallz,
thanks, I have heard of groups.. but never used them yet. Forgive me, but they seem a bit complex for my need.
I am still a bit fresh at anything complex and I am hoping for a method which is straight and relatively forward. I will investigate Groups, I am checking out the videos now.
Thanks Worldfallz
First of all, thanks for the
First of all, thanks for the advise, but after trying groups, I think I can safely go with a simpler solution.
I have to create a departmental site. I have about 13 departments who have similar content, but they can have extra content too. e.g:
Department A
- intro
- news
- staff
- about
Department B
- intro
- news
- staff
- about
- gallery
-----------
I am wondering how to approach this.
The content types I will have to create if I stick to the idea I have are:
-Department
- Intro
- News
- Staff
- About
- Gallery
Then I need to create for each department a department page, e.g: Fishing, Hunting, Food, etc.
Then I create a "About, Introduction, News, Staff, Gallery" content type too.
Then it becomes relatively simple.. When creating a "intro page" for your department you need only select your department content type ( i:e Fishing, Hunting as you created in a earlier step ), likewise when creating a "About" page for the department you are controlling. You create the custom 'About page', select the department and enter content.
Please advise, not 100% whether I am even approaching this in the correct way. Any help would GREATLY be appreciated..
_
That's pretty much what I did on my first try at the site and what spurred me on to find an alternative. So I'm not sure how you can say that's simpler than og, lol, but whatever works for you ;-)
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
@WorldFallz I think I need to
@WorldFallz
I think I need to ask the right questions here.. :) Why did you choose Groups over working with nodereference ?
_
I tried both and og just seemed simpler to me. Rather than having to configure my setup using roles, taxonomies, access control, etc. with all sorts of modules that may or may not play together nicely, I installed og and og_user_roles and got exactly the functionality I needed. Moreover, there's tons of og add-on modules so i've yet to stumble across something I've needed that hasn't been available. Also, og is a very well supported module and many other modules automatically integrate with it.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Departmental pages
I have to agree with WorldFallz i'm wanting to do exactly what you are Diegen and have looked at books and forums. OG seems the simplest and cleanest solution plus your users don't have to learn or do much in terms of posting. They just have to subscribe to the group/department they want to post in and or post to a public area. The presentation Here explains everything very well.
Again you will need to do lots of initial configuration if you have copy of your organization Org. chart up to date at hand it should not be that hard to setup.
Unless your me and have to do this when you already have all kinds of other modules installed and configured for another type of content entry. If you do this from clean install you should be up and running fairly quick.
You may try
You may try cck+view_own+nodeaccess_autoreference