Taxonomy

Hi!

I'd like to use Taxonomy in order to define site-wide filters.

What I mean is the following:
On the start page you select a region and one or more Music styles. When you then enter the site, the selections for Regions and music styles should be used as a "global filter" so that one can navigate the site without having to re-select the region and/or Music styles over and over again.

How can this be done?

Thanks
Christopher

If I click on a term in a taxonomy term page I would like to have a list of associated nodes with only titles and not a page with the full nodes.

I have found various possible solutions but they don't seem to work. To be clear: I use the Zen theme and I am pretty much a beginner in php..:
- creating a special node-taxonomy.tpl.php : something then needs to be changed in template.tpl.php but I am not sure what?
- inside the node.tpl.php file do it via $page;
- do it via modules: it can be done with Taxonomy VTN but then I lose the feeds that the normal taxonomy module provides.

Hi there! I'm trying to set up a menu that contains links to all the nodes/stories associated with a term, is there a module for doing that? I've tried looking at "taxonomy menu" and "taxonomy context" but they only seemed to create links to terms in a vocabulary, not to nodes in a term..
Basically, I have a vocabulary called "categories", with 2 terms in it "health" and "food" and I'd like to have two menus in the right column with links to all the articles in each category (and they should update whenever I add a new article)

Thanks!

We are in a debate as to whether we should use taxonomy or node reference!

Our website enables selling of Products, especially for Schools and Colleges. Users can create products or purchase products on the site. The Products have some categories associated with it.
Has a tree structure, root, L1, L2,L3. Parts of the categories are repetitive.

eg. Books
-- Education
---Physics
---- Grade I
---- Grade II
---- Grade III
---Chemistry

I think it's time taxonomy module got some more love in core. Drag and drop etc. was nice to get in D6, but there's much more we could do. Also I keep seeing various taxonomy administration helper modules cropping up - which is good, but there's no core patches cropping up alongside them, which is a shame, so I'm starting this in the hope of generating some discussion about things we could do this release cycle.

There's three obvious areas where Taxonomy could use some help.

Administration:

Merging terms.
Moving terms between vocabularies.
Mass operations (delete, edit).

Has anyone in this group found an elegant way to override the order in which Taxonomy Terms are displayed on a node? Or any way, for that matter...

Hi all

Just wondering if anyone has played with the idea of content type specific taxonomy settings.

Currently, the only way to implement a 1-1 and a 1-n relationship between two different content types that I know of would be to do this manually via CCK or the fapi for the two types. Similar situation for required fields.

A quick look at the code, albeit a very very short look, seems that this would not be to hard to implement this. Free tagging could be more interesting. Has anyone tried this in the past?

I think it'd be useful to have an overview of the various content recommendation modules in this group, and eventually a comparison review in the Handbook. I haven't used any of these apart from similar by terms, and may well have missed some, but we can expand as we go along. Additionally I've not used included anything like statistics, voting_api, views_bookmarks etc. which could probably be factored into a custom recommendation/ranking solution but aren't drop-in.

Content recommendation engine
http://drupal.org/project/cre

In a discussion on the main site- http://drupal.org/node/256913 it has been hinted that there is a module available to automatically do this:

When the user selects a taxonomy term to search, and that term is in a hierarchical vocabulary, automatically search the children of the term, to some predefined depth

I.e. when the user clicks on a link for "/taxonomy/term/tid" the system actually performs "/taxonomy/term/tid/1", or "/taxonomy/term/tid/all".

Greetings,
I'm having a strange issue with my taxonomy terms. It is quite possibly a views issue, but I figure I'd ask here first to see if anyone has experienced this before. Whenever I'm creating a view and want to filter by taxonomy vocab, the first term in my vocabulary is not visible in the filter. Whenever I give that term a heavier weight, it shows up in the view filter, but then the new first term disappears. Strange. Any thoughts, suggestions? Thanks all, in advance.
~Greg

Hello Everyone,
Is there a way (a view, an existing module, a swell hack), to limit the display of a vocabulary in a node editor?
For example:

Countries (Vocabulary)
- Africa
   - Kenya
   - South Africa
- Asia
   - Japan
   - Thailand

Hi I am new to Drupal and hence taxonomies and I need to create a way for articles which are written on a separate system to be posted to Drupal. So far I have been able to do most of what is required via XMLRPC however I am not quite sure how to add a valid taxonomy to an article and post it at the same time. For example can I write the taxonomy to the article at the same time as it is posted or is there another way I should do it, also what is the format of the data which I should use? I am writing the module using Python.

