Great idea, been thinking about the same thing myself recently, though I don't have the AI/statistical know-how to implement it.

I think this functionality should be built into the submission logic so that every node that is created has to pass through it. It should go between the "preview" and the "stubmit" stages. Before actually submitting a node the user should be presented with a list of possible solution threads.

Hello Dave. I read your submission. Have you checked these threads for information regarding ActiveState PPM Packages? I'm sorry if this isn't what you want, please continue your submission if I have not helped you.

Installing packages on ActiveState Perl.
Installing packages in windows98.
ActiveState Perl PPM HELP?!?!


This could be implemented (simply) by building a keyword list from the submission, running it through the existing search engine, and returning the results on the submit page. Advanced users could have a recommendations flag on their home node to turn it off. I don't know how many hoops submissions jump through currently, but this one would definitly add some overhead to node creation. Recommendations could be limited to initial thread posts and skipped for replies.

I also think CODE tags should be included, or at least an option in the search. There are many responses that are great answers to questions, but the entire message is a CODE block. Especially if I'm asking a question about usage of a module.

Bits: It should definitely include SOPW in the search. I know I spend most of my PM time there. I think returning threads instead of nodes would make searching less daunting to users. A multiple choice keyword selection from a list could help the search, nodes with user selected keywords would have a heigher weight than those without. Nodes written by high ranking users should be returned before lower ranked users', and you might as well roll the node ranking in with that too.