Search HELP

A quick reference to the features of Bible, Morph and Basic Search.

Page Contents


Click the little arrow under the Search icon.
Select Match Case for a case sensitive search.
Select Match all Word Forms to perform a search that is stemmed.
Note that stemming is algorithmic and matches non-Original language words by their perceived stem or root.

Syntax and Operators

Note that search operators must be UPPERCASE.

1. References

To search for references in the text of a resource you need to know the name that identifies the data (its datatype),
together with its value and how you want to treat that value.
The format is <datatype Op value> where Op can be:

  • ~ (narrow intersection),
  • = (exact match),
  • intersect (any intersection with value),
  • subset (result wholly included in value), or
  • superset (result includes the whole value).

Note ~ is the default operator that finds any bible reference within a range of verses in the same chapter.
For example, <bible Jn 3:16> is the same as <bible ~Jn 3:16>, and it will be found in John 3:16 and John 3:15-17, but not in John 3 nor John 2:24-3:17.
See Using Operators for more examples and a detailed explanation.

Familiar datatypes are handled automatically, so <Jn 3.16> or <~Jn 3:16> are recognised as <bible ~Jn 3:16>, whilst <G5547> is recognised as <GreekStrongs = G5547>.
Strong’s number ranges can be specified as <G875-878>, <H769-771>
Louw-Nida numbers & ranges can be specified as <LN 57.125>, <ln 57.125-57.129> or <ln 57.125-129>
TWOT numbers & ranges can be specified as <TWOT 1768>, <twot 1768-1768b>
TDNT Volume/Page can be specified as <TDNT 8.1>, <tdnt 7.445>, <tdnt 7.444-447>

2. (Logical) OR, AND, ANDNOT

The Logical or Boolean operators.

For example:
 Jesus OR Lord —> either “Jesus” or “Lord”, or both
 Jesus AND Lord —> “Jesus” and “Lord”
 Jesus ANDNOT Lord —> “Jesus” but not “Lord”

 Jesus, Lord —> comma = OR
 Jesus Lord —> space = AND
 Jesus -Lord —> dash = ANDNOT (no space after the dash)

In a case sensitive Bible Search, Jesus ANDNOT Lord means you want “Jesus” in a verse but NOT “Lord” (a referent for “Jesus” or “God”), whilst “lord” will be included.
Jesus ANDNOT “Lord Jesus” is less restrictive, as it allows “Lord” outside the phrase/expression “Lord Jesus”.

Note that using the characters comma, space, and dash can give incorrect results when used in combination with Proximity & Morph operators
e.g. @N, @V does not work, and you should use @N OR @V.


Results from a Bible search are bound by verses and a Basic search (incl. bibles) is bound by chapters or articles,
but you can further restrict results by specifying their proximity to each other.
These operators require results to be in exactly the same location, or in different locations; usually in a morphological resource, or a reverse interlinear bible.

For example:
λόγος ANDEQUALS word => finds where λόγος is translated as “word”
i.e. they refer to each other, and share the same location in the resource.
λόγος NOTEQUALS word => finds where λόγος is not translated as “word”
word NOTEQUALS λόγος ==> finds words other than λόγος that were translated as “word”.
In a reverse interlinear, this can show where “word” was interpolated.


The main unit of proximity for these operators is WORDS or WORD and these are the actual words you see in the text.
For example Lord BEFORE 4 WORDS Christ, Lord WITHIN 2-3 WORDS Christ; where 4 means between 1 and 4, 2-3 means between 2 and 3. Use 2-2 for exactly 2 words.
Note that intervening punctuation and footnote markers are ignored.

CHARACTERS or CHARS can be used and they include word separators (space), punctuation and footnote markers. Consequently, the minimum separation between words is 2.
For example Lord BEFORE 2 CHARS “Jesus Christ” will find “Lord Jesus Christ” with no punctuation or footnote markers between “Lord” and “Jesus Christ”.


These specify that word(s) should occur BEFORE or AFTER another word(s), and optionally restrict their proximity.

For example:
 Jesus BEFORE Christ
 Jesus BEFORE 2 WORDS Christ
 Christ AFTER 2 WORDS Jesus ==> functionally the same as “Jesus BEFORE 2 WORDS Christ”

You can use 5. Lists to specify multiple words e.g. (Lord, Jesus) BEFORE 2 WORDS Christ.


