search

ghbolivar / cropplanning

Automatically exported from code.google.com/p/cropplanning
0 stars 0 forks source link

Advanced Text Filtering #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 

By default, text filters are ANDed and apply to all filterable fields.

We should add the following features:

1. NOT and OR keywords

2. literal string matching via double quotes (lower priority)

3. targeted field matching via search term prefixes.  This is the real
cherry on top.  We could recognize the following prefixes (or any leading
substring of them) to limit specific terms to specific fields:
    crop: Crop Name
    variety: Variety Name
    plant: Planting Date
    transplant: TP Date
    harvest: Harvest Date
    flat: Flat Size
    field or location: Field or Location
    group: Groups
    notes: Notes
    otherreq: Other Requirements
    etc...

Original issue reported on code.google.com by cropplan...@gmail.com on 1 Apr 2008 at 2:54

GoogleCodeExporter commented 8 years ago 
I was thinking we use a colon (:) as the delimiter between prefix and search 
term.

Original comment by cropplan...@gmail.com on 1 Apr 2008 at 2:55

GoogleCodeExporter commented 8 years ago 
Oddly, this issue doesn't come up when I search for the word filter.

Original comment by cropplan...@gmail.com on 1 Apr 2008 at 2:57

GoogleCodeExporter commented 8 years ago 
A couple other things to search on:

keyword:
custom1..5:

The "custom1..5" will be interesting since we could in theory match on 
something as
simple as "c1:...".

Original comment by cropplan...@gmail.com on 3 Apr 2008 at 6:47

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 28 Sep 2008 at 8:13

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:44

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:52