BUG: Search conversion will not run

MJ. Smith
MJ. Smith Member, MVP Posts: 53,080 ✭✭✭✭✭
edited November 21 in English Forum

I enter the old syntax  <ln 93.1–93.388> NOT INTERSECTS {Section <SGNTSyntacticForce = prop. name>} 

it is converted to the new syntax louwNida:93.1–93.388 NOT INTERSECTS section:SGNTSyntacticForce:="proper name"

which does not produce results although each term by itself produces results - what is wrong with the use of NOT INTERSECTS? INTERSECTS works without the NOT.

Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

Tagged:

Comments

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,673 ✭✭✭

    That is to be expected when the intersection corresponds exactly to the smaller louwNida:93.1–93.388 set. So the overlap comes from the larger set with SGNTSyntacticForce:="proper name" NOT INTERSECTS louwNida:93.1–93.388.

    Dave
    ===

    Windows 11 & Android 13

  • Andrew Batishko
    Andrew Batishko Member, Logos Employee Posts: 5,362

    NOT INTERSECTS means that the search finds all the hits for the first term and removes the hits for the second term. That means that you want the term that is the superset to come first. You need this: section:SGNTSyntacticForce:="proper name" NOT INTERSECTS louwNida:93.1–93.388

    It's possible that you actually want something like the following, which returns all the things that are only represented in one of the tagging mechanisms (unneeded in this case, since SGNTSyntacticForce is purely a superset of louwNida (for proper names)): louwNida:93.1–93.388 OR section:SGNTSyntacticForce:="proper name" NOT INTERSECTS (louwNida:93.1–93.388 INTERSECTS section:SGNTSyntacticForce:="proper name")

    Andrew Batishko | Logos software developer

  • MJ. Smith
    MJ. Smith Member, MVP Posts: 53,080 ✭✭✭✭✭

    That is to be expected when the intersection corresponds exactly to the smaller louwNida:93.1–93.388 set. So the overlap comes from the larger set with SGNTSyntacticForce:="proper name" NOT INTERSECTS louwNida:93.1–93.388.

    See Visual Filter for Names - Logos Forums for my (your) original search argument.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,673 ✭✭✭

    That is to be expected when the intersection corresponds exactly to the smaller louwNida:93.1–93.388 set. So the overlap comes from the larger set with SGNTSyntacticForce:="proper name" NOT INTERSECTS louwNida:93.1–93.388.

    See Visual Filter for Names - Logos Forums for my (your) original search argument.

    Datasets can change in two years!  (more later if necessary)

    Dave
    ===

    Windows 11 & Android 13

  • MJ. Smith
    MJ. Smith Member, MVP Posts: 53,080 ✭✭✭✭✭

    [:$]And I can get caught copying without thinking 

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."