WITHIN specifies the proximity of words to each other, irrespective of order e.g. Jesus WITHIN 2 WORDS Christ.
NEAR is similar to WITHIN but has an inbuilt proximity of 48 chars (about 8-10 words) e.g. Jesus NEAR Christ.

You can use 5. Lists to specify multiple words.

5. Lists

A list (a, b, c, d, ...) is used to specify alternative search items in a compact form.
For example (who, whoever, whom) will match who or whoever or whom. The parentheses ( ) are optional in simple searches.
Prior to v7 you had to use a list with proximity operators e.g. (who, whoever, whom) NEAR Christ,
but now you can use (who OR whoever OR whom) NEAR Christ.

Logical operators within a list will give incorrect results e.g. (God AND love), Jesus is treated as (God AND love) AND Jesus

6. Wildcards

* 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 e.g. “My God”, “people of Israel”
You can use phrases in a list e.g. (“My God”, “My Lord”)
You can use wildcards in a phrase e.g. “Lord ??? Christ” will match “Lord and Christ”.

8. Fields

A Field is a specially tagged portion of text in a resource e.g. Bible Text, Words of Christ, Heading Text.
Use the “All... Text” drop down menu to limit a search to a field.
To match a specific word(s) within a field use the format fieldname:word e.g. words-of-christ:”blessed are”.
An alternative syntax is [field fieldname1, fieldname2, ...] word e.g. [field words-of-christ] “blessed are”.
See Search Fields for available fields.

9. Language Match Commands

Match commands can be used to refine matches for words in different languages e.g. [match dagesh] hebrew:מֶֽלֶךְ, [match accents] hebrew:מֶֽלֶךְ.
Commands can be combined by separating with a comma e.g. [match dagesh, accents] hebrew:מֶֽלֶךְ will be sensitive to vowels and accents.

Used for morphologically tagged resources, usually bibles.
General format is lemma:word@morph or root:word@morph e.g. lemma:λόγος@N, root:λεγω@N.
But you can also search for lemma:word, root:word or @morph e.g. lemma:λόγος, @N

Type g:transliteration or h:transliteration to get a Greek or Hebrew word list, from which you can select a lemma e.g. g:logos, g:lego, h:el.
Type @ to get a “Part of Speech” drop down and make your selections.
A root is best selected from the context menu e.g. λεγω is the root for λόγος so the search has to be root:λεγω@N.

Morphological terms can be used with operators #2 thru #6, #8 and #9 above, but note the following:

  1. To use @ with #3 the format is (@morph) e.g. (@CLI) ANDEQUALS therefore
  2. To use @ with alternative patterns the format is @morph1, morph2, morph3... e.g. περί BEFORE 1 WORDS @NG, JG, DG

