New Search HELP



A guide to Bible, Books, Morph and All Search for Logos 10






The Search syntax for Logos 10 is very different to that of previous versions and references to articles that still support it are designated as “old”. However, you can paste examples into the Search box and they will be converted to the new syntax.



Page Contents


What is Search?

“Search” can mean different things to users, so it should be clear that this wiki will discuss the Search tool in Logos and Verbum; specifically the Bible, Books and Morph types. It is not like Google Search which will attempt to interpret your input. Logos Search attempts to match your input to the text of your resources e.g. if you input kings of judah Search will attempt to find those words in your resources. It will not attempt to find a list of the Kings of Judah, but it is possible to further direct your search to find articles that may have a list of the kings e.g. heading:”kings of judah” will look for articles with those words in its heading.
Search not only works with the text of your books but also with a large amount of data categories that come from Faithlife. e.g. searching for persons when not directly named, preaching themes, biblical events and questions in the bible. These categories are usually called datatypes and the process of assigning them to text is called tagging. So, it becomes very important that you learn how to present your query (the “syntax”) so that it will be understood by Search.
The important thing to note is that you cannot search for punctuation and symbols! You can only search for words (incl. hyphenated words), possessive nouns (God’s) and numbers.

Options

These are found in the Search toolbar and will be referenced within brackets [..] in this document.

  • Select Match case for a case sensitive search.
  • Select Match all forms to perform a search that is stemmed.
    Note that stemming is algorithmic and matches some non-Original language words by their perceived stem or root.
  • Select Reference matching to impact results from a query with datatype terms:
    • Narrow will only use the datatypes that you specify.
      This was the default in Logos 9.
    • Default will get results from other datatypes with a similar value.
      For example: topic:”Holy Spirit” will also return results for preachingTheme:”Holy Spirit”.
      This is much the same as Match equivalent references (MER) in Logos 9.
    • Broad will incorporate datatypes, headwords and words with values that are equivalent to your value.
      For example: topic:”Holy Spirit” will return results that use “God the Spirit”, “Comforter” and “Paraclete” in addition to “Holy Spirit”.


Syntax and Operators

A Search query will often comprise a single term e.g. king, “John 3:16” whilst more complex ones will have multiple terms in the format: term1 OPERATOR term2…, where operators must be UPPERCASE e.g. king OR prophet.

A complex term will comprise a keyword and a value in the format keyword:value , where a datatype is an example of a keyword (see Advanced Searching).
Note the use of the colon (:) with a keyword as the <…> and {...} brackets of Logos 9 are no longer used for this purpose.

1. References

The text of a resource can include references, of which bible references are the most familiar. And they can occur in a variety of formats like vv. 25-26, 1 Cor. 2:6. If you hover over the first it will tell you it is Matthew 11:25-26 whilst the second is self-evident. The bible datatype manages these and enables you to search for them.
You can get the format of a reference after right-clicking it to get a Context menu and selecting Search in Copy reference: e.g. bible:”Matthew 11:25–26”. Then you can use it to find that reference in other resources. If you want the exact reference use bible:=”Matthew 11:25–26” otherwise bible:”Matthew 11:25–26” will return Mt 11:25, Mt 11:26 or a range of verses that include them e.g. Mt:11:25-30.
Note that Mt is equivalent to Matthew and you will find short forms for all the books of the bible.

There are many other datatypes and you can find how to search for them in the same way. But there is a general format that applies to all datatypes and their values i.e. datatype:[Op]value where Op can be:

  • = —> exact match e.g. bible:=”Jn 3:16” will only find Jn 3:16
  • << —> result wholly included in value, or value with any dependents e.g. Jn 3:16 with Jn 3:16b
  • >> —> result includes the whole value, or value with any ancestors e.g. Jn 3:16 with Jn 2:23-3:31, 3:16-17
  • ~ —> broad intersection, or value with all its dependents and ancestors i.e. << with >>
  • —> narrow intersection when no Op is specified e.g. Jn 3:16 with Jn 3:16b, 3:16-17
    • it finds any bible reference within a range of verses in the same chapter.
    • same as << with other datatypes.

Note that value requires quotes if it contains spaces.

Datatypes can have a number of formats:

  • bible:”John 3:16” —> is recognised as John 3:16
  • bible:”Jn 3:16” —> is also recognised as John 3:16, and
  • bible:Jn3.16 —> is also recognised as John 3:16
  • strongs:g3056 —> is recognised as GreekStrongs 3056
  • strongs:h769-771 —> is recognised as HebrewStrongs 769-771
  • greekGK:=”Greek GK #3365” —> is recognised as Greek GK 3365
  • greekGK:=3365 —> is also recognised as Greek GK 3365
  • louwNida:57.125-57.127 —> is recognised as Louw-Nida subdomains 57.125-57.127
  • louwNida:57.125-127 —> is also recognised as Louw-Nida 57.125-57.127
  • twot:1768-1768b —> is recognised as TWOT numbers 1768-1768b
  • tdnt:7.445-446 —> is recognised as TDNT Volume 7 Pages 445-446

2. (Logical) OR, AND, NOT

The Logical or Boolean operators.

Comma is no longer accepted for OR and there is limited acceptance of space for AND.

