The website documentation for the Glosssary module states in part:
The vocabulary need not be associated with any modules, though you can attach detailed description to terms by adding nodes to the terms, so it might be a good idea to associate the vocabulary with the "story" module.
This sentence raises at least the following questions for a Drupal/Glossary newbie:
- What is meant by "adding nodes to the terms?"
- What advantages/disadvantages are presented by doing so?
- What steps must a user take to add nodes to terms?
- What other uses might a user make of nodes added to terms?
- How might a user access relevant data to make other use of nodes added to terms?
Comments
Comment #1
nancydru"not be associated with any modules" should read: "not be associated with any content type"
1. Tagging a node with that term.
2. If a node is tagged with a term, then it is available as a "detailed description" for that term and will be available for that term on the Glossary page.
3. Make the vocabulary available for that content type. Add that term to the node.
4. I'm not sure, perhaps other users of Glossary can help here.
5. "taxonomy/term/xxx" and the "search for term" link. If you choose not to use the "Show detailed descriptions on the Glossary page" the module will create the "taxonomy/term/xxx" link for "Detailed description of..."
Comment #2
Marbux commentedI'm wondering if there is some relevant functionality that was removed from the module between 4.7x and 5.x. This page written by Stephen Winters describes a method to achieve multi-page glossary descriptions by attaching nodes to terms, but it was written for the Drupal 4.7x-compatible Glossary module. The relevant text on that never-finished page:
Cf., note that the page has fairly detailed instructions for the glossary module that might be at least partially recycled in revised documentation.
Comment #3
nancydruhttp://drupal.org/node/224377
AFAIK, it never actually worked quite that way. The link that now reads "Detailed description for xxx" does (well, now can) do a "taxonomy/term/xxx". I'm not aware of making any changes to that little piece of code. But I have made so many changes since Moshe let me update this module that it is possible that there was a change.
Certainly the entire settings process has changed dramatically since I started. I find that second excerpt to be rather unclear.
If someone had more experience with this module on 4.x, and is willing to provide a history lesson, I'm willing to read it.
Comment #4
Marbux commentedI had time to play a bit more and am slowly beginning to comprehend the functionality here. You can attain multiple "detailed descriptions," i.e., attach multiple nodes to a term, by tagging multiple nodes with the term. However, when you do so, in content nodes the term and its definition are no longer linked from an occurrence of the term in the text. Instead, when you click on a term link in the text, you get a page composed of the titles and teasers from all nodes tagged with the term. In other words, you get Drupal taxonomy behavior. One criticism here is that "attach" is probably not the right term to use for this functionality. A better term would be "associate" or more simply, just "link."
Another way of viewing the functionality is to observe that you must not use a glossary vocabulary as a taxonomy tag on a node unless you desire that: [i] the term/definition no longer be linked from its occurrences in content nodes; and [ii] content nodes be identified and linked as "detailed description" from a term/definition pair. Treating glossary entries as normal taxonomy tags carries a price. If you do not desire those results, then crate a new, non-Glossary vocabulary using the same terms/tag names or as many of them as you desire.
The "associated nodes" Glossary feature assumes that only nodes which are in fact "detailed descriptions" of defined terms will be tagged with the term.
I will work this information into the draft documentation.
Conceivable enhancements
Playing with the feature brings to mind the following conceivable enhancements for Glossary:
Add Glossary terms to another vocabulary. Assuming that a user wishes to use the detailed description feature for its intended purpose but also wishes to use the Glossary terms as or as part of a separate taxonomy for tagging node purposes, an ability to automagically have new Glossary terms added to a second vocabulary would be a big plus. This would basically be a one-way synchronization, in case a user wanted additional terms in the second vocabulary. Rationale: It's a PITA to keep large dual vocabularies synchronized manually.
This might be better done as a separate more general purpose module or as an add-on to the Taxonomy module, using an "add vocabulary A to vocabulary B synchronization tool" approach, with "synchronize 2-way" and "synchronize automagically upon new entry options."
Display term and definition with associated nodes.
This might be a sub-option for the detailed descriptions feature. This would work like the present functionality, except that when a site visitor clicks on a vocabulary term in a content node, the resulting page displays the term/description, followed by the display of associated node titles and teasers. In this scenario, the link name on the glossary term/definition would change from "detailed description" to something like "term also discussed in *these nodes,*" where *these nodes* is the link to display the content described in this list item.Rationale: This change would enable Glossary entries to be used both as a tagging taxonomy and as a glossary without maintaining a duplicate vocabulary for tagging purposes. Note, however, that should this concept be developed, pagination of output would be necessary on many sites because of the number of nodes that are tagged with a single term. Of the two approaches suggested in this post, I would personally choose this one.
Comment #5
nancydruYou're right and I think this should change. When I added the capability to show the teasers directly in the Glossary or term page, I just didn't think about that. IMHO, we should now only show a link as it would be if there were no nodes flagged with the term and allow the overview/term page to show the teasers, at least when that option is chosen. I think this is sort of what you mean in your second option.
I have never liked the terminology "Detailed description;" it was there when I started maintaining this module. I'm certainly open to alternatives, although we need to be conscious of current users (as in, maybe making the text a setting).
Your idea of a parallel vocabulary is an interesting one, but probably should not be part of Glossary. I wonder how much need there is for this and how one would describe it to get people interested. I don't think the code would be all that difficult - mostly hook_taxonomy. Indeed, probably 50% of that code is already in Glossary.
Comment #6
nancydruhttp://drupal.org/node/242687