The taxonomy "help" text is so sublimely complex. It throws around all of the terms that site admins need to know about (taxonomy, vocabulary, term, category, etc.) without clearly explaining how they're used in drupal, plus lots of bonus words like thesauri and descriptors. --mark http://api.drupal.org/api/function/taxonomy_help/6 The taxonomy module is one of the most popular features because users often want to create categories to organize content by type. A simple example would be organizing a list of music reviews by musical genre. Taxonomy is the study of classification. The taxonomy module allows you to define vocabularies (sets of categories) which are used to classify content. The module supports hierarchical classification and association between terms, allowing for truly flexible information retrieval and classification. The taxonomy module allows multiple lists of categories for classification (controlled vocabularies) and offers the possibility of creating thesauri (controlled vocabularies that indicate the relationship of terms) and taxonomies (controlled vocabularies where relationships are indicated hierarchically). To view and manage the terms of each vocabulary, click on the associated <em>list terms</em> link. To delete a vocabulary and all its terms, choose <em>edit vocabulary.</em> A controlled vocabulary is a set of terms to use for describing content (known as descriptors in indexing lingo). Drupal allows you to describe each piece of content (blog, story, etc.) using one or many of these terms. For simple implementations, you might create a set of categories without subcategories, similar to Slashdot's sections. For more complex implementations, you might create a hierarchical list of categories. For more information please read the configuration and customization handbook <a href="@taxonomy">Taxonomy page</a>. array('@taxonomy' => 'http://drupal.org/handbook/modules/taxonomy/') The taxonomy module allows content to be classified into categories and subcategories, or vocabularies and terms. Terms may be organized in controlled vocabularies (vocabularies with multiple lists of categories), in thesauri (controlled vocabularies that indicate the relationship of terms), in taxonomies (controlled vocabularies where relationships are indicated hierarchically), or in free vocabularies (vocabularies where tags are defined during content creation). To view and manage the terms of each vocabulary, click on the associated <em>list terms</em> link. To delete a vocabulary and all its terms, choose "edit vocabulary". When you create a controlled vocabulary you are creating a set of terms to use for describing content (known as descriptors in indexing lingo). Drupal allows you to describe each piece of content (blog, story, etc.) using one or many of these terms. For simple implementations, you might create a set of categories without subcategories. For more complex implementations, you might create a hierarchical list of categories.

On Nov 14, 2007 12:27 PM, Michelle Cox <mcox@charter.net> wrote:

On 11/14/2007 2:09:58 PM, Neil Drumm (drumm@delocalizedham.com) wrote:

...

Avoid use of "Taxonomy" in the UI. The overall system, despite the module name, is "Categories."

I took a quick peek on my site and the only place I see it called "Categories" is on the menu label and the title of this page: ?=admin/content/taxonomy . Note the URL to that page. Seems to me like the overall system is "Taxonomy" with a half attempt to change it to "Categories" that failed. What's wrong with rolling it back while we think about what best to call it in 7?

And the heading of the fieldset on node/add/{content type with more than one vocabulary}. The name of the overall system simply is not used a whole lot. This naming system applies for Drupal 4.5 through 5, and may be changed for Drupal 6. We have quite a few precedents for using different labels in UI from what we use in the API or URLs: - node is content - path is URL alias - watchdog is log These differences happen and are okay. It would be nice to reconcile everything, but changing a core module name, and breaking a chunk of contributions, is harder than changing the UI label. -- Neil Drumm http://delocalizedham.com