You can also search for manuscript words, individually or as a phrase (#7). Also see Basic Search below.

A convenient way to search for biblical text in bibles, and for data that is associated with it e.g. glosses, Words of Christ.
You can also perform morphological searches but get the format by using Morph Search as above and then select Bible Search
e.g. lemma:λόγος@N will then appear as <lemma = lbs/el/λόγος> ANDEQUALS <lbs-morph+el ~ N????>, where lbs=Logos Morph and el=Greek.

You can use operators and lists #1 to #9, but using a subset of #1 that applies to bibles e.g. Louw-Nida and Strong’s numbers. Note that you won’t find bible references!

You may get results in Fuzzy Bible Search, depending on the search term.

Primarily used for non-bible resources, but you can search bibles as per Bible Search above
with the advantage that results can cross verse boundaries (select “Bible Text” instead of All text).

You can use operators and lists #1 to #9.

lang:word is a manuscript search, where lang can be greek, hebrew, aramaic, syriac or a non-biblical language
e.g. greek:λόγος, aramaic:מלך, hebrew:מלך. It will find all occurrences of that word in an Interlinear bible unless you restrict it to “Surface Text” instead of All Text.


Everything searches Factbook, Media, Atlas, books on, your Personal Books and your Documents.
It also searches for resource data (metadata), Community Tags and Topics in your library.
Most of the results are partial and provide links to more complete searches:

  • You may get results in Fuzzy Bible Search, depending on the search term.
  • Topic —> provides articles from your library if the search term is a topic addressed by the “Logos Controlled Vocabulary” (LCV) dataset.
    The search term can be a phrase or words – don’t use <Topic words>.
    Note that Topic Guide is more direct and you can get further results from the Collections section.
  • Factbook —> provides results from Factbook that are related to the search term e.g. topics, biographies, events.
  • Media —> provides an image search of your library.
  • Atlas —> provides a search of the Atlas (online) if your search term is a <Place>.
  • Community Tags —> searches tags that you & others have applied to resources to supplement Faithlife’s tags.
  • Library Resources —> searches your Library metadata for resources that satisfy the query.
  • —> searches metadata for resources that satisfy the query (online).

This Search is included with Basic Search and Bible Search.
It performs an online search of multiple English bibles for words that ‘fuzzily’ belong to a bible passage.
The words are treated individually, and should be separated by spaces (or AND) to get a result.

Results appear in your preferred bible, with the most likely matches at the top. Note that some words are ignored, and fuzzy matches are not highlighted.
For example, results for fortunate are those who will highlight “are”, “who” in 2 Chron 9:7 (ESV), but “Happy” is not highlighted.
A search for happy are those who is more fruitful, and you will see results with “blessed”, whilst 2 Chron 9:7 is not included!

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.

Advanced Searching

The capabilities of the Logos 4/5 search engine have been extended with search types that enable powerful searches for rich new categories of biblical data.
Many of these features require a current Feature Set, whilst some require a subscription e.g. Faithlife Connect.

New Datatypes

Most datatypes are straightforward and familiar and they can be referenced in the text,
but many of the new ones classify words or sections of the text in much the same way that you would
e.g. <Person>, <Place>, <PreachingTheme>, <Event>. But the values they have are not as abbreviated, nor as predictable, as <Bible> or <GreekStrongs> values.
The necessary information for these datatypes is stored in a dataset, and most have been documented.

Person, Place, Thing

These datatypes enable you to get relevant results from your bible:

  • <Person xxxxx> —> biblical persons e.g. <Person Jesus>
  • <Place xxxxx> —> biblical places (towns, rivers, regions..) e.g. <Place Jerusalem>, <Place Jordan>, <Place Judea>
  • <Thing xxxxx> —> biblical things e.g. <Thing Aaron’s Rod>, <Thing dog>

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”.


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

  • <Sense =~xxxxx> —> encompasses the meaning of various words used in the bible

For example:
   <Sense ~knowledge> —> finds all words (and senses) with an inherent meaning of ‘knowledge’
   <Sense = knowledge> —> finds words with exactly the sense of ‘knowledge’


These datatypes identify sections of text in various resources.

For example:

Note that these datatypes require the {Section} extension syntax to get results from your resources.
The datasets are documented in Manuals (type:manual) in your Library, but search parameters may be documented in Glossaries (type:glossary).

Datatype Searching

Start with a Reverse Interlinear bible and right click a word. The right side of the Context menu will show which of these datatypes are present,
and the left side will allow you to Search by opening the Search tool with a properly formatted query e.g. {Section <PropositionalOutline = Jesus-Action>}.

Alternatively, type a word in a Search Find box and let the Autocompleter suggest and format the query for you
e.g. type ‘marriage’ and you will see suggestions for the Topic, Preaching Theme, Culture and Sense. Click and run the search.
An Everything search would be more fruitful as it will usually provide a Factbook article with further results and links to Guides.
If you want to restrict the suggestions then type, for example, ‘<PreachingTheme marriage’ or ‘<Event Moses’.

In resources like the Early Church Fathers you can get the reference and its datatype after choosing Reference from the context menu e.g. <JustinMartyr = Justin Martyr, Dialogue with Trypho 8>, and that will give results from other resources in your library.

Search Extensions

The {extension} syntax effectively provides new search types/plugins to the Search engine which can be used within the existing
Basic, Bible & Morph searches, depending how you want the results formatted i.e. by verse or by article.
Many are associated with data types, but not all e.g. {Highlight} is a search to find the highlighting styles in your resource(s).

One way to view this syntax is to regard a <datatype> search as a specific {extension} e.g. {Reference <bible Jn 3:16>} could be looking for references to Jn 3:16 in any resource,
whereas {Milestone <bible Jn 3:16>} will return the text of Jn 3:16 from a bible (or commentary).
Note that you won’t find <bible> milestones in a bible dictionary or encyclopedia!

Note the Search Field (and highlighting) drop-down menu doesn’t apply to search extensions.


{Section...} returns the text that is identified by a textual datatype (from information stored in a dataset).

Example usage:-

  • {Section <Event xxxx>} e.g. {Section <Event The flood>}
  • {Section <LiteraryType xxxx>} e.g. {Section <LiteraryType Healing>}
  • {Section <Culture xxxx>} e.g. {Section <Culture Light>}
  • {Section <PreachingTheme xxxx>} e.g. {Section <PreachingTheme Marriage>}
  • {Section <PropositionalOutline = Jesus-Action>}

Consult the appropriate Glossary or Manual for search terms, or use the context menu.


The {Highlight} extension finds the text you have highlighted in your resources.

  • {Highlight StyleName} —> finds highlights with that style
  • {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. use quotes if palettes or styles contain a slash in the name (not needed for spaces)

For example:
   {Highlight Turquoise Highlight} —> finds all highlights with the ‘Turquoise Highlight’ style
   {Highlight Test/Turquoise Highlight} —> finds highlights with the ‘Turquoise Highlight’ style from the ‘Test’ palette
   {Highlight Highlighter Pens/Orange Highlighter}
   {Highlight Highlighter Pens/*} —> finds all highlights with styles from the ‘Highlighter Pens’ palette.
   {Highlight Highlighter Pens/”Highlight/Orange”} —> finds highlights with the ‘Highlight/Orange’ style from the ‘Highlighter Pens’ palette.


A Label provides a way to attach multiple tags to text, much in the way you attach a label to your luggage with information that enables it to be identified as yours. Use the Highlighting tool to attach a label to a style via the new Labeling section. You can define its properties/attributes and assign default values. When you have applied the style and given values to the Label properties you can Search as below.
Note that you can create any number of attributes with the same name.

  • {Label labelname WHERE [NOT] property1=~value1 AND property2=~value2 ...}
  • {Label labelname} —> finds all labels that have the specified label name
  • {Label labelname WHERE property1} —> finds all labels that have the specified property name (ANY value)
  • {Label labelname WHERE NOT property1} —> finds all labels that don’t have that property name
  • {Label labelname WHERE property1 ~“King David”} —> finds all labels in which the property1 value contains “King David”
  • {Label labelname WHERE property1 ~“King David” AND property2 = OT} —> finds all labels in which the property1 value contains
    “King David” AND the property2 value is exactly ‘OT’

For example:
   Create label Personality with attributes Name, Name, Date, Description
   {Label Personality} —> finds all labels of type Personality
   {Label Personality WHERE Name =Anyone} —> finds labels with exact value ‘Anyone’. It won’t work if a label has multiple Name values.
   {Label Personality WHERE Name ~Anyone} —> finds all labels with value ‘Anyone’ in Name.


Headwords are used to identify articles in a 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 resources like a bible dictionary, encyclopedia, or concordance.

  • {Headword words} —> returns the text of an article, so it is also possible to search for words WITHIN the article.

For example:
   {Headword Salvation}
   {Headword Salvation, nature of}

Wildcards are not allowed, so you have to be precise. Note that a Topic Guide for Salvation would return both results.


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.
The {Milestone} extension will return the text associated with a datatype value in such resources.

  • {Milestone <datatype xxx>} —> returns the text of any datatype value except Headword

For example:
   {Milestone <Bible Jn 3:16>} —> returns the text of Jn 3:16 in a Bible or Commentary
   {Milestone <G123>} —> returns the text of Greek Strong’s #123 in Enhanced Strong’s Lexicon.

Passage List

Finds occurrences of bible references from a Passage List.

  • {PassageList xxxxx} —> N.B. copy and paste the PL name to get the exact name.

For example:
   {PassageList OT Quotes from Jesus – ESV} —> finds references from the PL OT Quotes from Jesus – ESV


Finds all the text spoken by a Person.

  • {Speaker <Person xxxx>}

For example:
   {Speaker <Person Jesus>} —> finds text where Jesus is the speaker


The Addressees in Reported Speech dataset allows you to find all the places where a person, place, or thing is spoken to in the biblical texts.
Find everywhere Satan speaks to Jesus or look for all the places Jesus prays to the Father.

  • {Addressee <Person xxxx>}
  • {Addressee <Place xxxx>}
  • {Addressee <Thing xxxx>}

For example:
   {Addressee <Person Disciples>} WITHIN {Speaker <Person Jesus>} —> finds occasions where Jesus is speaking to the disciples
   {Addressee <Place Jerusalem>} WITHIN {Speaker <Person Jesus>} —> finds occasions where Jesus is addressing Jerusalem
   {Addressee <Thing Bird>} WITHIN {Speaker <Person An Angel>} —> finds occasions where an angel is speaking to birds
Note: AND could be used but it gives spurious results in a Basic Search


    • x WITHIN y —> finds text x that is fully contained within y
    • x INTERSECTS y —> finds those parts of text x that overlap yv7+
      (x WITHIN 0 WORDS y — v6)
  2. NOT modifier — v7+
    Acts as a logical NOT with certain operators:
    • x NOT WITHIN y
    • x NOT NEAR y
    • x NOT BEFORE y
    • x NOT AFTER y
      • note that these will also be satisfied if y is not present.
  3. Aliases — v7+
    Whilst there are others these are least likely to be confusing:
    • EQUALS is the same as ANDEQUALS
    • NOT EQUALS is the same as NOTEQUALS

Use INTERSECTS where the search terms may not share the exact same location.
If the text of one search term may not be contained fully WITHIN the other, use INTERSECTS.
Note that INTERSECTS highlights and counts the overlapping text.

For example:
   <Person Jesus> ANDEQUALS <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> WITHIN <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 is the preferred search.

   <Lemma = lbs/el/κύριος> INTERSECTS <Person Jesus> —> will find where “Lord” (κύριος) refers to Jesus in RI’s.
   <Lemma = lbs/el/κύριος> WITHIN <Person Jesus> —> returns the same results in this case.
   <Lemma = lbs/el/κύριος> ANDEQUALS <Person Jesus> —> fails for similar reasons to the above.

   <LogosMorphGr ~ NGSF?> ANDEQUALS (tongue, language) —> would the usual choice for this, but
   <LogosMorphGr ~ NGSF?> WITHIN (tongue, language) —> gives the same results.

   generation WITHIN {Milestone <Bible Lk 11>} —> finds ‘generation’ within the text of Lk 11 (in bibles or commentaries).
   blessed WITHIN {Milestone <Mk 11>} —> finds ‘blessed’ within the text of Mk 11.
   descendant WITHIN {Milestone <LN 10.30-31>} —> finds ‘descendant’ within the text of two Louw-Nida semantic domains.
   Nazareth WITHIN {Highlight Important Events} —> finds ‘Nazareth’ within the (user created) style ‘Important Events’.
   darkness WITHIN {Section <Culture Light>} —> finds ‘darkness’ within the text of the Cultural Concept for ‘Light’.
   darkness NOT WITHIN {Section <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’ is tagged together with Israelites involved in the Conquest of Canaan – should be the same as <Person Israelites (the Conquest)>.
    <Person Israelites> NOT INTERSECTS <Person Israelites (the Conquest)> —> finds ‘Israelites’ who were not involved in the Conquest of Canaan e.g. in the book of Joshua.

   <Person Isaac> INTERSECTS {Speaker <Person Abraham>} —> finds references to Isaac within text spoken by Abraham
   {Speaker <Person Jesus>} INTERSECTS {Section <LiteraryType Quotation, Old Testament>} —> finds all the instances in which Jesus quotes the Old Testament.
   <Gen 3:1–7> INTERSECTS {Milestone <Mt 4:1–11>} —> finds where the story of the Fall is referenced in comments on the Temptation of Jesus.

Filtering with Reference Ranges

Basic Search has a new heading All Passages, similar in use to All Passages in Bible Search. Its use in Morph Search & Bible Search has been extended.
Click it to see a list of the Reference(s) you can enter in order to filter your search. The references suggested will depend on the resources you select
e.g. from the Reference Box of NPNF 1.2, St Augustine, copy the reference Aug., De civ. Dei 1.27 and paste into the Reference Range box of a Basic Search for “suicide”.

Note: You won’t see the heading in Basic Search unless the resources are associated with a datatype.
Tip: You might find this easier than using WITHIN {Milestone...} in the Find box.
Tip: Clear the Reference Range box before entering a range with new resources.


Select Match Equivalent References to get results on the same topic/item with datatypes like Person, Place, Thing, Topic, PreachingTheme.
It has no effect on the <Bible> data type.

For example:
   <Person Holy Spirit> —> will also return results for <Topic Holy Spirit> & <PreachingTheme Holy Spirit>

Searchable Labels

Some types of data are identified as Labels rather than datatypes. The main advantage is the number and search flexibility of their properties
e.g. logical NOT, implicit ANY value.
These may only be available to subscribers or owners of a current Feature Set e.g. Logos 7 Full Feature Set.
See also Searchable Labels in the “Logos Help” resource.

Bible Outline


  • Reference – a Bible reference of the passage being outlined

For example:
    {Label Bible Outline WHERE Reference ~ <Bible Zech 14>}

Journal Article


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

For example:
    {Label Journal Article WHERE Title ~ "Contextual Analysis"}
    {Label Journal Article WHERE Author ~ "Warrington"}
    {Label Journal Article WHERE Topics ~ <Topic Gospel of Luke>}

Lectionary Reading


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

For example:
    {Label Lectionary Reading WHERE References ~ <Bible Zech 14:4>}



  • Title – title of the sermon
  • Subtitle – optional
  • Creator – name of the creator e.g. <Biography John Piper>
  • Series – optional sermon series
  • References – optional Bible references for the sermon as a whole e.g. <Bible Psalms>
  • Date – optional Date reference when the sermon was first delivered
  • Liturgical Date – optional Liturgical Date reference when the sermon was first delivered

For example:
    {Label Sermon WHERE Title ~“Pray for God”} —> partial string match
    {Label Sermon WHERE Series = Prayer} —> exact string match
    {Label Sermon WHERE Date = <Date Jul 9, 2015>} —> exact date match
    {Label Sermon WHERE Date ~<Date Jul 2015>} —> any date in July
    {Label Sermon WHERE References = <Bible Ps 141:1-4>} —> exact reference match
    {Label Sermon WHERE References ~ <Bible Ps 141>} —> any verse in Psalm 141
    {Label Sermon WHERE Creator =<Biography John Piper> AND References ~<Ps 141>} —> any Piper sermon on Psalm 141
    {Label Sermon WHERE Creator ~“User name”} —> use this for your Sermon documents

Figure of Speech

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


  • Name
  • Description

For example:
   {Label Figure of Speech WHERE Name=Aposiopesis}
   {Label Figure of Speech WHERE Description=Sudden-Silence}


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


  • Source – Bible Reference
  • Target – Bible Reference
  • Relationship – Citation | Quotation | Allusion | Echo
  • Corpus – optional New Testament | ... |

For example:
   {Label Intertext WHERE Source ~ <Gen-Mal>} —> finds passages in the NT whose Source is the OT
   {Label Intertext WHERE Target ~ <Mt-Rev>} —> finds passages in the OT that are used in the NT
   {Label Intertext WHERE Source ~ <Gen-Deut> AND Relationship=Quotation} —> finds quotations in the NT that come from Gen-Deut.
   {Speaker <Person Jesus>} WITHIN {Label Intertext WHERE Source ~ <Gen-Mal>} —> finds passages from the OT that were used by Jesus
   {Speaker <Person Moses>} WITHIN {Label Intertext WHERE Target ~ <Mt-Jn>} —> finds OT passages spoken by Moses that were used in the Gospels
   {Speaker <Person Moses>} WITHIN {Label Intertext} —> finds Intertext passages in both OT & NT where the speaker is Moses

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.


  • Genre
  • Attribution

For example:
   {Label Psalm WHERE Genre=Praise}
   blessed WITHIN {Label Psalm WHERE Genre=Praise}
   {Label Psalm WHERE Attribution=David}
   {Label Psalm WHERE 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. These tags enable you to search the proverbs for where a father offers advice. You can even find where God—as a father—offers advice to his children. See Proverbs Explorer Interactive for values to search.


  • Type
  • Form

For example:
   {Label Proverb WHERE Type=Advice}
   father WITHIN {Label Proverb WHERE Type=Advice}
   {Label Proverb WHERE Form=List}

Logos Bible Software Wiki

Welcome, Guest! (sign in)