For example:

  • Jesus OR Lord —> either “Jesus” or “Lord”, or both
  • Jesus AND Lord —> both “Jesus” and “Lord”
  • Jesus Lord —> is equivalent to Jesus AND Lord, but
  • (Jesus Lord) —> is not accepted. Terms in parentheses require an explicit operator
  • Jesus, Lord —> is treated as Jesus AND Lord because the comma is ignored
  • Jesus NOT Lord —> find “Jesus” but “Lord” cannot be present.
    With [Match case] in a Bible Search, it means you want “Jesus” but NOT “Lord” (a referent for “Jesus” and “God”), whilst “lord” will be included.
  • Jesus NOT “Lord Jesus” —> is less restrictive, as it allows “Lord” outside the phrase “Lord Jesus”.

Note: you cannot use space for AND in combination with other operators.

3. Proximity

Results from a Search can be limited to verses, chapters or articles but you can further restrict results by specifying their proximity to each other (and their order).

EQUALS, NOT EQUALS

These operators require results to be in exactly the same location or in different locations in the resource, usually in a morphological resource or a reverse interlinear (RI) bible.

For example:
Note that lemma is valid in Bible Search as well as Morph Search.

  • lemma:λόγος EQUALS word —> finds where λόγος is translated as “word”
    i.e. they refer to each other and share the same location in the resource.
  • lemma:λόγος NOT EQUALS word —> finds where λόγος is not translated as “word”
  • word NOT EQUALS lemma:λόγος —> finds words other than λόγος that were translated as “word”.
    • this can show where “word” was interpolated in a RI translation.
    • restrict this query to the New Testament to avoid spurious results.
  • strongs:g3056 EQUALS word —> this will work in older KJV bibles without a RI.

BEFORE, AFTER, WITHIN

These operators specify the order of terms in the text and/or restrict their proximity.

  • BEFORE specifies that the first term occurs before the second term.
  • AFTER* specifies that the first term occurs after the second term.
  • WITHIN specifies the proximity of terms to each other, irrespective of order.

The main unit of proximity for these operators is WORDS and these are the actual words you see in the text.
Intervening punctuation and footnote markers are ignored, so the minimum separation between words is 1.
CHARS (characters) can also be used and they include word separators (space), punctuation and footnote markers.
Consequently, the minimum separation between words is 2.

  • Lord BEFORE 4 WORDS Christ —> separation is between 1 and 4 words.
  • Lord WITHIN 2-3 WORDS Christ —> separation is between 2 and 3 words.
  • Lord BEFORE 2-2 WORDS Christ —> separation is exactly 2 words.
  • Lord BEFORE 2 CHARS “Jesus Christ” —> will find “Lord Jesus Christ” with no punctuation or footnote markers between “Lord” and “Jesus Christ”.

For example:

  • Jesus BEFORE Christ
  • Jesus BEFORE 2 WORDS Christ
  • Christ AFTER 2 WORDS Jesus —> functionally the same as “Jesus BEFORE 2 WORDS Christ”
  • Jesus WITHIN 2 WORDS Christ
  • (Lord OR Jesus) BEFORE 2 WORDS Christ —> specifies two words before “Christ”.
    Use [Match case] for Lord as this is a referent/title for “Jesus” and “God”.

NEAR, THEN

  • NEAR is equivalent to WITHIN 48 CHARS i.e. an inbuilt proximity of 48 chars (about 8-10 words).
  • THEN is equivalent to BEFORE 1-1 WORDS but the overall expression is treated as a single term.

For example:

  • Jesus NEAR Christ —> both terms are counted and highlighted differently
  • Jesus THEN Christ —> the terms are counted as 1 and highlighted the same
    • Jesus BEFORE 1 WORDS Christ —> returns double the count & words are highlighted differently.

4. Intersection

You can find where the text results of different search terms overlap or whether the text of one lies within the other.
The operators are used with terms like Person, Event, Culture together with words or phrases.

IN, INTERSECTS

  • x IN y —> finds text x that is fully contained within y e.g. Shem IN event:”The flood”
    • x must be the smaller term.
    • Note: this was WITHIN in Logos 9.
  • x INTERSECTS y —> finds those parts of text x that overlap y e.g. Lord INTERSECTS person:Jesus
    • it will also match data in the same location or column of an Interlinear e.g. Jesus INTERSECTS louwNida:93.169.
  • x NOT IN y —> finds text x that is not contained within y e.g. Shem NOT IN event:”The flood”
  • x NOT INTERSECTS y —> finds text x that do not overlap y e.g. Christ NOT INTERSECTS person:Jesus
    • where person:Jesus matches “Lord Jesus”, “Lord”, or “Jesus”.

NOT will also be satisfied if y is not present.

If the text of one search term may not be contained fully IN the other, use INTERSECTS.
Use INTERSECTS where EQUALS may fail because the terms do not share the exact same location.
Use WITHIN 0 WORDS if INTERSECTS fails when used with Proximity operators.

See Advanced Searching Examples for other examples.

5. Term

The term keyword is used to merge different terms so that their results count is normalised and they will have the same highlight colour.
It is usually used for a list of words with OR.

  • term:(a AND|OR b AND|OR c ...) —> only OR and AND are allowed.

