> > > * Require SESAT help? > > > > > If someone could help us explain how enrichments work now, it would > > be nice.
Enrichments are now just normal search commands (ie SearchDataObjects) with the additional properties added in as fields. So in the templates where before you referenced the enrichment object (via the $enrichments list) now you must use datamodel.getSearch(..) Since you often want just the searchDataObjects in order sorted by the score they got you can use AbstractEnrichmentDirective. Check out the EnrichmentDirective subclasses we have under genericno.sesam.no for example implementations, but basically it is just to override the placementCorrect method to suit your needs. In fact i have already done this for you in genericse.sesam.se and it's been implemented in defaultSearch.vm & enrichmentsColumn.vm Also note that the command's attribute always-run used to be by default false where now it is true! You'll notice now in genericno.sesam.no that you often always-run="false" but not always-run="true". This change hasn't been done yet in genericse.sesam.se ~mck -- "When prosperity comes, do not use all of it." Confucius | Homepage - www.wever.org | Sesam Search Engine - www.sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
