every user has their own vocabulary

so you can show, but disabled-- see what everyone else has been tagging a node with

http://castlin.net/blog/1/2009/03/vocabulary-user

Ontology module in SCF profile's custom modules directory, originally authored by Mark Goetz, is very close to ready to be committed to Drupal.org. It relies on Taxonomy extra (taxonomy_extra) module, originally by Alister Lewis-Bowen, and also in SCF profile's custom modules.

Make the (presently undeclared) dependency on graphbrowser module optional.

While we prefer to use existing modules rather than create custom ones whenever possible, the specific needs for storing additional Gene Ontology data with Drupal (multiple kinds of relationships between terms) and the functionality of Term Fields module did not match up.

Furthermore, Term Fields:

Community Supported Agriculture
17 people here.

Who is interested in building the tools, and who just in deploying them?

Filter it through recipe suggestions.

Any CSA with capital resources?

About 2,000 CSAs in the U.S. About half, maybe, have web sites. Most do not have interactivity-- many have probably paid a chunk of money on this.

We have a tricky user interface problem for taxonomy.

We have a very large hierarchical vocabulary, and multiple terms can be selected.

Currently the tree is much too large to reasonably navigate and control-click, control-click the terms one-by-one without a disastrous mistake

As it stands now SCF's project manager would prefer a type-ahead completion like free tagging terms get.

This is how one would embed it in a node.tpl.php, but this should all be done in a pre-process function instead.

<?php
// here it is all together, expect normal typos:
$normal_terms = '';
$special_terms = '';
foreach ($taxonomy as $tid => $term_object) {
 $term_name = $term_object->name;
if ($term_object->vid == 3) {

Struggling with taxonomy import.

After stripping everything out, the conclusion is that taxonomy_save_term, by itself, without even the hooks to add extra data, is simply too slow, with a minimum of three database calls per term. (data, hierarchy, vocabulary)

<?php
// commented out below from TCS, possibly of interest
// $term = (object) array(
// 'predicates' => array(),
// );

// $term->id = $concept->getAttribute('id');

// $term->uri = $url;

// $term->name = $termname->textContent;
// $term->namerefs[] = $termname->getAttribute('ref');

The parser needs to follow the instructions here:
http://geneontology.org/GO.format.obo-1_2.shtml

To import a file of the kind available here:
http://geneontology.org/GO.downloads.ontology.shtml

Taxonomy Import/Export is the slightly misnamed in Drupal's CVS http://drupal.org/project/taxonomy_xml

How to in Views 2

Using a taxonomy term associated with a node as the argument in your block view. In the original Views module, the PHP Argument handling code was a collapsed fieldset that opened to reveal a textarea in which to input code. In Views 2 this is still necessary, unless we're missing out on some uber-advanced method, but harder to get to.