Creating a vocabulary
Last modified: January 3, 2009 - 14:49
When setting up a vocabulary, Drupal will prompt for:
- Vocabulary name (Required) -- A name for this vocabulary; for example, Topics.
- Description (Optional) -- A description of the vocabulary (this item may be used by some modules and feeds).
- Types (Required) -- A vocabulary may be associated with or more node types. So, an administrator might declare that a particular vocabulary is to be associated with stories and blogs, but not book pages. If an expected node type is unavailable, check and make sure that the module for the specific node type has been activated.
- Hierarchy (Optional) -- Allows a tree-like taxonomy (In Drupal 5, hierarchies are set as an option. In Drupal 6 and later, all vocabularies are hierarchical if that's how you arrange the items.).
- Related terms (Optional) -- Allows relationships between terms within this vocabulary. Think of these as "see also" references (this item is not used by many Drupal modules).
- Freetagging (Optional) -- Users create terms as they go by typing comma-separated lists of the terms they want to apply to content instead of selecting from a pre-existing list of terms. Freetagging vocabularies will present users with a text input that will autocomplete with matching terms if they exist.
- Multiple select (Optional) -- Allows users to categorize nodes by more than one term. Useful for cross-indexing content. Nodes may then appear on multiple taxonomy pages.
- Required (Optional) -- Requires a user to select a term in this vocabularly in order to submit the node. Otherwise, when creating a node, users will be offered a none option as the default for each vocabulary.
- Weight (Optional) -- Allows the administrator to set the priority of this vocabularly when listed with other vocabularies. When vocabularies are left with the default weight of zero, Drupal displays multiple vocabularies in alphabetical order. Increasing a vocabularies weight with respect to other vocabularies will cause it to appear after them in lists. Conversely, lighter vocabularies will float nearer the top of lists. Useful for specifying which vocabulary a user sees first when creating a node.
