As text retrieval geeks, we hate manual tagging :-) We want you to analyze the content (might I suggest using Lucene and Mahout) and categorize it for us. :-) But jokes aside, a major category of tags would be "(text) analysis" or "tokenization" or "term processing for indexing" -- all that stuff related to Analysis and all the language specific stuff that is needed before something is put in the index.
And then there are all the classes that represent the information from the index, they are used in indexing (putting in) and searching (taking out), but they really are index related, not specifically indexing or searching. Oh the problems coming up with a good set of tags... Note, I added a handful of tags anyway. -Paul > -----Original Message----- > From: Seth Rosen [mailto:s...@architexa.com] > We were wondering if you guys could do us a quick favor. Would you take > 5-minutes, go to the site, and > tag code as being performance-sensitive, query-related, indexing, > needs-refactoring, or something similar. > We believe that with people tagging the Lucene codebase - it will become an > awesome community > resource. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
