taxonomy

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.

Hello!

I'm curious - is there a good (and ideally easy) way to incorporate tagging of comments?

I'm thinking D6 here. Is node comment a good way to go? the only way to go?

Has anyone been down a similar road before? Any pitfalls?

Looking forward to any tips you might have!

Thanks!

Hello,

I've been searching in the hope that there is an answer but didn't find anything, so apologies if I turn out to duplicate an existing thread.

I am building a site with several vocabularies. I use Taxonomy Menu to turn some of them into a menu. What I want is this: if a user clicks a term (from vocab A) in the menu he/she should get a page with only those nodes that match vocab B. And I need to style that in a certain way to.

Example:
- vocab A has terms: archives, libraries, courses
- vocab B has terms for countries: Britain, Germany, Belgium

I'm working on a review type website and i've broken it into Categories. I got the Categories working with Taxonomy which is pretty cool, but what I want to do is when someone goes to a "Category" I want to give them the option to sort the listing by popularity (and other criteria) would the Views Module be the thing to do that?

Thanks,

I'm trying to plan out how to do a review type site in Drupal if anyone has done something similar.

Sorry this is so long. I tried to include as much detail as possible, so it could kind of act as a “recipe” for future websites like mine. (By the way, I didn’t know if this applied more to “Views” or “Taxonomy” so I posted this in both groups. I know duplication is frowned upon, but I know that most people aren’t members of both groups so I didn’t want to select only one group if the solution really lies within the conceptual framework of the other group).

I've just installed the Organic Groups module to our site at http://opensourceschools.org.uk (well, to the dev. copy at the moment...) and would love to use this to provide tailored content to school leaders, teachers, techies etc who form distinct segments of our growing community. Hitherto, I've used a taxonomy to tag content for these groups - is there any way to move the tagged content into the new groups automatically, or do I have to work my way through the archive?

I'm working on a D5 site (yes, unfortunately!) where we use taxonomy to create a "poor-man's-epublish" - basically a view of newsletter issues and articles under them. We have a vocabulary for "Newsletter issue" and just tag article nodes with the term of the issue, like "Fall 2008." Since there are other vocabularies on those nodes we're using the primary_term module to make the newletter issue the primary term.

It's all working great except for sorting: primary_term.module only implements views sorting by term id - it ignores the term weight:

Hello everyone,

So I'm working on this project, and it's been going pretty great thus far. I'm incredibly close to being done and really kicking ass at getting the site perfect. Then I stumble accross this big pitfall with vocabulary index: I don't want to display terms with no nodes assosciated with them.

Explenation of where the problem occurs:

Hej,
Jag bråkar lite med taxonomy och views men har fastnat lite med argumenten.

Jag har aktiverat vyn taxonomy_term, som är en standardvy, för att ersätta taxonomi term-sidor.
Jag har en vokabulär, Märken, som är uppbyggd på detta sätt:

Märken
--Tillverkare 1
------Produkttyp 1
------Produkttyp 2
--Tillverkare 2
------Produkttyp 1

Varje produkttyp har noder kopplade till sig. Tillverkare har inga noder kopplade till sig direkt utan är bara "pappa" till produkttyp.

Taxonomy as implemented by Drupal is already an abstraction. However it can benefit from toolkits that add pre-existing taxonomy structures to it according to a user's requirements.

This core is intended to work in conjunction with taxonomy but concerns it's self with taxonomy structure instead of taxonomy function. Although it is not the purpose of this project to develop structures so much as allow the user to, instances of difference in structure are useful to express as examples: