Taxonomy

What is it?

This module provides two ways of referencing relevant content. Both of these methods provide configuration to filter for specific content types and vocabularies, limit the maximum size of the result and provide some header text. The result on both cases are a list of nodes which the module considers most relevant based on the categorization of the current page. This is achieved by finding other nodes which are of one of the allowed types and have the most number of terms in common. The two methods are:

Blocks

This module will provide as many customisable blocks as a site administrator wants. Each block has its own settings for node type, vocabulary, maximum result size and otional header text. Blocks can appear on any page which causes terms to be loaded into Relevant Content. Usually this is any page which views a node (a node page or a view such as a taxonomy term list). Usually you only want a block to appear on a node page, however you may find situation where you want to place a block on a non-node page.

CCK (new)

The new CCK Field Type (available in both 1.3 releases for Drupal 5 & 6). This is a read-only field (much like Node Referrer) which allows the administrator to embed a field that is "display only" (ie, nothing appears on individual node edit forms). This field is configured in the same way the blocks are configured; node type & vocabulary filtering, maximum result size limit and header text. The advantage of the CCK method is the result set is more "embedded" within the content.

Place is a collection of modules for storing and displaying geographic location data and in Drupal.

Displays a vocabulary as a tree within a block. Provides blocks for each of the vocabularies on a site. Browsing the terms within a block is done via AJAX like calls, making it quick and a light load on the server.

A demo of this module can be seen with the bird classification on our demo Scratchpad.

This module was inspired by the work of R.D.M.Page on PygmyBrowse.

Tax Tree Nodes shows a taxonomy including all terms with at least one node attached to it as well as a link to the node.

The admin settings allows you to:

Note: As of 2009/11/09, this module appears to no longer be supported. If you are interested in taking this module over, or you as the module maintainer feel this message has been posted in error, please reply to #237109: Taxonomy Strider module appears abandoned.

This module allows administrators an avenue to manage free tagging terms while still encouraging users to suggest new terms.

Examples of potential usage:

• If a tag added by a user is a synonym of an existing term, (optionally and) automagically replace it with the existing term. This can also be used to handle alternate spellings of a term, typographical errors and so on.
• If a tag added by a user uses the related terms feature of the taxonomy module, optionally tag the node with those terms as well.
• Optionally also insert the ancestors (parents, grandparents etc.) of the provided tags.
• Make a free-tagging vocabulary read-only. Non-existent terms are not included and are instead sent to a management interface where they can be dealt with appropriately.

This module lets administrators blacklist a set of terms on vocabularies. This is useful if a vocabulary can be modified by your end-users (prevents bad words from polluting your tags on a social-networking site, for instance) or if the vocabulary is feeded automatically (for instance with keywords extracted automatically through the Yahoo Term Extraction module).

Provides an action (via the actions module) that triggers a configurable list of pre-existing actions if a node contains certain taxonomy term values, which are configurable as a comma separated string, including regular expressions (eregi).

I guess you could look at this as filtering an action depending on a nodes taxonomy terms, it will check all vocabularies assigned to that node-type.

With this module you could

This module allows site administrators to easily collapse several similar (synonymous) terms into one super-term, as to avoid duplicate terms (for both ny and New York, say). This will likely be in core of Drupal 7.