Garamond.jl icon indicating copy to clipboard operation
Garamond.jl copied to clipboard

Extend base input parser

Open zgornel opened this issue 6 years ago • 2 comments

A query language should be defined and developed. Should word at query term level, with boolean operators. Main operations should implement logical AND, OR (at this point implicitandNOT` (i.e. negation)

zgornel avatar Apr 03 '19 09:04 zgornel

These should also work across multiple input parsers. For example, I might want to search for "coupon" with the base text parser, AND'd with a search for results within a given geographic area (using a latitude+longitude+radius parser), to determine which local businesses have coupons available in my city.

jpsamaroo avatar Nov 23 '20 00:11 jpsamaroo

Indeed. The base input parser shoul dbe viewd as a "last-stage parser" that parses the query into a query data structure that is sent to the search methods. I'm envisioning a stacked parser approach here where parsers call the base one as one can build easily complex selection from the db. So a flow would be "natural query --> (NLP parser) --> select-like query --> (Base input parser)"

zgornel avatar Nov 23 '20 08:11 zgornel