Taxonomy

Tag Trap is a module that allows administrators to specify certain tags that are not allowed in a free-tagging taxonomy environment. To be clearer, if you've set up your site to have one or more free-tagging fields for content creation, you can apply this "trap" to the free-tagging field's vocab so that when the user submits the form (the node creation or edit form) for validation, the validation will fail if any of the terms the user supplied are in the exclusionary list for that vocab. It fails validation on the first term that it comes across that is not allowed.

By default, Drupal displays free tags in alphabetical order. Sometimes, however, the order that tags have been entered per node is important. Perhaps more relevant tags are entered first. Maybe larger sponsors should display before smaller sponsors.

Tag Order module allows you to select vocabularies whose terms you would like to preserve in the original order entered per node.

This module was developed for http://www.fastcompany.com/

Description

Provides an alternative, user friendly interface to multiple select input box for selected taxonomies on node creation.

Designed specifically for 2-tier hierarchical classification systems, the module creates tabs for the root elements. Each tab contains the corresponding children, which are click to select and click to remove. It also add an area to display the selected terms and ability to remove them without searching through the tabs for the undesired terms. The module will also allow you to target specific taxonomies to act on, while leaving other taxonomy interfaces unaltered.

This module enables to associate nodes according to different criteria such as Taxonomy and CCK fields.

You can give a different weight for each criterion. All criteria will be aggregated by the main module which compute a matching score for each couple of nodes. Then, for a given node, you can get the other nodes that are associated to it. The associated nodes are ordered by the matching score they have with the given node.

Different associations can be defined with their own criteria and weight.

Auto-generates HILCC (Hierarchical Interface to the Library of Congress Classification) taxonomy terms for nodes that have LCC call numbers (library-assigned numbers like "QA 76.73 .P224 2005"). This can help you build a Drupal site that auto-organizes by a hierarchic subject tree.

For instance, items with different call numbers like QA76.73 and QA75 would be clustered under the Drupal category Engineering & Applied Sciences > Computer Science. The taxonomy terms are generated during node creation and update, and now optionally during cron runs and using node batch operations (from admin/content/node).

Possible uses are:

• Subject-based search, for instance using the Apache Solr module
• Subject-based breadcrumb, using the Taxonomy Breadcrumb module.

(For an example that uses all these modules, see the links to the demo below).

CA Taxonomy provides actions and condition checks for nodes and their taxonomy terms for the Conditional Actions module bundled with Ubercart 6.x-2.0

Requirements

Ubercart 6.x-2.0-rc1 or higher.

Credits

Original development sponsored by FourChords Creative LLC.

Callouts creates a way to display multiple blocks that are related by taxonomy terms. After you place the module into a region on your site, when a user goes to a page any callout blocks (callout is a new content type) with the same taxonomy terms as that page will be displayed in the region.

This Module is great if your looking to show related products in an e-commerence enviroment, or announcments depending on what page of the site your users are on.

This module provides a method to manage one to many relations between nodes using a taxonomy vocabulary to assign meaning to each relation. Only one level of parent/child relationships is actually supported.

Child nodes are displayed in tabs on the parent node, and can be created edited, cloned or deleted directly from there. The labels for these tabs are defined by the terms of a particular vocabulary assigned to children nodes.

Nodes of a particular content type can be configured to become parents of nodes of another type from the Content Type Edit form. It is required that child nodes are previously configured with a fieldgroup that contains two fields: a node reference that will hold the relation with its parent and a taxonomy field that will hold the term that assigns meaning to the relation.

This module has been sponsored by Gamefila and is published here at Drupal with the aim to be useful to anyone else, but no feature requests will be accepted as the current functionality is frozen and based on sponsor requirements. Please, use it only as an example or additional resource for your own implementations. Only support to understand the exact features it currently provides or questions on how it works are provided.

This collection of modules integrate some of the functionality provided by the Ar-PHP library, a library designed to provide solutions for common problems when processing Arabic content.

The main module includes the ArPHP library. The list of included modules: