Revision of Categories in Drupal from 2006, December 15 - 11:57am

The revisions let you track differences between multiple versions of a post.

Categories are assigned to resources (such as webpages) in order to organize our site. This functionality is provided by Drupal's Taxonomy module.

Categories can then be assigned properties, such as access permissions or site navigation hints, that will then be inherited by the resource they're assinged to. In this way, the behaviour of resources on our site can changed anytime by simply assigning the resource select categories.

Not knowing exactly what we'll be doing with our site (it should be a collaborative process), I (Dave Allen Barker Jr) just created two categories (Administer, Content management, Categories): "Category" and "Tag".

Category

A structured taxonomy maintained by webmasters


The name for this vocabulary. Example: "Topic".

Description of the vocabulary; can be used by modules.

Instructions to present to the user when choosing a term.

A list of node types you want to associate with this vocabulary.

Allows a tree-like hierarchy between terms of this vocabulary.

Allows related terms in this vocabulary.

Content is categorized by typing terms instead of choosing from a list.

Allows nodes to have more than one term from this vocabulary (always true for free tagging).

If enabled, every node must have at least one term in this vocabulary.

In listings, the heavier vocabularies will sink and the lighter vocabularies will be positioned nearer the top.
Tag

A classic folksonomy to also inform the Category taxonomy.


The name for this vocabulary. Example: "Topic".

Description of the vocabulary; can be used by modules.

Instructions to present to the user when choosing a term.

A list of node types you want to associate with this vocabulary.

Allows a tree-like hierarchy between terms of this vocabulary.

Allows related terms in this vocabulary.

Content is categorized by typing terms instead of choosing from a list.

Allows nodes to have more than one term from this vocabulary (always true for free tagging).

If enabled, every node must have at least one term in this vocabulary.

In listings, the heavier vocabularies will sink and the lighter vocabularies will be positioned nearer the top.