David, Thanks for creating this great module. It is almost exactly what I need. In conjunction with the Glossary module, it rocks! (Well it will with a small change). For the glossary module to work with a term, the Description field for the term needs some content.

Could you modify your module to put something in the description field when it creates a new term? A possibility for filling the Description field could be to string together any field labels and field contents for the tagnode; or if the tagnode contains a field called Description just copy that in.

Using the Tagnode and Glossary modules together will add another level of dynamic content. For example, if (from your example) a tagnode is Artist on a music website, then with the Glossary combinde, whenever the artist's name is written in a story it is automatically turned into a link to the artist info.

Warm regards,
Chris

Comments

dado’s picture

dado commented

Chris,
My apologies at getting back to you so late. I thought I was getting all issues email to me but apparently only bugs.

I am unfamiliar w/ the Glossary module but would be happy to try to integrate. If you are still interested please post here, along with a few more details. Specifically-
you seek this for Drupal 4.6 or would 4.7 suffice?
what algorithm do you recommend?
if node contains field named t("description") then populate term's description field with this, otherwise populate the term's description field with the node's title.

David

barc-1’s picture

barc-1 commented

Hello David. Many thanks for replying. If you could add this functionality it would be fantastic. I have deceided to wait a little before sending my Drupal site live so I only need it for Drupal 4.7. In terms of how it should populate the Term Description field, I think it would be good to do as you suggested.
Warm regards,
Chris

dado’s picture

dado commented

Chris,
I just committed a change to HEAD CVS version of Tagnode (which is for Drupal 4.7).

Now tagnode (4.7) does this:
When inserting or updating a tagnode, it populates the term's description field with the node's teaser (except with tags stripped out). If the stripped teaser is blank then it instead populates the term's description with the node's title (so term's descr will = the term's name in this latter case).

I opted to use the teaser since it would be difficult to get any flexinode "description" field in there, and it works for all cases. You then have control what gets put in the term description. Drawback: Every term description now has "description:" at the beginning. Might be able to remove such from teaser w/ custom theme - I dunno.

Please let me know if this is rational. Please suggest any alternative approach you can think of. E.g. should I prepent the term's description with its name also?

Please also let me know exactly how you are using this & what is the benefit. I migth want to use it myself and would want to document if it proves useful.

Thanks,
David

dado’s picture

dado commented
Status: Active » Fixed
barc-1’s picture

barc-1 commented

Thanks David. Sounds great to me! Yes, and I think using the Teaser is the best solution.

The way I have been developing my site (still on a test server at home) to use this is as follows...

I maintain a community network website that is for all organisations involved with refugees in the Brisbane area. This site has various categorised announcements, events etc listed and they are all entered by volunteers and community workers from the different organisations in the sector. There are about 60 different organisations listed on the site.

Whenever a user creates a new item on the website, if it contains the name of one of these organisations, I want an automatic link created through to more information about the organisation. The site users tend to only do the minimum in creating items on the site so this needs to be automatic or it won't happen.

I found that in Drupal this could happen by using the Tagnode module and the Glossary module together. I use Tagnode to automatically create each organisation as a Tagnode when it is entered into Drupal. I use Glossary to automatically link relevant text (i.e. Tagnode Title) within any node to the relevant Tagnode. Both use a vocabulary of terms to do their thing. If you set them each to use the same vocabulary then they work together.

1. Set up a new Flexinode type for Organisations. This contains contact details and a summary of the work of the organisation.
2. Set up a vocabulary "Organisations". You can LEAVE EMPTY all the checkboxes of the node types to which the tagnode should be taggable. (You will not be manually associating tagees and tagnodes. Glossary will do it automatically).
3. Link the Tagnode's node type and vocabulary as per standard Tagnode instructions.

4. Set up the Glossary module as per standard instructions. Set the vocabulary created above ("Oganisations") to be the one to use in Admin -> Input Formats -> Configure -> Configure.
5. Glossary terms become links with mouseover description wherever they are found within a node (of the permitted types) on the website. A clickthrough will take you to the term description in the glossary index. Also, if the term has any nodes associated with it, then those nodes can be displayed also (or instead of the description). So, it would be good if, when a Tagnode is created that a nodeterm record is also created. For my situation it is very easy for me to do this manually.

* Note that Glossary will not link a term where the description field in the taxonomy term is empty. (This is what this thread has been all about. Tagnode 4.6 leaves the description field empty so use Tagnode 4.7).

I hope this is understandable.

Warm regards,
Chris

dado’s picture

dado commented
Version: 4.6.x-1.x-dev » 4.7.x-1.x-dev

Chris,
Impressive work. Thanks for the documentation on this. I will add
to the documentation for tagnode. If you remember, please post here when you go live so we can check it out in action.
Thanks
David

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)