For example:

  • term:(who OR whoever OR whom OR whose) —> will produce results with the same highlight.
  • term:(“famine in” AND land) —> will work with a phrase.
  • term:(“he ass” OR ass) —> “ass” is only counted once when it occurs in “he ass”.

6. Wildcards

Wildcard symbols are used to represent zero or more characters in a word.

  • * will match any sequence of zero or more characters
  • ? will match 1 character in a word, and also matches zero characters at the end of a word.

For example:

  • lord* —> matches “lord”, “lords”, “lorded” and “lord’s”.
  • lord? —> matches “lord”, “lords”, but not “lorded” nor “lord’s”.
  • lo?d —> matches “lord”, “load” but not “lod”.

A wildcard will not match punctuation, spaces, or anything else that separates words i.e. Jesus?Christ and Jesus*Christ will not match “Jesus Christ”.

7. Phrases

Use quotes to search for a phrase in the text e.g. “people of Israel”. This ensures the order and close proximity of the individual words, without stemming
i.e. words in a phrase do not respond to [Match all forms] but they do respond to [Match case].
An alternative is to hyphenate the words e.g. people-of-Israel, and they will respond to [Match all forms].
If a phrase could be interpreted as a datatype then use the text keyword.

For example:

  • “Lord Jesus Christ” —> use [Match case] to get “Lord”.
  • “Lord Jesus” BEFORE 1 WORDS Christ —> is functionally the same as the above.
  • “Lord ??? Christ” —> will match phrases with a word of three letters between “Lord” and “Christ”.
  • Lord-Jesus —> an alternative to “Lord Jesus”.
  • text:”John 3:15-16” —> will prevent the interpretation of bible:”John 3:15-16”.

8. Fields

A field is a specially tagged portion of text in a resource e.g. Surface Text, Bible Text, Words of Christ (WOC), Heading Text, Large Text.
You can use the “All... Text” drop down menu to select an available field or you can use field names to affect individual terms of your query.

The query syntax is:

  • field.fieldName:expression —> use abbreviated fieldNames like bible, WOC, heading, largetext.
    • fieldName1/fieldName2/...fieldName9:expression —> searches multiple fields

Note that the field. modifier is only needed to prevent ambiguity.

For example:

  • woc:”blessed are” —> also WordsofChrist:”blessed are”
  • field.bible:Joshua —> prevents ambiguity with the bible datatype
  • bible/content:Joshua —> also prevents ambiguity with the bible datatype
  • surface:baptism —> look for “baptism” in the visible text (or manuscript) i.e. it avoids footnotes
  • heading:baptism —> look for “baptism” in headings
  • heading:(baptism OR salvation) —> look for multiple values in headings
    • heading:term:(baptism OR salvation) —> uses a term list
  • heading/largeText:baptism —> look for “baptism” in multiple fields
  • heading:baptism NEAR bible:”Acts 2:38” —> the bible term is not restricted to a heading.
  • heading:(baptism NEAR bible:”Acts 2:38”) —> restricts both terms to a heading.
  • crossRef:1Kings7 —> will find 1 Kings 7 as a cross-reference in a bible.

See Search Fields for available fields.

9. Language Match Commands

Match commands are used to refine matches for words in different languages.
The affected term will ignore equivalent Match options in the toolbar, which will still apply to any other terms.

The query syntax is:

  • match.langMark:word

For example:

  • match.case:god —> matches lower case “god” but it will be affected by [Match all forms] in the toolbar.
  • match.nostem:god —> no stemming i.e. “gods” is not allowed but it will be affected by [Match case].
  • match.nostem:match.case:God —> only “God” is allowed. It overrides [Match all forms] and [Match case].
  • match.case:”God” NEAR lord —> only “lord” will be affected by [Match case] in the toolbar.
  • match.exact:She —> will not match transliterated Shē, Shēʹ.
    • a word in double quotes ~“She~” also requires an exact match.
  • match.marks:ἀγάπῃ
  • match.accents:hebrew:מֶֽלֶךְ
  • match.dagesh:match.accents:hebrew:מֶֽלֶךְ —> will be sensitive to vowels and accents.

Grouping

1. Precedence associated with AND/OR operators.

Christ OR Jesus AND Lord will be interpreted as Christ OR (Jesus AND Lord) unless you type (Christ OR Jesus) AND Lord. Adding parentheses (…) will remove the ambiguity because (Christ OR Jesus) will be evaluated first.

You can improve the clarity of results if you type term:(Christ OR Jesus) AND Lord as “Christ” and “Jesus” will have the same colour instead of being different.

Note that you can introduce proximity between the two expressions with term:(Christ OR Jesus) WITHIN 2 WORDS Lord.

Remember that OR is the only operator that provides a choice and it will introduce ambiguities unless you use parentheses to indicate precedence.

2. Precedence with/between Proximity operators

You may assume that God NEAR wrath AND might will ensure that both “wrath” and “might” are close to “God”. But results will show that NEAR has precedence as it is parsed as (God NEAR wrath) AND might. So you must impress your precedence and use God NEAR (wrath AND might).

So don’t worry about precedence, just use parentheses!

3. INTERSECTS and Proximity operators

(lemma.g:γυνή INTERSECTS sense:wife) AFTER 1 WORDS morph.g:R will count and highlight results for both the lemma and the pronoun as per an AFTER query. But if you were only interested in the lemma result then you did not make best use of parentheses.
lemma.g:γυνή INTERSECTS (sense:wife AFTER 1 WORDS morph.g:R) makes this an INTERSECTS query and only the lemma (with sense = “wife”) is counted and highlighted!


