[KinoSearch] Roadmap .30 and Scorers

[Justin DeVuyst]

Thanks guys but I'm already past that point.  What I've been
working on lately is attempting to aggregate data from CPAN
and other places into the index in a useful way.  But while
I'm doing this I'm asking myself if KS can handle very specific
queries.  Maybe something like "give me a highly rated (doc
boot based on cpanratings data) XML module that's cited as a
prereq at least a few times and has been uploaded in the past
2 years or has few bugs".  Of course KS would have an easier
time with "xml" but that's no fun:)

Clearly KinoSearch is a great choice for indexing all the big
text like POD, code, reviews, etc...  My latest thoughts lean
towards some sort of a mix between KS and a more standard DB
approach.  I'm not sure how the mixing would happen though.

Maybe its be better to keep them seperate.  KS for the simple
and more intelligent searching and the DB for more detailed
dumb searches.

The faceted searching sounds cool except for that one problem.

Any ideas?

Thanks,
jdv

Andrew Bramble wrote:
>>
>> also need CPAN::Mini, a POD extractor, etc.  I'n fact, for setting
>> up a
>> bare-bones CPAN search, extracting the desirable data from all those
>> archives is bigger problem up-front problem the fundamental KS
>> stuff.
>>
>
> I must agree , if you're even considering indexing CPAN with KS,
> CPAN::Mini
> and CPAN::Mini::Extract and the code to turn  these into say a
> document per
> '.pm' requires a heap of work with things like pod extractors , ppi
> etc.
> _______________________________________________
> KinoSearch mailing list
> KinoSearch at rectangular.com
> http://www.rectangular.com/mailman/listinfo/kinosearch
>



_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch