Taxonomy improvements for Drupal 7

In my humble opinion, the main source of taxonomy's suckage is the separation between the taxonomy add/edit forms, and the node edit form. I doubt I'm alone in that I find I have the best idea of how a piece of content should be organized when I'm writing it. If i find i want to add a non-freetagging term, I have to
1 save my work in draft form,
2. go to the taxonomy page,
3. find the proper vocabulary,
4. add a term,
5. then find my draft.

These 5 steps could be easily reduced to one step. Here's a rough mockup of what it would look like:

What I love about doing it this way is that users don't need to look it up in a manual... the feature is waiting for them as soon as they add their first piece of content.

++++++++++++++++++++++++++++++++
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
++++++++++++++++++++++++++++++++
work: http://www.onnetworks.com
blog: http://www.nicklewis.org

haha, Nick lewis you made my day. I am interested in this one because I think the way 37Signals handles these type of interactions is applicable here. They allow stuff to be added, as you hover over the parent it will show a few actions you can do, and you can in line change anything by clicking the edit when you hover over the link (Cant really describe, just look at a demo on their site) Most of the other interactions you mentioned should be do-able with dragging and dropping? (Merging terms. Moving terms between vocabularies).

@stdbrouw - If that was in response to what I wrote, I agree that vocabularies are by and large fine -- the only thing I was pointing out was that the taxonomy fieldset is titled "vocabularies" -- which is non-intuitive to a new user, and completely inappropriate in the context of a node form (where as its the correct terminology on a taxonomy management page...).

Renaming the fieldset to "Categories", on the otherhand, would ensure that the purpose of those form fields is clear to anyone who can read.
++++++++++++++++++++++++++++++++
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
work: http://www.onnetworks.com
blog: http://www.nicklewis.org

I really wish that core taxonomy terms could be contained in a node, which would then make it easier to do things like tell a bookmark or flag module to "follow" a specific tag from one person, or from everyone.

This is what http://drupal.orgh/project/category tries to do in part. But this could be done cleanly in Drupal core, and would let someone creating a site more closely emulate functions of sites like del.icio.us etc, in terms of being able to look at and "follow" terms in different ways.

Sam Rose
Social Synergy
Open Source Ecology
P2P Foundation

I've not used this module, but it was a SoC project, and has a recent dev release for 6 -- http://drupal.org/project/taxonomy_manager

FunnyMonkey
Tools for Teachers

I really like the 'free tagging' option in node forms. It's a quick way to select and add new terms for your nodes. The only problem with it is the hierarchy. I think it would be best to disable the free tagging option, when multiple hierarchy is selected for a vocabulary. The idea of adding a term dynamically to a vocabulary from within the node form (looking at the wordpress screenshot) would be a great improvement. Adding a select list for choosing the preferred vocabulary would be even better.

Last year I've created a module called 'vocabulary_browser'. I've created it for a costumer who got really fed up with the abstract way of D5 dealing with categories. My costumer wanted to administer his categories and store products in a visually hierarchical way.

add_term.png
term_added.png
add_another_term.png
change_view_term.png
change_parents.png
change_view_node.png

Great advantage of the module is the quickness of creating a large vocabulary with a lot of terms, sub terms, terms with multiple parents and so on. All is done with AJAX and without page refreshes. Per user collapsed statuses of folders are stored, so every time a user visits the vocabulary browser, everything is displayed the same way as when he left the page. Another advantage is the possibility of adding nodes to the terms on the fly.

Disadvantages of the module is the slowness of the scripts to load when the list of terms is getting very large. A solution for this could be that the script only loads terms of which parents are expanded. Another disadvantage is the node-edit form in the vocabulary browser. If a node type has a lot of fields, for example the product node from UC, it getting a little messy due the lack of space in the edit pane of the vocab. browser.

I'm not expecting that the vocabulary browser module has got a great future ahead, especially while it needs so much scripts to function. But it maybe could be a way to inspire others to great other ideas. Anyway a small simpler version of the browser, in node forms, could be very user friendly. The expandable / collapsibe folders feature is imo very nice. Saving the status of the folders per user is also very cool, i think.

My wishes for node forms:

• I would like a folder like (collapsible / expandable) hierarchical presentation of terms.
• Selecting other vocabularies should be made possible by using select list and AJAX.
• Drag and drop for changing the structure of terms.
• Creating new terms (or even vocabularies) on the fly.

Yeah, I think enhancing the taxonomy management capabilities is a great idea!

When using free tagging, misspellings and variations of a single tag or keyword topic creep in, so you end up with lots of low-node-count terms, all clustered around a single topic.

I had considered building a module to help sort this out - find similar terms (based on soundex or other methods), with emphasis on finding terms with few posts, allowing one to 'merge' the terms into the correct term, and update the posts that were assigned to the incorrectly-spelled terms that have been merged into the single term. This last bit is the most important, because I don't want nodes to lose their tags.

Anyway, that's one of those features I've wanted for a while. I haven't done any investigation into the techniques required to do the 'merge' and node reassignment.

I don't want to use synonyms for this because many times, the variations are due to typos or misspellings. :(

Michael Curry
Classified Ads Module For Drupal 6 | My hangout

I was on the phone with the guys at Acquia this morning about a taxonomy code sprint I am hosting in Chicago September 8-11, 2008 and he pointed me here. Understandably, this is extremely short notice, but we're really interested in increasing the performance of taxonomy to handle really big vocabularies as well as a number of other issues that are layed out here really well. The Encyclopedia of Life hopes to use Drupal to have an organism-centric multisite hosting environment and as you can image, are experiencing some of the shortcomings of the core taxonomy. We created a website to help us start organize the sprint at http://sprint.eol.org and will work on the list of needs over the next few days. If you have anything to add to this list, I'd love to get all of your feedback. There's a colleague of mine at the Field Museum in Chicago that is organizing the logistics and needs a head count from me so she can organize parking, food, etc. So, if you are interested in attending, please sign-up on the site above. If anything cool comes out of similar sprints at Szeged, this proposed sprint could hopefully be an extension/refinement of that work.

I donot know whether I am posting in correct group or not.

I have one doubt.

I have story content type and in that content type I want to add the radio button with private and public options.

If user select the private then I will not show the contents to all the users.

Is this can be achieved with taxonomy.If yes then please provide me the details on this.

The private module set the content type as private and public.Here users are not able to choose private and public.

I want that the users are able to choose the public and private.Here when user create the story node there is no option of private and public selection.

I think there must be one node access with fields api option in drupal core as cck is going to be integrated in drupal core.

This help us to create any content type as public and private with fields.

I went on this page and Google Chrome puts up a bit red warning saying:

Warning: Visiting this site may harm your computer!
The website at groups.drupal.org contains elements from the site focus.circulargenius.com, which appears to host malware - software that can hurt your computer or otherwise operate without your consent. Just visiting a site that contains malware can infect your computer.

Anyone know what's up with that?