Bible Search is a convenient way to search biblical text in bibles, and for data that is associated with it e.g. Words of Christ, Persons, Events, Miracles. You can restrict your search by Verse or by Chapter . If you want to search by Sentence or Clause (or other grammatical structures) you must look to Syntax Search or Clause Search.

To perform morphological searches it is best to use Morph Search and then select Bible Search to get the correct syntax.

You can search for bible cross references in footnotes e.g. crossref:1Kings7 (the bible reference bible:1Kings7 used to be sufficient in Logos 9).
Depending on the search terms, you may get results in Fuzzy Bible Search.


Books Search replaces Basic Search from Logos 9. It is primarily used for non-bible and non-morphological resources, but you can search bibles if you select “Bible Text” instead of All text. Results are given by article, which is usually a chapter in bibles.

lang:word is a manuscript search, where lang can be greek, hebrew, aramaic, syriac or a non-biblical language. It will not find occurrences of that word at the lemma level e.g.

  • greek:λόγος
  • hebrew:מלך
  • aramaic:מלך

You can filter your search with a reference range if you see the heading All Passages
e.g. select the resource NPNF 1.2 and you can enter/paste a reference like Augustine City of God 20.1 into the Reference Range box.


This search is used for morphologically tagged resources, usually bibles.
Morphological terms can be used with most Operators but note that proximity searches should be attempted in an original language resource rather than one with a reverse interlinear.

For lemmas and roots the format is lemma.x:word, root.x:word where x specifies the morphology e.g. lemma.g:ἀγαπάω (g = Logos Greek morphology).
For morphological codes use @codes or morph.x:codes e.g. @VF, morph.g:VF.
In practice, Logos will help you format the query. You only need to know that they can be combined as a single term e.g. lemma.g:ἀγαπάω@VF.

First select the resource, which is particularly important for Hebrew.
Type g:transliteration or h:transliteration to get a Greek or Hebrew word list from which you can select a lemma or a root
e.g. g:agapa —> lemma.g:ἀγαπάω (SBLGNT), h:el —> lemma.h:”אֵל:5” (LHB).

Type @ to get a “Part of Speech” picker and make your selections e.g. @N, @VF.
Now you will have a search term like lemma.g:ἀγαπάω@VF for the Greek word and its morphology.
If you use @ by itself the picker will use morph.x:codes format to reflect the morphology.

But you can still use @ terms as follows, even in Bible Search :

  • @CLI EQUALS therefore
  • (@NG OR @JG OR @DG)
  • term:(@NG OR @JG OR @DG)
  • @NG WITHIN 1 WORDS term:(@JG OR @DG)

You can also search for manuscript words —> see Books Search above.


Whilst you can use all the power of an Advanced Search All Search is more useful for a simple word/phrase query with a modest library of resources.
The main search is a ranked search of all books in your Library, including Personal, Cloud and Print resources . Other types of search are presented in Cards with rectangular frames, but they usually provide partial results with an option to get more:-

  • Factbook —> links to Factbook articles.
  • Preferred Bible —> results from your top Bible.
  • Your Documents —> results from documents that you created.
  • Atlas —> relevant results from Atlas [online].
  • Library —> searches Library for metadata that includes the main term.
  • Questions and Answers —> a search of label:answer with a topic or question that matches the main term.
  • Media —> images from Media Collections in Media Search.
  • Faithlife Sermons —> relevant Sermons from sermons.faithlife.com [online].
  • Popular Quotations —> returns Quotes where the main term matches an author or word(s) in any quotation [online].
    • note that resources could be outside your Library.


Available from the toolbar of most resources, Inline Search allows you to search the resource with results formatted directly in the text.
Click the icon to initiate a search and click it again to exit.


Fuzzy is a display option in Bible Search. It performs an online search of multiple English bibles for words that ‘fuzzily’ belong to a bible passage and presents results in each bible being searched. The words are treated individually and should be separated by spaces (or AND) to get a meaningful result.

Note that some words are ignored, and fuzzy matches are not highlighted.
In ESV for example, results for fortunate are those who will highlight “are”, “who” in 2 Chron 9:7, but “Happy” is not highlighted and neither is “Blessed” in other passages.
A search for blessed are those who is more fruitful and 2 Chron 9:7 is (rightly) not included.


Searching Filtered/Selected Resources

Whilst you can select resources via Collections or Tags and Ratings, it is not always convenient/necessary to create Collections and Tags for many searches.

1. Enter a Collection rule
In the Search box for Resources enter a rule that you would use for a Collection.
e.g. * -type:bible will select all types of resources except bibles.

2. Select from Library
Select some resources in Library, right click and choose Search these resources. Depending on the resources you have selected, it will open either a Bible Search or a Basic Search and allow you to enter a search term.
If you filter Library from the Sidebar or Find box, and/or sort it via the headings in Details view, you will have a list of resources that specifically interest you e.g. sort by Last Accessed for resources you recently read/opened.


Advanced Searching

