By venkat-rk on
I am trying to understand the distinction between 'related terms' and 'multiple select' while creating a vocabulary.
Related terms is defined in taxonomy help as "Allows relationships between terms within this vocabulary. Think of these as see also references", whereas, Multiple select is defined as " Allows pieces of content to be described using more than one term. Content may then appear on multiple taxonomy pages".
In effect, they seem to be the same. Or, am I missing something?
Comments
I am having trouble myself
To me it looks like this:
Multiple select means you can put one node into multiple categories (e.g. Airports and Restaurants and San Francisco) if you are reviewing a restaurant in San Franciscos Airport.
The result is, that you can browse to the content trough 3 different categories.
I am not sure what related items are for, but the node will be only in the category you have specified.
Airports and Airlines can be related. Meaning while you are browsing Airports, you can also get recommendations on Airlines.
In fact I am struggling with a similar question myself right now.
My problem is:
How can I have a page and a book belong to the same category, but when I browse that category only have either the book or the page show up.
E.g. Pages are for Reviews, books are for Articles.
I want to see an Article on California, or a Review of Hotels California.
Even better would be, when I browse Categories, have the articles show first and below all articles are the reviews.
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
One is for node description(s), one is for term structuring
There is no intrinsic relationship between Multiple Select. It's just saying that one thing can be described in several ways. Big. Red. Dog.
Beef Stroganoff in a menu may be categorised using Multiple Select as being both a Stew and a Beef Dish.
That is, this item can be classified in both of these 'classes', independant of each other.
Related Terms defines relationships between terms (as you quoted) irrespective of actual nodes.
Other terms related to Beef Dish may be Lamb Dish, Pork Dish, partially because if your recipe book was divided into a chapter that was titled "Beef Dish", these are chapters I'd expect to see alongside it.
A related term to Stew may be Soup or Curry... for the same reasons.
This way you can have a recipe book that is divided into chapters on both axis!
... there may be justification for using a totally separate vocabulary altogether for Ingredients vs Preparation, but that's probably overkill.
Whether you think antonyms and alternatives are "related" is up to you and what you want to achieve. A user manual certainly needs the documentation for encoding to be related to the documentation for decoding, whereas you won't get much mileage by declaringr Windows Software as being related to Mac Software
There is also Term Aliasing for terms that really are the same thing.
If you don't fully see the need for using these terms and using this structure, don't use it! Just because a Taxonomy can be structured doesn't mean it always should be, sometimes all you want is a list of keywords.
.dan.
.dan. is the New Zealand Drupal Developer working on Government Web Standards
Thank you for that excellent
Thank you for that excellent explanation. Some or all of this should really be in the handbook. It is so tiresome to figure out the meaning by trying it out on the site. After a while, it goes all over the head.
Is term aliasing the same as 'synonyms'?
Too much terminology
Glad it helped. If you liked that, I've got more information theory for you
Sorry, yes.
I should have used the proper term - I just didn't think of it at the time. "term aliasing" is a phrase I made up. forget it.
(it still bugs me that everywhere there is talk of 'Taxonomy' and 'Terms' but the admin interface is still labelled 'Categories' to mean the same thing ...)
.dan. is the New Zealand Drupal Developer working on Government Web Standards