How to list nodes where its terms name is one of _another_ vocabulary's term name?

My situation is as follows:
Nodes are tagged with different terms(e.g. finance, tennis, football, etc). I would like to group tennis and football under Sports section. My idea is to create a vocabulary called Sports and add tennis and football as terms in this vocabulary. Then filter terms names of nodes corresponding to terms names in Sports vocabulary. How to do that with view?(Filter term name to another vocabulary's term name).

Note: I know that you can write the terms directly in "Taxonomy: Term" filter but it would be much more elegant to control the list of terms through the vocabulary.

Comments

merlinofchaos’s picture

If you have just one term per node, you can add Taxonomy: Vocabulary as a field and group on it. If you have multiple terms per node, however, this is not a workable solution and the piece you need to do this doesn't exist yet.

denislabonkink’s picture

you can add Taxonomy: Vocabulary as a field and group on it.

I don't understand the part "group on it". How would you do that?

Probably my question isn't clear enough. Here are more informations:
I want to create a Sport node view type where it will only show nodes(Row style: Node) with term name matching 1 of the terms names of a specified vocabulary.

On a side note, is there a way in Views to allow users to input their own SQL query?

merlinofchaos’s picture

In the style settings there is a select field for the 'grouping field'. That's how you group on a field.

giorgosk’s picture

Merlin
If I understand well on the 5.x views we could add "Taxonomy: Terms for " fields but NOT YET on 6.x views ?
Is that feature going to be added in the near future ?

merlinofchaos’s picture

Use Taxonomy: All terms (it lets you restrict what vocabularies it uses).

giorgosk’s picture

Merlin
Thanks a lot,
"Taxonomy: All Terms" made me think that it was NOT what I was looking for

merlinofchaos’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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