The Logos Search engine enables powerful searches for rich categories of (mainly) biblical data and the necessary information for these categories is stored in a dataset.
Use of them will require a current Feature Set or a subscription e.g. Faithlife Connect.
The term keyword will apply to datatype names, search extension names, field names, label names and property names that you use in a Search e.g. Person, Event, Miracle.
They are case insensitive whilst their values are usually case sensitive e.g. event:”The flood”. So the general syntax is keyword:value.

Datatypes
Most datatypes are straightforward or familiar and are usually referenced in the text, but the advanced ones classify words or sections of the text e.g. Person, Place, Preaching Theme, Event. Section datatypes used the Section keyword in Logos 9 and that is still the case e.g. section:event:/value/.

Labels
A Label provides a way to attach multiple Properties to text that can be linked by the AND/OR operators and used with wildcards. Property values are usually associated with a datatype e.g. agent:person:Peter in label Miracle, where the Agent is “Peter”.

Narrow Reference Matching
For purposes of this guide, choose Narrow Reference Matching in the Search toolbar as this was the default for Logos 9.

Broad Reference Matching
This is too broad for the person keyword (below) because it also uses the familiar name(s) as a term e.g. person:Paul will match any names that contain “Paul” or “Saul” when the intended target is the Apostle!


Keyword Searching

Start with a Reverse Interlinear bible and right-click a word. The Context menu will show which keywords are present, and the other side will provide a Search by opening the Search tool with a properly formatted query e.g. propositionalOutline:Jesus-Action.
Alternatively, type a word in a Search Find box and let autocomplete suggest and format the query for you e.g. type marriage in Books Search and you will see suggestions for Preaching Theme, Culture and Sense. Select one and run the search.
If you want to restrict the suggestions then start typing e.g. culture:marriage, event:moses and make your selection.
If you want to see available datatypes then press the + icon in the Find box and select one. Some values will be suggested or you can start to type a possible value and then make your selection.

Person, Place, Thing Searches

You can search for these fundamental entities:

  • person:name —> biblical persons e.g. Jesus, Peter
  • place:name —> biblical places (towns, rivers, regions) e.g. Jordan, Jerusalem
  • thing:name —> biblical things e.g. Aaron’s Rod, Dog
  • biography:name —> non-biblical notable persons e.g. Martin Luther

For example:

  • person:Jesus
  • place:”Jericho (New Testament)”
  • thing:”Aaron’s Rod”
  • biography:”Martin Luther”

A Search will also find referents for Person, Place and Thing i.e. pronouns, verbs and some adjectives.
Note that a referent can cover several words e.g. “Lord God”, “king of the Jews”.

Speaker, Addressee

Speaker finds all the text spoken by a biblical Person (and sometimes by a Thing).
Addressee allows you to find where a Person, Place, or Thing is spoken to in the bible (it returns the text of the speaker).

  • speaker:name —> the name datatype is assumed (Person, Thing)
  • addressee:name —> the name datatype is assumed (Person, Place, or Thing)

For example:

  • speaker:Jesus —> finds text where Jesus is the speaker
  • addressee:”A Crowd” —> finds the text spoken to a crowd
  • addressee:”A Crowd” IN speaker:Jesus —> finds occasions where Jesus is speaking to a crowd
  • addressee:Disciples IN speaker:Jesus —> finds occasions where Jesus is speaking to the disciples
  • addressee:Jerusalem IN speaker:Jesus —> finds occasions where Jesus is addressing Jerusalem
  • addressee:Bird IN speaker:”An Angel” —> finds occasions where an angel is speaking to birds.

There can be multiple addressees in a speech, hence the use of IN. But INTERSECTS would be safer.

Sense

This datatype is encapsulated by the Bible Sense Lexicon tool and its dataset.
A Search will find words corresponding to a sense in your bibles.

  • Sense:=~word —> encompasses the meaning of various words used in the bible

For example:

  • sense:=knowledge —> finds words with exactly the sense of ‘knowledge’
  • sense:<<knowledge —> finds words for “knowledge” and all of its descendants
  • sense:>>knowledge —> finds words for “knowledge” and its ancestors i.e. senses for which “knowledge” is a descendant
  • sense:knowledge —> finds words for “knowledge” and all of its descendants
  • sense:~knowledge —> finds words for “knowledge” and all of its ancestors and descendants
  • sense:<knowledge —> finds words for the descendants of “knowledge”, but not “knowledge” itself
  • sense:>knowledge —> finds words for the ancestors of “knowledge”, but not “knowledge” itself

Section Searches

These searches return the text that is identified by a textual datatype from information stored in a dataset.
They correspond to {Section…} searches in Logos 9.

  • section:datatype:=~value —> this is equivalent to {Section <datatype value>} in Logos 9
  • reference:datatype:=~value —> this is equivalent to <datatype value> in Logos 9
  • datatype:=~value ==> section OR reference
    • this format is used for most practical purposes, but use the section keyword for more accurate results.

For example:

Consult the appropriate Glossary (type:glossary) or Manual (type:manual) for other search terms, or use the Context menu.

Label Searches

A Label can have multiple properties associated with the resource text, much in the way you attach a label to your luggage with information that identifies it as yours.
Labels allow different operators together with wildcards e.g. logical AND/OR/NOT, the wildcard *, implicit all and explicit any.

