taxonomy

Taxonomy is a great term for advanced categorization of content through parent and child relationships. I get it.

When editing a vocabulary, you can structure it as parent terms and children terms.

What is seriously missing is a way to enforce these relationships at node creation, especially if you need to be able to add child terms at node creation.

If you can pick a parent menu item at node creation, why can't you do the same with taxonomies?

Buenas compañeros! Es la primera vez que escribo,
Mi duda es sobre las taxonomias y vocabularios en Drupal 7.

Tengo 2 tipos de contenido que van usar categorias o vocabularios por lo que
cree los 2 vocabularios. Pero a la hora de agregar el campo en las opciones de
configuracion, no puedo cambiar el vocabulario
"Opciones del campo Categoria

Estas opciones se aplican al campo Categoria en todos los sitios en los que se use. Como el campo ya contiene datos, algunas opciones ya no se pueden cambiar."

We are trying to build an InfoBase using Drupal. I am trying to use Taxonomy. Currently I am simply defining a set of terms. I would love to know how any of you use it. What I really need is an ontology of businesses (not only terms, but also relationship between terms). Here are some questions:

1. Can you construct relationship between terms
2. Can you constrain these relationships based on some rules (RDF schema comes to mind)
3. Is there any relationships between taxonomy module and the RDF in the core?

Hey friends,

Is there any module or options to make site users to follow or unfollow the taxonomy terms and based on the following terms, I have to send notification if any new post posted on that particular terms. Im using drupal 6.20

Thanks,

Gobi :)

What tools/modules do you use for site Documentation? I'm looking at using Book module and the plethora of add-on modules to make it more usable for our site help docs. What we have right now is a mess of unrelated nodes and it's hard to find anything. The site topics will encompass a wide array of software our IT department supports and tutorials and videos to walk new users through various tasks.

What tools do you use?

Since I'm apparently known as the girl with all the questions... I'm gonna ask a question (isn't that what groups are for??:)

I have about 180 taxonomy terms set up for an e-commerce site (thanks to Taxonomy Manager that wasn't too painful), each term needs to have its own page and menu item with a grid of products that are tagged with that term. Rather than create 180 Views and 180 menu items, I'm hoping/praying there's an easier way to do this. Any suggestions?

I'm interested if anyone ever faced the situation when you need to delete all nodes under certain taxonomy term. I haven't found any reasonable solution for this yet. However, I need to massively delete near 10-20k nodes and each of them belongs to some taxonomy term. I think it can easily be done with minimal UI built upon standart Taxonomy module and Batch API.

Any ideas about this?

Hey guys,

I just enabled multiple terms for node creation and i just wanna display those mulitple terms as a tree sturctured in a block i tried with the following code

 if ( arg(0) == 'node' && is_numeric(arg(1)) ) {
 $node = node_load(arg(1));
 if (module_exists('taxonomy')) {
 $terms = taxonomy_link('taxonomy terms', $node);
 print theme('links', $terms, array('class' => 'node-terms'));
} else {
  print 'No associated categories.';
 }
 }

But no luck its just displaying all terms, But i have to display like below

 - parent term1 

How did you guys organize your taxonomy for your real estate site?
I'm looking at it and trying to figure out the best approach...

The "parent term" property on a taxonomy term is a unique, non-field-api, non-transferrable relation that has not been upgraded to Field API. This GSoC idea does not propose to replace this in core as the short term goal, because a transitive relationship field can exist side-by-side with the current "parent term" field and the "parent term" field can be drupal_alter'ed out of existence. However, if this project succeeds, it would be developed further to include in core.