X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=source%2Fmircoders%2Fsearch%2FSearchTerm.java;h=af2de1cc240508380f1af320a88df753f9ba9107;hb=2d3a3231809a1af4e373c3fd13902eeee26728c9;hp=6e7bdca9a431eb2642ea21a14db19bcf3a6dabac;hpb=02bd273fe5a10b719ad479e6073fe515d5283eff;p=mir.git diff --git a/source/mircoders/search/SearchTerm.java b/source/mircoders/search/SearchTerm.java index 6e7bdca9..af2de1cc 100755 --- a/source/mircoders/search/SearchTerm.java +++ b/source/mircoders/search/SearchTerm.java @@ -38,7 +38,35 @@ import mir.entity.Entity; import org.apache.lucene.document.Document; +/** + * The SearchTerm class attempts to encapsulate the relationships + * between: + * + * The basic idea is that how you index, query, and display a + * particular field in a resource are all intimately related, possibly + * more so than how you index two different fields of the same + * resource. + * + *

Instances of classes implementing SearchTerm are created when a Mir + * content entity is indexed by the IndexingProducerNode Class. The + * index method of each class is called in turn to add a bit of + * information to the Lucene documents which will be added to the + * index after it is created and all its fields specified. Instances + * of the same classes are created by ServletModuleOpenIndy so that it + * can construct a query to match against the lucene index, here the + * makeTerm methods are called in turn to pick out the parameter they + * want from the request and then construct the appropriate fragment + * of lucene query, which are ultimately concatenated together. These + * classes are also used to return appropriate template models + * representing any hits to be displayed as a result of processing the + * query.

+ */ abstract public class SearchTerm { protected String partOfEntity; protected String paramName;