= Proposal number : Proposal title = || '''Date''' || 2008/08/13 || || '''Contact(s)''' || fxprunayre || || '''Last edited''' || [[Timestamp]] || || '''Status''' || draft || || '''Assigned to release''' || to be determined || || '''Resources''' || resource available || == Overview == « Narrow you search » module / improve the summary search code. It could allow output as list of keywords with frequency and optionnaly tagcloud view (http://en.wikipedia.org/wiki/Tag_cloud). === Proposal Type === * '''Type''': GUI Change, LuceneSearcher * '''App''': !GeoNetwork * '''Module''': Search Interface === Links === * '''Documents''': * example http://www.geocatalogue.fr/ * '''Email discussions''': * '''Other wiki discussions''': === Voting History === * Vote proposed by X on Y, result was +/-n (m non-voting members). ---- == Motivations == Extends the summary section of a lucene search. This use only the index in order to compute statistics over a search. Statistics are produced over the full list of result (not only the one in the current page), it could be the entire metadata catalogue. There's no access to the database for this operation. == Proposal == Current implementation produce (see xml.search service) : {{{ }}} Configuration : list of search criteria which could be agregate Agregation type and criteria type: * text (e.g. keyword) * numérique (e.g scale) * date (niveau d'agrégation : semaine, mois, année) (e.g last update date) Changes : * LuceneSearcher.makeSummary() * Add an option to search services to only produce the summary (like the fast option but really fast / only summary) * Add config file to define * criteria : MUST be in the index * criteria type : String|Number|Date * agregation type : * String : count * Number : count|equalInterval + classe ?| quantil + classe * Date : count|annualy|monthly|daily * sort option (count|name) === Backwards Compatibility Issues === == Risks == == Participants == * List of participants and role (if necessary) in current GIP