The search implementation is described below.
1) Search configuration --
* The search configuration must describe what fields are searchable on a content type. e.g. for a motion we should be able to specify e.g.
<searchins>
<searchin value="title" field="bu:shortName">Title</searchin>
<searchin value="body" field="bu:body">Body</searchin>
<searchin value="docno" field="bu:registryNumber">Doc No.</searchin>
</searchins>
which states that the title, body and docno are searchable.
value - is a short-identifier
field - is the specific element / or attribute that we want to search for
the text in the element is the literal shown to the user.
the information in field is used to build the search query on the document
dynamically. This is then eval-ed into a full-text search query.
2) Search behavior --
- Search results must look like listings
- Search results must be ordered based on the order-by parameter.
Logically the ordering should also be included in the search query eval, but
this can be implemented separately.
Original issue reported on code.google.com by ashok.ha...@gmail.com on 30 Nov 2011 at 2:54
Original issue reported on code.google.com by
ashok.ha...@gmail.comon 30 Nov 2011 at 2:54