Integration with Node Auto Term [NAT] and Glossary

Looking for feedback on my wake-up-in-the-middle-of-night brainstorm (sad but true).

In investigating using Taxonomy for navigation, I came across Node Auto Term, and it seems like a great concept. At first I thought it might be an alternative to NH, but now I'm thinking they'd be very complementary.

I plan for my site to have thousands of visitor-contributed pages, lots of different doc types and lots of terms attached to each node, many different classification matrices, each factor its own vocabulary. Therefore IMO not really suitable to be fully managed by NH, rather too high-maintenance for my taste.

So I just want to use NH to manage the "backbone spine" of "Topic" nodes, creating the site's structure and coordinating paths with menu navigation/breadcrumbs.

I won't try to bring all the actual visitor-contributed content into the NH hierarchy, just use taxonomy and Views to bring the myriad content nodes together by term under the NH-managed Topic nodes.

And adding Glossary to the mix seems like, like, well words fail me, I'm inspired.

So here's my idea, hoping for some sort of feedback, especially on any anticipated compatibility issues:

• Activate NH, NAT, Pathauto and Glossary on the same content type (e.g. "GlossaryTerm").
• Creating a GT node causes NAT to automatically creates a same-name-as-title term in a ContentTopic vocabulary, which will be used by the community to tag all their contributed content
• This topic node is not tagged with this term - it's a parent of the nodes in its same-name term, not a peer
• It is tagged with the Glossary vocabulary and the Glossary module requires a "dedicated" vocabulary, so only one of these nodes are tagged with each of the Glossary terms. Result:
• Glossary filters all the content nodes so that the first use of a given glossary entry in the content will automatically link to the topic node.
• Small downside: two parallel vocabularies, but remember the "main" one is automatically generated by NAT when the GT node is created.
• The GT nodes will contain an "extended definition/general overview" of that topic, with support for synonyms (different content words going to the same topic node) and related terms generating See also: links to other GT/topic nodes.
• NAT integrates with Views to show all of the content nodes tagged with a term classified and sorted under the topic node.
• Therefore NH will allow the editor to efficiently maintain the "primary topic hierarchy" for structure and navigation, much more effectively IMO than using taxonomy for navigation, while
• NAT will automatically "bring along" all the community content tagged with the same-name ContentTopic terms within that structure.

This of course is really just managing one aspect of the content, but the NH menu system should enormously help the visitor is navigate through the Glossary hierarchy. Other parts of the site can use other navigation/structure options combined with Views to slice and dice the content via the other classification factors, possibly still using a hierarchical taxonomy to present alternative paths through the content.

Whew, if you've waded through all of this thanks for your time.

I hope I've made my ideas understandable, and any feedback would be greatly appreciated.