hierarchy

Hello from Grand Rapids!

I've been here for two weeks and already the Drupal involvement begins! I'm not actually working on the development, but our web developer is fairly new to Drupal with very few people to consult in GR; only the support forums. So we have a question based on permissions, and the context is that we're creating a website called The Rapidian that will act as an online distribution platform for citizen journalism in Grand Rapids. In this setup, we have many roles, with first-time reporter and reporter on the lower rungs and editor on the higher rungs.

So when adding content in a custom content type like a “news story,” can we hide/show certain fields based on a users role? For example, we’d like an editor role to be able to check a field “has been fact checked” but not show this to the reporter role.

I've been trying to wrap my head around this for a while and I'm running into a roadblock in terms of providing good usability to community members vs. correct information architecture. As an example, let's say I'm running a website about plants, and visitors can add articles about different plants. This is just a crude example to help understand the problem. When a visitor goes to create a new article, they can categorize it as follows:

Plant Part
- Color
-- Produce

Hi all,

Is there a way to make vocabularies hierarchically dependent, so that their terms would inherit this hierarchy?

Example:

Now for tagging an event we first select Country, then City, then Theater.
I found no solution for this on D5, now I'm on D6.
Any ideas (patches are welcome too)?

And, of course, having this working together with http://drupal.org/project/hierarchical_select would be great.

p.s. Thing which is not an option - placing terms in one vocab.

What solutions have people had most success with in creating hierarchical sites with Drupal? In my experience, users don't find the 'Menu settings' section on the node edit form at all intuitive.

Among different approaches I've seen are:

• Book module
• Taxonomy menu
• Node hierarchy

Cheers,

Alex.

Hi All,
Thanks for a great module. I'm trying to make pathauto construct hierarchical urls using cck-nodereference fields for the hierarchical relationships. And I have some questions about the tokens that are created for nodereference fields. As far as I can see the only usable token is [fieldname]-nid. Is this correct, or are the *-title and *-link tokens populated in certain circumstances?