taxonomy

Robert Douglass sounds the call for reviews of three key taxonomy usability improvements:

Jag har stött på ett delikat problem gällande taxonomi och användare, och tänkte höra om någon i närheten sitter med en lösning. I korthet går det ut på att hitta ett sätt att koppla en taxonomi/kategori till användare.

I've just updated my PayPalNode module which handles classifieds using per taxonomy term pricing calculations to make charging for a content-type more flexible.

It's available now for 5.x and is live on one site already.

If anybody else would like to test it and give feedback that would be great. I'm not looking for new feature ideas at present.
If everything works, I'd like to get a 1.0 release out.

Find it on the project page.

Looking for advice on when to use:

• http://drupal.org/project/taxonomy_fields
• http://drupal.org/project/cck_taxonomy
• http://drupal.org/project/content_taxonomy

They all seem confusingly similar.

I love the way you can use a phrase like "People who live in %" using the regular Drupal profile module and then by clicking the link, get a list of all users who live in %. I'm trying to get the same thing happening with profiles as nodes. I've tried using CCK taxonomy fields in both the Node Profiles and the Bio Modules. It almost works, but only intermittantly. Sometimes I get the message "There are currently no posts in this category ..." other times, some users will show up and others won't - even when they have been tagged with the the term.

At long last, a group exists to discuss all things taxonomy, especially managing taxonomy. The clamor can subside!

Seriously, why hasn't taxonomy had a home on groups.drupal.org before now? What can we do to ensure taxonomy is used and developed to its potential?

Short report about what's going on with the taxonomy manager. Last week my exams at university started (until end of June), so not much coding yet.

User Interface

On any CMT-eligible node page, you have three operations.

The first, add term, applies to the node itself, and so can always be present.

The second and third apply to terms, and so have to have a user interface for each term a node has (if any).

Each operation can stand alone, but the latter operations can also be seen as subtasks of the above.

term[s]  node
| |      |
| |      |_> add new or existing term
| |______L_> position term 
|_L______L_> add new or existing synonym and flag which gets naming rights

This project, like the rest of my life in general, is dedicated to my father, John Melançon, 1928–2007.

I'm a week [or two] behind on GSOC updates. I'll try to catch up with a couple in the next few days, and then be on report-back schedule every Friday. Less focused data dumps have been and will continue to be posted to Agaric Design Collective's site (desperately in need of an overhaul).

The Community Managed Taxonomy (CMT) vision, to recap, is the option to put taxonomy vocabularies under the control of your site's user community. Huge free tagging vocabularies can become consolidated and even hierarchical without giving up any of the openness of community tags. Categorization of content and even site structure can be put in the hands of users. Instead of trying to imagine in advance what categories ought to exist, or re-filing everything later, you, the admin, can spend your time on more important things, like reading Summer of Code posts about what's on its way for Drupal!

The first week of summer of code is nearly over. So it’s time for a short report what I’ve done so far with the “Taxonomy Manager”.

First of all, a short description of my project. At the moment, the Drupal’s taxonomy module provides only a simple administration page for adding / editing terms. When having a bigger amount of terms, it gets hard to manage the list of terms. My project will implement an additional powerful interface for managing longer lists of terms.