topic-linking for nodes

We have a Q&A section which is topicalized. We have a huge Seekers of Perl Wisdom which is not.

It may add to the strength of the Q&A section if it had links to the relevant nodes in Seekers

It will be easier to look through Seekers for related questions if one can browse by topic

The reason this idea struck me is that I saw the post Baseball line up (best rotation) and saw it as a post on Constraint Satisfaction / Operations Theory which is the same as my recent post, whose title is quite topical, but not specific enough: Constraint Satisfaction Problem

Comment on topic-linking for nodes

Replies are listed 'Best First'.
Re: topic-linking for nodes by Masem (Monsignor) on May 17, 2001 at 23:06 UTC
Again, I'll say it: Keywords, Keywords, Keywords The system is practically in place; it needs only two things; the ability for editing and deleting keywords by the node author and gods, and a way to search on the keyword. Dr. Michael K. Neylon - mneylon-pm@masemware.com \|\| "You've left the lens cap of your mind on again, Pinky" - The Brain	[reply]
Re: Re: topic-linking for nodes by vroom (His Eminence) on May 17, 2001 at 23:40 UTC
Good idea... now editors and node authors should be able to delete keywords from nodes... now just to build something that actually uses the keywords :) vroom \| Tim Vroom \| vroom@cs.hope.edu	[reply]
Re: topic-linking for nodes by aardvark (Pilgrim) on May 18, 2001 at 17:00 UTC
We are having a similar metadata problem at work. We are hoping to solve it by requiring users to categorize their content. We are providing them with a controlled vocabulary list and asking them to enter up to three subject codes. The goal is to have these categories drive a search engine and a browse by topic feature. Of course, there is the problem of not being sure if they picked the correct subject codes. There doesn't seem to be any way to guarantee this without human intervention. Also developing a controlled vocabulary list that meets every person's needs is hard as hell. One solution is to have global metadata, data that should be collected about every file(node) and local metadata, info that is specific to a section or content type. This allows us to fine tune our metadata without putting a huge burden on the user. Having global and local metadata also cuts down on the size of any controlled vocabulary list. The sections of the Q&A section could be a good start for subject codes(global metadata). The goal of browsing by topic is a good one and it would compliment the Super Search nicely. The work of the Dublin Core and the W3C (RDF) could provide some good ideas and blueprints for this topic. Get Strong Together!!	[reply]