I am not sure if this module will help me accomplish what I want to...my site is centered around events and then images and blog posts are posted during an event which I want to 'round up' in a block while someone is viewing any node with the similar taxonomy term.

How I envision it is for the event node creator to be able to create the master taxonomy term somehow in the event node creation page (/node/add/event). Then that taxonomy term is automatically allowed to be used by users creating blog entries or images or forum topics (or any node) and they will be presented with this "Event Listing" taxonomy list that they are required to choose ONE from the list.

Of course I'd like this process to be automated, initiated from the event node creation page.

Did I explain myself properly?

Comments

molenick’s picture

molenick commented

I'm using this module to enable a similar process. Basically, I have a CCK type which stores all my core information, as well as a series of auxiliary CCK types to store additional related information.

I use NAT to create a taxonomy term with the same name a new node of my core CCK type. This then allows me to associate the auxiliary data to the core data through taxonomy.

For example, say I have a core CCK type called "dinner" which I intend to use to plan meals with.

1) Create CCK type "dinner_cck".
2) Create Taxonomy "dinner_vocab", assocating it with type "dinner_cck".
3) In NAT, setup "dinner_cck" to create a term in "dinner_vocab" anytime a node of that type is created using the node's title.
4) Create CCK types called "main_dish" and "sides".
5) Alter "dinner_vocab" so it is also used by these two new CCK types.
6) Create some main dishes and sides and link them to a node of type "dinner_cck" through the NAT-created taxonomy.

Then start creating views and such to tie it all together. I've been using it with taxonomy_access and taxonomy_menu and they all work pretty well together other than a few minor problems.

Zen’s picture

Zen commented
Status: Active » Fixed

Appears to be fixed - thanks :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.