Syntax (formal):-

  • label:(labelName AND|NOT property1:value1 AND|NOT property2:value2 ...)
  • label:(labelName AND|NOT (property1:value1 OR property2:value2 ...))
    • OR can be combined with AND | NOT but use parentheses to get the desired result.
  • label:(labelName NOT property:*) —> finds occurrences that don’t have that property name e.g. label:(miracle NOT patient:*)
  • label:property:value —> finds all labels with that property value e.g. label:agent:John
    where “John” will match the name of any Person that contains “John”.
  • label:labelName —> finds all occurrences of that label e.g. label:miracle

Unlike Logos 9, a datatype does not have to be stated with a property value e.g. agent:John above.
If you need to be more precise the syntax is property:datatype:value e.g. agent:person:”John the Baptist”.

Simple Syntax :-

  • labelName:(property1:value1 AND|NOT property2:value2 ...) e.g. miracle:(Patient:Paul AND Agent:Jesus)
  • labelName:(property1:value1 OR property2:value2 ...) e.g. miracle:(type:Affliction OR type:Healing)
    • OR can be combined with AND | NOT but use parentheses to get the desired result.
  • labelName:property:value —> finds labels with that property value e.g. miracle:audience:”John the Baptist”
  • labelName:any:value —> finds labels with that value in any property e.g. miracle:any:Peter
  • labelName:property:* —> finds labels that have that property name e.g. miracle:audience:*
  • labelName:* —> finds all occurrences of that label e.g. miracle:*

Note: that a modifier label. will be needed for labels whose name conflicts with a datatype e.g. label.longacreGenre.

See Searchable Labels for examples of Faithlife labels.

User Labels

Use the Highlighting tool to attach a label to a style via the Labeling section. You can define its properties and assign default values.
When you apply the style to your text you will be prompted to supply values for the various properties (and you can create new properties).

Do not create a property with colon : in its name.
The label: keyword or the label. modifier must be used in a Search.

For example:
    Create label Personality with properties Name and Description:

  • label:personality —> finds all occurrences of label Personality
  • label:(Personality AND name:person:David AND description:=King) —> finds labels where “David” is described as a “King”
  • label:(Personality AND description:”King of Israel”) —> finds all persons described as ”King of Israel”
  • label.personality:description:”King of Israel” —> simple syntax with modifier
  • label:(Personality NOT description:King) —> finds persons not described as a “King”.

Milestone

Milestones are datatype markers in resources that are indexed (or organized) by that datatype e.g. the book/chapter/verse numbers in a bible,
the Strong’s numbers in Enhanced Strong’s Lexicon.
Milestone will return the text associated with a datatype value in such resources.
Bible milestones are especially useful because you can get the commentary on a passage when you search Bible Commentaries, Study Bibles, or Bible Notes.

  • milestone:datatype:value —> returns the text of any datatype value except Headword

Note that term IN|INTERSECTS datatype:value can be interpreted as a milestone query, but it can produce sputious results with the bible datatype
so it is better to use term IN|INTERSECTS milestone:datatype:value.

For example:

  • milestone:bible:”Jn 3:16” —> returns the text of Jn 3:16 in a Bible or Commentary
  • milestone:Jn3.16 —> is equivalent. It has no spaces and period can be used in place of the colon
  • love IN milestone:Jn3:16 —> finds “love” within the text of Jn 3:16 in a Bible or Commentary
  • “an account” IN milestone:(bible:Ro OR bible:heb) —> finds the phrase in the text of Romans or Hebrews.
  • milestone:topic:Flood —> returns similar results to a Topic Guide.
  • milestone:Strongs:G3056 —> returns the text of Greek Strong’s #3056 in relevant lexicons.

Passage List

Finds occurrences of bible references in a resource from a Passage List.
And it can be used to provide cross references in a Bible Search.

  • passageList:name —> get the exact name via copy and paste

For example:

  • passageList:”OT Quotes from Jesus – ESV” —> finds references from OT Quotes from Jesus – ESV
  • milestone:passageList:”OT Quotes from Jesus – ESV” —> uses the passage list as milestones.

Headword

Headwords are used to identify articles in a dictionary resource. It is usually the visible text at the top of an article like this, but there can be non-visible headwords, or aliases. They are found in resource types like lexicon, dictionary, encyclopedia, or concordance.

  • headword:word —> returns the text of an article, so it is also possible to search for words in the article.
    • word has to be precise as wildcards are not allowed.

For example:

  • headword:Salvation —> returns the text of the article named “Salvation”
  • headword:”Salvation, nature of” —> Dictionary of Bible Themes has this headword
  • sinner IN headword:salvation —> finds “sinner” in the article on Salvation.

A Topic Guide for Salvation will return more results.

Highlighting

