Vocabulary per user (VPU)

The primary goal of this module is to provide a vocabulary for users with correct 
permissions that only they can edit and use.

A secondary goal is to make the vocabulary/term interface easier to use, since
this permission can be given to non-admins.

*** REQUIREMENTS

VPU requires Taxonomy.

It supports Token.

*** PERMISSIONS

VPU has two permissions:

 * 'maintain personal vocabulary' - grants users of this role a personal 
vocabulary.

 * 'access full term form' - without this permission, users with 'maintain 
personal vocabulary' will see only a simplified version of the term form:
title, description, and weight.

*** TEMPLATE

VPU requires a sacrificial vocabulary to be used as a template for the personal
vocabularies it will create. Whatever settings this template has will be applied
to all new personal vocabularies.

VPU supports user tokens in the title, so if you have the token module installed
you can name your template such as "[user]'s vocab ([uid])".

*** CONFIGURE

After setting permissions, visit /admin/content/taxonomy/vocabulary_per_user

Pick whether personal vocabs for other users should be disabled or hidden.

Choose the template vocab.

There is a batch option at the top to create all the new vocabs.

*** BEHAVIOR

Users with the 'maintain personal vocabulary' permission will now have a 
"My Vocabulary" tab on /user. Under this they can manage add, edit, and delete
terms within that vocab.

They cannot change the vocab name.

When editing/creating a node, users with 'maintain personal vocabulary' will see
their personal vocab. Depending on the module settings, they might see other
users' vocabs, but they will be disabled. The template vocab will not show up.
Non-personal, non-template vocabs will work as always.

Users with 'administer taxonomy' rights can also manage personal vocabs from 
/user

*** THANKS & NOTES

The base for this module was http://drupal.org/project/taxonomy_user
In contrast with http://drupal.org/project/community_tags, these vocabularies
are essentially private.
VPU was needed to allow non-profits to define their own distinct set of terms
for an agency catalog.


*** QUESTIONS & TODO

Not yet sure of the best reaction to user deletion and/or uninstall
View integration is hawt