No Documentation on Full Node Glossary Entries in all of Drupal-land

Do you want a new content-type called 'glossary entry' so that you can manually add new nodes i.e. pages to a glossary?
This is not what this module provides - this provides an automatically created glossary of terms from a vocabulary.

If you want to create your own glossary of nodes, create a new content type (Administer -> Content Management -> Content Types) called 'glossary', and then use the CCK module to extend that node type with any further fields you want to capture if you want more than just 'title' and 'body'.
Then use the Views module to create a summary page of all your 'Glossary' pages into a list.

Also keep in mind that a taxonomy term's description (MySql: longtext) may contain as much explanation as you want, including HTML. However, Glossary may not display it all.

Ahh, I figured it out - DUH! Actually the information on how to do it is sitting there staring us all in the face...

Glossary runs on a taxonomy vocabulary and its terms. That means that there is a "Glossary" vocabulary to be used on the node types you have it set for. Hopefully one of those types is either "page" or "story."

This had me confused for a while: You should not assign these terms to the nodes that will have the glossary flagged. Those who have done so have noticed that clicking on the indicator takes them to a "taxonomy/term" page for that term - listing all such tagged content.

The only content that should be tagged with the actual glossary terms are the "full node" descriptions. DUH!!! That way clicking on the link takes you to that full-node description. I would assume that the vast majority of the time there will be only one node assigned with those terms.

Now, "Detailed description" makes perfect sense!

Of course! That makes a lot of sense.... interestingly, I've actually been using this module in a completely different way from it was intended, but with equally effective results for my needs.
I apply the glossary filter to my blog posts using the main vocabulary which I use to categorise all content in my site (not specifically a 'glossary' vocabulary) - that way if I mention 'monkeys' in a blog post (which is a term in my vocabulary), clicking on it goes to the taxonomy/term page for 'monkey'.
I then use taxonomy_redirect + views to theme how I present all the other content in my site about monkeys.

Have I actually been abusing glossary all this time? Should I have used another module?! I guess there are no 'right' answers - this has worked for me very nicely, so even though I never actually use the glossary alphabar presentation page, I'm happy!

I'm not sure how you're doing that unless taxonomy_redirect is doing it. It's certainly an interesting application and one worth looking into.

I guess I'm confused by both of these methods...

Nancy, you say :

> The only content that should be tagged with the actual glossary terms are the "full node" descriptions. DUH!!! That way clicking on the link takes you to that full-node description. I would assume that the vast majority of the time there will be only one node assigned with those terms.

How are you doing this? Are you using CCK and applying the glossary term there?

Tanoshimi, you say you are redirecting the linked glossary term...How are you doing this? All of my glossary terms point to the same page -- the glossary listing page.

Any clarification would be greatly appreciated as I feel one of these methods will help me create a node based glossary.

Thanks!
Mike

Mike,

I create a "story" node that describes the term and tag it with that Glossary term. Then Glossary sees that there is a node for that term and generates a 'taxonomy/term/xxx' link to view it. Hopefully I'll have this on my live site soon and you can see it working. Hopefully I'll have the better documentation finished soon as well.

Tanoshimi is using the Taxonomy Redirect module, which intercepts the 'taxonomy/term/xxx' links and redirects them elsewhere. At the moment I can only guess that he's redirecting it to a search for the term. Pretty neat idea.

Exactly - my blog entry nodes have the glossary filter applied, so when I write a blog entry which contains any of the terms in my vocabulary, these are automatically highlighted and turned into links which point to that term's entry in the standard taxonomy term view page taxonomy/term/xxx.
By default, this is a teaser list view which shows all nodes which have been tagged with that term on your site. But if you use the taxonomy_redirect module as well, you can repoint these links to go to a view, passing the term ID as an argument, and then you can customise the view any way you want.

I'm in the middle of writing up a quick 'How To:' document to add to the handbook on how to set this up (although I've pretty much described it above!)

One more thing to note is that the behaviour of the link which the glossary filter creates can sometimes differ depending on how your vocabulary is set up... the following is an extract taken from the _glossary_filter_process function, which defines the $linkto variable which is the url where the highlighted glossary term will point to:

    foreach ($terms as $term) {
      $term_title = $term->name .': '. strip_tags($term->description);
      if ($term->nodes > 0) {
        $linkto = "taxonomy/term/$term->tid";
        $hash = NULL;
      }
      elseif (count($vids) > 1) {
        $linkto = 'glossary/'. $term->vid;
        $hash = NULL;
      }
      else {
        $linkto = 'glossary/term/'. $term->tid;
        $hash = NULL;
      }

So, for each term in the node body, if there is at least one node on your site which has been tagged with that term (if ($term->nodes > 0) then the link will go to the taxonomy/term/XXX page for that term ID.
If there are no nodes tagged with that term, and you have more than one vocabulary (count($vids) > 1), it will go to /glossary/vid.
And if you only have one vocabulary, but no nodes with that term it goes to /glossary/term/XXX.

I don't know if that helps explain any more!

#8: Great. Let me know when you've written it so I can link to it from my documentation.

#9: Yes. First, the node counting code has changed just a bit. Also, in response to another issue, I'm thinking about removing the vid count check so you'll only get one entry, no matter how many vocabularies are being used.

But what is the point of creating a glossary, and going to all the trouble to define the terms, if you can't apply those terms to arbitrary nodes?

That seems extremely limiting.

@shunting:

full ack

Greetings, -asb