Looks like these are pretty close, can you give a rundown of the differences in functionality between NT and NAT other than the obvious term<->node cause/effect difference?

For example, does NT assign the created node to the term (NAT doesn't, it considers the same-name node to be a parent not a peer of the nodes in the term)

Also, when you say you maintain a "hierarchy" on the nodes, do you mean via coordinated menu and path aliases like Node Hierarchy module? If not, then how does the hierarchy manifest, how is it useful/visible for creating structure?

Also if not, possibly have a look at NH and let's talk about changing this to a feature request, because maintaining a set of hierarchical nodes where their menu tree and breadcrumbs, the URL hierarchy AND the parallel taxonomy are all kept in sync would be absolutely wonderful!

Last question - is there the ability to display all other node types tagged with the term as children of the same-name node via Views integration (NAT and I think NH both do).

Along with a readme, a detailed descriptive doc in the Handbook would be great too. . .

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Status: Active » Fixed

Trying to answer some of the questions here:

NAT creates a term our of a node, and not backwards, and does not have the hierarchy support, interface is different as well. Last versions of this module also creates terms out of a node.

About NH, I am not familiar with it, but it looks like it works on the content side independently of the taxonomy.

This module is mostly based on the taxonomy part, not on the content (nodes) parth. When I say it supports hierarchy what I mean is that it tries to emulate the taxonomy tree hierarchy. How does that work? Let say you have a taxonomy tree like this:

Operating System (tid: 1)
|-- LInux (tid: 2)
|-- MAC (tid:3 )
`- Windows (tid: 4)

It will try to keep that hierarchy in the nodes by selecting the parent term as the taxonomy term for the node associated to a specific term.

To be clear, you'll have the following nodes created with the following terms of the mapped vocabulary automatically assigned:

Operating System (taxonomy term: NONE)
Linux (taxonomy term: Operating System - tid: 1)
MAC (taxonomy term: Operating System - tid: 1)
Windows (taxonomy term: Operating Sysmem - tid: 1)

With this, you can eventually create vocabulary listings using nodes instead of terms.

About views integration, I can think there are things you can done. The module does not provide Views support directly. Something that would be useful is to provide something to views to build a proper query, but there are ways you could do this on your own.

For instance, to do what you asked, you could have a Views configured to display certain nodes with certain term and have the term name as an argument. Then using the PHP argument configuration, you could extract the term name from the node being viewed (assuming you are displaying the views as a block when viewing a page) and then feed the view with that name and that would do it.

About documentation, well, is always something put behind because of time constrains. If you want to get familiar enough with the module and write a proper documentation out of it and improve the README if that's necessary, please feel free to do so.

Hope any of this helps.
Ariel.=

HansBKK’s picture

HansBKK commented

Thanks a lot Ariel, and if I do end up using this module past testing stage I'll try to help out with some intro docs for others considering using it. Feel free of course to use text from this issue in the meantime, or perhaps just point to it from the project page.

Just to make sure I've understood your answers, I'm going to re-phrase some points, please let me know if I've misunderstood.

Both TN and NAT help automate the creation of matching (same-name) node-term pairs. TN does this by creating the node automatically when the term is created, while NAT creates the term automatically when the node is created.

Neither of them actually assigns the term to the same-name node, considering the node to be a "parent" of the nodes to be tagged with that term, not a peer.
--------
Now for some more question, I'm sorry I'm coming from a noob point of view here :)

It also handles hierarchy by automatically assigning the vocabulary to the set content type and maintaining the hierarchy on the node as well.

I see how you automatically build the hierarchy of the TERMS in the vocabulary, and the TERMS of the parent are assigned to the nodes created. But does TN create any relationship between the parent NODES and its children?

To use your example, here are some possible Operating Systems "pages": A the full-node display of the OS node, or B the tax-term teaser display of pages tagged with the OS term, or C a View.

Q1 Is there any functionality in your module that will show a connection between the OS node and the Mac/Linux/Windows nodes in A or B?

Q2 If I want to build a page (probably using Views) that shows the OS node at the top and (a list/table or teasers or full-nodes) of the Mac/Linux/Windows nodes, would I have to figure out how to do this with some PHP code? (I believe NAT has this built-in, and I know NH does)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.