The highlight keyword will find the text you have highlighted in your resources.

  • highlight:”styleName” —> finds highlights with that style name, irrespective of Palette
  • highlight:”paletteName/styleName” —> useful if multiple palettes have a style with the same name
  • highlight:”paletteName/*” —> finds all highlights from that palette
  • highlight:* —> finds all your highlights (very effective with Inline Search).

Note avoid creating styles with a slash in their name.

For example:

  • highlight:Box —> finds all highlights with that style
  • highlight:”Double Underline” —> finds all highlights with the Double Underline style
  • highlight:”Emphasis Markup/Double Underline” —> finds highlights with the Double Underline style from the Emphasis Markup palette
  • highlight:”Emphasis Markup/*” —> finds all highlights with styles from the Emphasis Markup palette



Example Searches

Note that lemma will only work with resources using Logos Morphology.

  • person:Jesus EQUALS place:Nazareth —> gets one result in most RI’s (Acts 26.9). In Mk 6:1 (ESV) “his hometown” is tagged for Nazareth,
    but only “his” is tagged for Jesus, so person:Jesus does not occupy the same locations as place:Nazareth.
  • person:Jesus IN place:Nazareth —> will get more results, incl. Mk 6:1 because person:Jesus is fully within the text for place:Nazareth.
  • person:Jesus INTERSECTS place:Nazareth —> will get even more results because of overlap. This would be the preferred search.
  • lemma:κύριος INTERSECTS person:Jesus —> will find where “Lord” (κύριος) refers to Jesus in RI’s.
  • lemma:κύριος IN person:Jesus —> returns the same results in this case.
  • morph.g:NGSF EQUALS (tongue OR language) —> would the usual choice for this, but
  • morph.g:NGSF INTERSECTS (tongue OR language) —> gives the same results.
  • generation IN milestone:bible:Lk11 —> finds “generation” in the text of Luke 11 in bibles or commentaries.
  • male IN milestone:louwNida:10.30-31 —> finds “male” in the text of Louw-Nida sub-domains in LN lexicons.
  • Nazareth IN highlight:”Important Events” —> finds “Nazareth” in the (user created) style ‘Important Events’.
  • darkness IN culture:Light —> finds “darkness” in the text of the Cultural Concept for ‘Light’.
  • darkness NOT IN culture:Light —> finds where “darkness” is not within the text of the Cultural Concept for ‘Light’.
  • person:Israelites INTERSECTS person:”Israelites (the Conquest)” —> finds where ‘Israelites’ are also tagged with Israelites involved in the Conquest of Canaan
    (should be the same as the latter).
  • person:Israelites NOT INTERSECTS person:”Israelites (the Conquest)” IN milestone:bible:Joshua —> finds ‘Israelites’ who were not involved in the Conquest of Canaan.
  • person:Isaac IN speaker:Abraham —> finds references to Isaac within text spoken by Abraham
  • bible:Gen3.1–7 IN milestone:Mt4.1–11 —> finds where the story of the Fall is referenced in comments on the Temptation of Jesus.
  • speaker:Jesus INTERSECTS literaryTyping:”Quotation, Old Testament” —> finds all the instances in which Jesus quotes the Old Testament.
    • if IN gives the same result it would better delineate the terms.



Searchable Labels

Some Faithlife labels are described here but see Searchable Labels in “Logos Help” and “Verbum Help”.
The Context menu will also expose labels and you can consult the appropriate Manual (type:manual) or Glossary (type:glossary) for properties and their values.

The examples utilise both formal syntax and simple syntax where the label keyword is omitted.

Bible Outline

Properties:

  • Reference – a Bible reference of the passage being outlined

For example:

  • label:(bibleOutline AND reference:Zech14)
  • bibleOutline:reference:Zech14

Journal Article

Properties:

  • Title – the title of the article
  • References – the primary Bible reference(s) for the article
  • Author – the author(s) of the article
  • Topics – the primary Topic reference(s) the article is about
  • Date – the Date when the journal was published

For example:

  • label:(journalArticle AND title:”Contextual Analysis”)
  • journalArticle:(author:Heiser AND title:”I dare you not to bore me”) —> articles by Michael S. Heiser
  • journalArticle:topics:”Gospel of Luke”
  • journalArticle:date:”Jul 2015” —> published July 2015

Lectionary Reading

Properties:

  • Title – the title of the reading
  • References – Bible references included in the reading

For example:

  • label:(lectionaryReading AND references:Zech14.4)
  • label.lectionaryReading:references:Zech14.4 —> the modifier is needed because the keyword is also a Search field.

Sermon

Sermons that can be found in books of sermons and the Church Fathers.

Properties:

  • Title – title of the sermon
  • Subtitle – optional
  • Creator – name of the creator e.g. “John Piper”
  • Series – the sermon series name
  • References – Bible references for the sermon e.g. “Psalm 141”
  • Themes – Preaching Themes e.g. Creation, “Blessing and Cursing”
  • Date – Date the sermon was first delivered
  • Liturgical Date – Liturgical Date for when the sermon was first delivered

For example:

  • label:(sermon AND title:”Pray for God”) —> match sermons with a partial Title
  • sermon:title:”Pray for God”
  • sermon:series:Prayer —> Prayer series
  • sermon:date:”Jul 9, 2015” —> exact date
  • sermon:date:”Jul 2015” —> any date in July
  • sermon:references:”Ps 141:1-4” —> sermons on Ps 141:1-4
  • sermon:references:Ps —> sermons on any Psalm
  • sermon:(creator:”George Whitefield” AND references:Mt) —> finds Whitefield sermons on Matthew

Figurative Language

Figurative language includes metaphor, simile and other types of non-literal expressions. This label is based on a dataset of important figurative expressions in the New Testament which are documented in Figurative Language Glossary.

Properties:

  • Category – e.g. Metaphor, Metonymy, Simile, Euphemism, Idiom, Hyperbole
  • Source – e.g. Above
  • Target – e.g. God
  • Type – e.g. Above as God —> combines Source and Target

For example:

  • Label:(figurativeLanguage AND Category:Metaphor) —> finds all types of Metaphor
    • {Label Figurative Language WHERE Category ~ <FigurativeLanguageCategory Metaphor>} in Logos 9
  • figurativeLanguage:category:Metaphor —> simple syntax for Metaphor
  • mountain IN figurativeLanguage:category:Metaphor —> finds where “mountain” is used in a metaphor.
  • figurativeLanguage:(target:God AND category:Metaphor) —> finds words that conceptualize “God”.

Figure of Speech

The associated data is based on Bullinger’s Figures of Speech where each article has a title and several references to the Bible.
You can find any figure of speech by its Name or Description.

Properties:

  • Name
  • Description – where available, this is a description of the Name.

For example:

  • label:(figureofSpeech AND name:Aposiopesis)
  • figureofSpeech:name:Aposiopesis
  • figureofSpeech:(name:Aposiopesis AND description:Sudden-Silence) —> same result as Name only.
  • label:(figureofSpeech NOT name:Aposiopesis) —> this cannot be done with Simple syntax

Intertext

Intertext (Intertextuality) labels expose the data behind the interactive resource “New Testament Use of the Old Testament”.

Properties:

  • Source – Bible Reference
  • Target – Bible Reference
  • Relationship – Citation | Quotation | Allusion | Echo
  • Corpus – “New Testament” | “Old Testament Pseudepigrapha” |
    “Works of Josephus” | “Works of Philo” | “Apostolic Fathers” | “Nag Hammadi Codices”

For example:

  • label:(intertext AND source:Gen-Mal) —> finds passages in the NT whose Source is the OT
  • intertext:source:Gen-Mal —> Simple syntax
  • intertext:source:bible.nrsv:Baruch —> finds passages in the NT whose Source is Baruch in Apocrypha
  • intertext:target:Mt-Rev —> finds passages in the OT that are used in the NT
  • intertext:(source:Gen-Dt AND relationship:Quotation) —> finds quotations in the NT that come from Gen-Dt
  • label:(intertext NOT corpus:”New Testament”) —> finds passages for any corpus but “New Testament”
  • speaker:Jesus INTERSECTS intertext:source:Gen-Mal —> finds passages from the OT that were used by Jesus
  • speaker:Moses INTERSECTS intertext:target:Mt-Jn —> finds OT passages spoken by Moses that were used in the Gospels

Miracle

This label provides a search of miracle stories in the Old and New Testament.

Properties:

  • Type – Healing, Affliction, Exorcism, Judgment, Nature, Resurrection, Communication, or Provision
  • Agent – the Person that instigates the miracle e.g. God, Jesus, Peter
  • Patient – the Person or Thing that the miracle directly affects e.g. Sarah when Isaac was born
  • Beneficiary – any Person that benefits from the miracle e.g. Abraham when Isaac was born
  • Audience – any Person witnessing the miracle
  • ThingInvolved – any Thing mentioned/involved in the miracle e.g. snake, animal, flood, rain
  • Instrument – any Thing directly used to instigate the miracle

For example:

  • miracle:(agent:Jesus AND type:Healing) —> finds passages where Jesus performs a Healing
  • miracle:(agent:Jesus AND (type:Healing OR type:Affliction)) —> also finds where Jesus cures an Affliction
  • miracle:(agent:Moses AND thinginvolved:snake AND type:healing) —> healings that involve a snake
  • miracle:any:person:Peter —> miracles where Peter is involved in any capacity
  • miracle:any:John —> miracles involving any Person named “John” e.g. John the Baptist.
  • miracle:any:person:john —> will allow you to select a specific “John”.

Question

This label provides a search of all the questions in the bible broken down by Type and whether they are rhetorical.

Properties:

For example:

  • question:rhetorical:false —> finds passages where the question is not rhetorical
  • question:(rhetorical:false AND type:Wh-) —> finds questions of type “Who?”, “What?”, “When?”, or “Where?”
  • question:rhetorical:false INTERSECTS addressee:Jesus —> finds questions addressed to Jesus.

Psalms Explorer

Every psalm within the book of Psalms has been tagged and placed within the Psalms Explorer dataset. These tags enable you to search the psalms
according to properties and values listed in the Psalms Explorer Interactive.

Properties:

  • Genre
  • Attribution
  • Structure – Acrostic | Chiasm | Strophe
  • Tag – e.g. Messianic| Selah| Maskil

For example:

  • label:(psalm AND genre:Praise)
  • blessed IN psalm:genre:Praise
  • psalm:attribution:David
  • psalm:(genre:Praise AND attribution:David)

Proverbs Explorer

Every proverb within the book of Proverbs has been tagged according to Type and Form and placed within the Proverbs Explorer dataset.
See the Proverbs Explorer Interactive for values to search.

Properties:

  • Type
  • Form

For example:

  • label:(proverb AND type:Advice)
  • proverb:type:Advice
  • person:God IN proverb:type:advice —> advice concerning the Lord
  • proverb:(type:Saying AND form:”Synthetic Parallel”) —> a saying in which the second half builds upon the first.


Logos Bible Software Wiki

Welcome, Guest! (sign in)