Content from taxonomy descriptions
| Project: | Taxonomy Node |
| Version: | 5.x-1.5 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi,
when I discovered the "Taxonomy Node" module, it seemed to solve lots of long-standing deficiencies of Drupal. Especially it seems to offer lots of potential to enrich Drupal core's taxonomy,
- starting with basics like adding images and other multimedia content to a taxonomy term (e.g. a logo for a company or organization, or a typical sound for an animal classified with Drupal's taxonomy),
- going further by becoming able to tag "terms" (respectively taxonomy nodes) with other terms, and extending the associated nodes with CCK fields, and harvesting the gathered data through Views, and
- starting to enable some kind of "semantic taxonomy", e.g. where a vocabulary for locative information can become integrated with Location and GMap modules (e.g. the taxonomy node for the term "Europe > Germany > Berlin" gets a map with a marker on "Berlin"), or where a vocabulary for temporal information gets associated nodes, listing backlinks to the terms (e.g. the term "1973" has an associated node that lists articles tagged with this term by utilizing the "node referrer" module).
(I'd love to hear usage scenarios from other users of this module!)
However, after playing around for a while with the module, I became a bit irritated - but maybe I've not yet configured it correctly ("Map Node Operations" at admin/settings/taxonomynode is disabled since I couldn't figure out what this does exactly; it seems to work similar like the "NAT" module and work on vocabularies, not on nodes). Some observations I made so far:
- Firstly, taxonomy nodes for an existing term are "empty", especially they seem not to be tagged with the associated term. That means e.g., that by clicking on the term "Drupal modules" I'm not getting the taxonomy node "Drupal modules" in the taxonomy listing. How do I get from an taxonomy term to the associated taxonomy node (when node isn't tagged with tern)? How do I get from an taxonomy node to the taxonomy term (with which it isn't being tagged)? Either I don't understand yet how this module is supposed to be used, or this behaviour does not make much sense. Could we get bidirectional connections from the taxonomy node to the taxonomy term that are being displayable to the site's users? (I'd even love to see something like taxonomy nodes to fully override Drupal core's taxonomy, but I think this is by far out of the scope of this module?)
- Secondly, taxonomy nodes for an existing term seem to have no content in the node's body, even if the taxonomy term included descriptions already. All I'm getting is a message on the edit term page, saying something like: "You can edit the associated node Fédération Cynologique Internationale as well". Again, either I don't understand yet how this module is supposed to be used, or this behaviour does not make much sense. We have thousands of terms with descriptions; would we have to move the content manually from the term's descriptions to the associated taxonomy node bodies, without any possibilty to sychronize the content from term's descriptions with the associated node's bodies? Could we get some way to synchronize and/or move the content from term descriptions into taxonomy nodes (and, if possible, a way back, from node bodies to taxonomy descriptions)?
- I haven't yet tested this, but what happenes to taxonomy nodes when uninstalling the "taxonomy node" module? The worst case scenario is that thousands of manually edited taxonomy nodes get deleted. Also, for the everiday usage: Could we get an option to prevent nodes from being deleted automatically through the taxonomy node module?
Again, I'm using this module only for a few hours on one site's vocabulary, so possibly I haven't yet understood and/or configured it correctly - for that I'd like to apologize beforehand. However, if the mentioned features are indeed impossible at the moment, I'd love to hear some comments about them - could you imagine to implement them, at least partally, or is this more a "provided as is" kind of module?
Thanks for this wonderful module & greetings, -asb
#1
Hi,
Any update about above great questions please?
Thanks a lot in advance for your reply!
greetings,
Martijn
#2
Hi,
I am going to try to answer some of these questions, quite a few things to address. Sorry I took a while to answer, the recent comment remind me to do so.
Map nodes operations is a way to tell the module to sync what you did on the node to the term. (e.g. if you delete the node, the term gets deleted).
Please read #344039: Taxonomy Node: Drupal 6 version!, in particular comment #20 about why the node created is not associated with the term, at least so far.
Once you have configured the association, you should see a link to the associated node of a term on the term's edit screen, and, you should see a link to the associated term from the node's edit screen.
Here you have answered a little bit of the previous question, about the term descriptions, it might be a new feature to implement. And I understand it is related to not having the term set in the node itself. If you are a developer, there's a function you could use in your theme (like when theming the node) to get the associated term from a node and display whatever info you want there. The only thing I am thinking about synchronizing the term descriptions with the node body is that you might want to put in the node body whatever you want, and that might not be the term description.
If you uninstall the taxonomynode module nothing would happen really. Actually there's not an uninstall function at all, and this remains me that there should be one, but it will just wipe out the taxonomynode table, it won't do anything about the nodes.
And about preventing the nodes to be deleted from the taxonomy node module, that might be a new feature as well.
Can you added two separate feature requests for:
- uninstall function
- prevention of node being deleted
We can follow up discussion of those issues there and focus on the description discussion here.
Thanks,
a.=
#3