Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#3 NOT-anywhere vs NOT-near

open
nobody
General (18)
5
5 days ago
2004-10-07
mhaye
No

Currently, the NOT operator means "not anywhere"
when applied to a meta-data field, and "not near" when
applied to the full text.

Consider implementing a "not anywhere" for full text.
Not sure if this would be very useful -- should a
document with a match in chapter 12 be excluded
simply because a NOT term is in chapter 1?!?

Discussion

  • Kirk Hastings
    Kirk Hastings
    2005-02-11

    Logged In: YES
    user_id=1125214

    The more I talk to people about, the more it seems we should
    do this. Also it would be nice to support this in both
    binary [(love or life) not (work and death)] and unary [not
    (music and laughter)] forms.

     
  • mhaye
    mhaye
    2005-07-20

    Logged In: YES
    user_id=978215

    UPDATE: The default is now "not anywhere" for meta-data
    fields, and "not near" for the full text. We think these are
    sensible defaults, but if there is a valid use for the other options,
    we can consider implementing them:

    (1) Option to specify slop on a meta-data "NOT", essentially
    supporting a choice between "not anywhere" and "not near"

    (2) Option to specify infinite slop on text "NOT", again giving a
    choice.

    For now, we'll leave it as is.

     
  • mhaye
    mhaye
    2005-07-20

    • assigned_to: khasting --> nobody
     
  • mhaye
    mhaye
    2005-07-20

    • priority: 5 --> 1
     
  • Kirk Hastings
    Kirk Hastings
    2005-07-21

    Logged In: YES
    user_id=1125214

    I think we can close this one too...

     
  • mhaye
    mhaye
    2007-04-18

    • priority: 1 --> 5