nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] Commented: (NUTCH-294) Topic-maps of related searchwords
Date Tue, 06 Jun 2006 14:25:30 GMT
    [ ] 

Dawid Weiss commented on NUTCH-294:

Ehm, sorry I'm so late with this -- tons of work.

1) Stefan, if you can't get it working, speak up what is not working (exceptions? anything
else?). The only thing you need to do is enable the clustering plugin in your configuration
-- there should be a checkbox next to your search box, tick that and you should be able to
see clustered results when you perform a query.

2) Now, having said that, I don't think that's what you're after. Carrot2 performs clustering
of search results based solely on the information contained in snippets retrieved from documents
(in other words, there is NO ontology and NO predefined information, everything is constructed
dynamically). If you're looking for topic-maps then I guess you're after a certain type of
classification engine that could pick relevant categories and display them along with search
results. It's not what (the open source) Carrot2 does.

> Topic-maps of related searchwords
> ---------------------------------
>          Key: NUTCH-294
>          URL:
>      Project: Nutch
>         Type: New Feature

>   Components: searcher
>     Reporter: Stefan Neufeind

> Would it be possible to offer a user  "topic-maps"? It's when you search for something
and get topic-related words that might also be of interest for you. I wonder if that's somehow
possible with the ngram-index for "did you mean" (see separate feature-enhancement-bug for
this), but we'd need to have a relation between words (in what context do they occur).
> For the webfrontend usually trees are used  - which for some users offer quite impressive
eye-candy :-) E.g. see this advertisement by Novell where I've just seen a similar "topic-map"
as well:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message