A while back catch created a feature request for the Project issue tracking module to allow free tagging on issues (see http://drupal.org/node/187480). The use case he indicated was to be able to attach certain labels to issues, for example benchmark, needs re-roll, needs doxygen, etc. Other use cases would include tagging issues that need testing in certain ways (eg. MySQL, PGSQL, Javascript, IE, etc.) and tagging issues that are good for certain audiences (eg. newbie, GHOP, DROP, etc.).

Just looking around for components for an issue tracking system. One key feature would be that users can setup their own controlled vocabulary for their issues...

WordNet (http://wordnet.princeton.edu/) is a large lexical database of English. Nouns, verbs, adjectives and adverbs are grouped into sets of cognitive synonyms (synsets), each expressing a distinct concept. Synsets are interlinked by means of conceptual-semantic and lexical relations.

One possible approach to taxonomy on a social networking/community site is to give each user their own Vocabulary. The following snippet does just that. It is a basic no-frills hack for creating a Vocabulary with the name of the current User (first it checks to make sure such a Vocab doesn't already exist). I left the "echo" lines in it so you can see what it's doing. Feel free to bang on it, bag on it, chop it up, use it in your modules, whatever.

I have release a new Drupal module regarding taxonomies, called Taxonomy blacklist.
This module lets administrators blacklist a set of terms on vocabularies. This is useful if a vocabulary can be modified by your end-users (prevents bad words from polluting your tags on a social-networking site, for instance) or if the vocabulary is feeded automatically (for instance with keywords extracted automatically through the Yahoo Term Extraction module).

There's a new tutorial at http://drupal.org/node/200631 which is a different approach to Taxonomy Access Control than I have seen, a very different approach to Groups (as a concept), and multiple Domains (hence a multisite solution). I am trying to discern what is going on with og, mulltisite, domain access, and TAC generally.

For mass categorization or labeling of Drupal content, use the "taxonomy node operations" module:

http://drupal.org/project/taxonomy_node_operations

"Adds the ability to assign terms to nodes in the node operations dropdown in admin/content/node."

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

The taxonomy help page text is not quite as good as it could be. Please help rewrite it. This is a wiki page. Discuss changes in comments and weave them back into the main text. I'll include the text twice. The first text is the reference and the second instance of the text is the revised text that we'll try to put into Drupal 6.

Here it is - the current text as a reference:

The taxonomy module is one of the most popular features because users often want to create categories to organize content by type. A simple example would be organizing a list of music reviews by musical genre.

Our next meeting will address the question, "Taxonomy - What is it and what can it do for me?"

I know our last meeting was just two nights ago. But it is clearly time for a discussion on taxonomy. Let's see if we can't get a discussion going before the meeting and set ourselves up to delve deep into taxonomy at our next meeting.

For simplicity sake, Ontology and Taxonomy are the same thing.

The stormy land where CCK meets taxonomy is looking more promising all the time.

Adding to CCK Taxonomy and Content Taxonomy there's a couple more that are even more exciting to me, because I think they emphasize using taxonomy to store their data and relationships.

http://wimleers.com/blog/new-module-hierarchical-select - very slick.

http://drupal.org/project/cck_taxonomy_ssu - allows multiple select.

What modules do we use to make Drupal core taxonomy better, easier, prettier, or tastier? Add to the wiki!

Helper modules

• Edit term - edit the term of the taxonomy listing you're looking at.
• Taxonomy manager - much better bulk management of terms, including moving and merging

Today, the SoC program official ends. I'm glad that I was able to make the first release of my project today. Last week has been an intensive week of testing (thanks to all my tester) and the weekend has even been more intensive with bug fixing and today I finally had time to write some documentation. So I think, most things are done.

Some highlights from recent weeks that I think I forgot to mention:

More soon...

We are getting closer to the official end of SoC, so it's time now to stop implementing new features and to to do a lot of testing and to fix bugs, so that I'm hopefully able to release a first version of the Taxonomy Manager by end of SoC.

As a result of ripping off the taxonomy module to make community managed taxonomy, I noticed some extra SQL in there. And it's been removed. I find this quite exciting, affecting core... even if just removing a few unnecessary letters.

As for Community Managed Taxonomy itself, the editing of community-managed vocabularies and necessary administration options that weren't even mentioned in any posted plans. Pushing through with node-based term adding and arranging as outlined in previous posts continues.

The last 2 weeks I spent a lot of time in adding paging mechanism to the tree structure, in separating the tree structure as a own form element type and in adding of a form for editing data from a specific term.

At the United States Social Forum I met a linguist and Drupal user who told me that taxonomy could implement any kind of classification he could imagine.

Now I think I'm beginning to see what he means. CMT just might unleash a latent, awesome power in taxonomy (if it does I'll be sure to tell the Drupal for Evil group).

Taxonomy doesn't have to be hierarchical or flat. Categorization can be mesh, lattice, or called most simply, network.

Again a short summary, what has been done the last week and what I've planed to do this week.

Progress last week:

Rework of weight management for terms

As announced in my last report, I did a total rework for the weight management for reordering terms. Initially, I planned to have weight select forms included in the tree structure. Soon, we saw, that this is not very nice.

The code doesn't actually quite do anything yet, but almost all the pieces are in place for community-managing of your taxonomy while browsing content. And, you can look at the code if you're very brave. An initial release will be coming to the CMT project page soon.

The cmt.module file is almost 1,000 lines long, plus an include file for the repetitive information of a form dropdown and the .info and .install files (I've been using install and uninstall a lot!)

Settings etc. work and an initial form for adding terms. Lots of thoughts and decisions documented at Agaric's project site.

Coded all the days before, during, and after Drupal camp weekend and have made good progress. Continuing to borrow heavily from taxonomy.module itself for the structure of tables and some functions, tweaked to make them community-managed, and from community_tags, especially for how to add a form on node view pages (in CMT's case, for endorsing and suggesting arrangements and terms).

Best thing, as far as CMT goes, was meeting more people who will actually want to use the module!

This week I got some feedback for the first parts of the taxonomy manager. People provided me with additional ideas, that's always great. Again I thought about some points, like how to manage term weights or how to do merging.

The only update of interest to the general populace is the creation, together with Matthias Hutterer of the Taxonomy Manager GSOC project, of the Taxonomy Drupal Group on this site.

(Apologies for the long delay in actually posting this.) Here's the user interface breakthrough - a breakthrough at least until I try to implement and use it, at least - for node-centric community taxonomy management.

After finishing my exams last week, I finally had much more time to work on my project this week as the last time.

So I started with coding. The first task was to write a simple jQuery script for a dynamic tree view (collapsible parents) for a vocabulary.

Robert Douglass announced a new release of the CCK Taxonomy Fields module. The module allows sets of terms to be used as custom fields on content types.

This release fixes Views integration and guarantees that hierarchical taxonomy lists are represented correctly wherever they appear.

Douglass would like help with sorting views by CCK taxonomy and free tagging support.

There's a patch to improve the handling of taxonomy terms applied to nodes which would also help contributed modules deal with them. Status is that it has to be re-rolled and then reviewed.

http://drupal.org/node/56670

UI idea

Here is an UI idea, which would require a close cooperation with mh's taxonomy browser. It's build on top of two parts, 1. a quick and easy UI for the creation of new terms while assigning and 2. the more extensive UI with all required flexibility and overview.

1. community categorization of nodes

People have an autocomplete tagging field on node view - with which they can tag the node. If the tag is new, it needs to be categorized. So you would need JS, that detects the new tag and asks the user for the categorization (small js taxonomy browser which shows only term categories (no leaves)?). It would be neat if it's possible to create new category (votes) for the term there too.
It would be cool, if voted categories also appear there, perhaps in another color.

2. community taxonomy manager

But what's completely missing, is a place where users get some kind of overview about the whole taxonomy. Which votes have been already placed? How can they vote for things like renaming terms, or recategorisation? So I would put a link to the "community taxonomy browser" on node view.
So, from the users point of view, I think it would be great if matthias' taxonomy browser, could work in "community" mode - where actions may require voting. Also important, it should show all voted terms again in another color, clicked on that term, user can vote for it, or also for placing it in another category, It should be also possible to see the votes of other people for that term, wherever they wanted to place it.
So what here would be needed, is a flexible taxonomy manager. You would need some hooks too extend it (display all votes for a term) and to separate the clicked actions from the logic behind (only vote instead of apply) - and so a good cooperation of you both would be needed.
I think this would get the user a really user friendly community managed taxonomy. While it's possible to do some quick things, mainly the creation and categorization of a new term, also with 1.

Voting tresholds

If you have a hierarchical taxonomy, it might be quite common that users vote for the same category. But it might be rare that user want to insert the same term - so multiple votes for the same term might be too rare.
-> Perhaps it would be a good idea, if it's possible to have the voting treshold apply for only X hierarchies. E.g. if the admin specifies a depth of 2, the management of the upper 2 hierarchies would be based on votings with the configured treshold, while the bottom is customizable directly (without votes).
So one can configure voting for more important categories, while the "leave tags" are creatable/changeable immediately.

We have the ability to "Add or edit vocabularies that pertain only to this group. Each vocabulary will be shown on the post authoring form. Use categories to organize content within your group."

What should our taxonomy group taxonomy be? Edit this wiki page to add or modify, and Matthias or I will get around to creating it soon enough.

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!