NEW Logos Now Feature: Faithlife Assistant

Philana R. Crouch
Philana R. Crouch Member, Logos Employee Posts: 4,597
edited November 20 in English Forum

Faithlife Assistant is a new tool for searching with natural language. Just enter your questions to find information about people, places, and themes in the Bible, theological topics, how to use Logos, and your Faithlife account.
 
Here are some examples of the type of questions you can ask Faithlife Assistant:
* Who is Jesus?
* Tell me about grace?
* Read John 3:16-17.
* Open a Bible Word Study on love.
* I need a verse about patience.
* How do I export my sermon?
 

How do I find Faithlife Assistant?

You can open Faithlife Assistant from the Tools menu or by using CTRL+Space or CTRL+Alt+D. Submitting your query with CTRL+Enter will force an audio response. Using CTRL/CMD+Esc will clear the history.

 
Please help us improve Faithlife Assistant by submitting your feedback through this Google Form.

«1

Comments

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    I am not sure I am getting how this is different from a regular search. Can you give us some scenarios where this tool would be preferred over a regular search?

    It seems when I type a question it opens either a factbook or everything search.......so why the extra step???

    I do not want to come across a "negative". Trying to understand how to use it best. :) Thank you for your great work!

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    I am curious if this is a "work in progress?" See my screenshot below.....the first couple questions are somewhat difficult but would be helpful to have that type of "AI" (?) but the last few questions are basic and I was not able to get a answer.......



  • xCurt
    xCurt Member Posts: 2

    as it says in line 1: First type "help" and read how to ask

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    I am not sure I am getting how this is different from a regular search.

    I believe that this might be an attempt to provide a "Tell Me" search assistant like the one you can find in Microsoft office products and in other software. I asked for this a while ago.

    If it is what I think (I don't have LN so I cannot test), its use will at times overlap with but still differs from regular search commands. The idea would be to be able to find more easily commands by using natural language instead of having to know the exact command syntax (think fuzzy command box). 

    In some cases if the question is close to existing commands, the result will be anticlimactic ("how do I search for grace" will presumably just initiate a basic search for grace). But it gets more interesting with "how do I export my sermon". Normally the word "my" would not be recognised in a literal command syntax, but an assistant is able to focus on keywords (export, sermon) to figure out what you want. It will be good to hear from those who have it how it works out.

    I would love to see how it behaves in relation to complex searches. 

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    Francis said:

    I would love to see how it behaves in relation to complex searches. 

    Give me an example and I will try it.....

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    as it says in line 1: First type "help" and read how to ask

    Really?

  • Gregory Lawhorn
    Gregory Lawhorn Member Posts: 982 ✭✭✭

    Francis said:

    I would love to see how it behaves in relation to complex searches. 

    I would, too. I typed in "What questions did Jesus ask Peter" and it couldn't make sense of it. So much for "natural language" parsing. It's a cool idea, but doesn't seem ready for release.

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    I can only conjecture since I don't have access to the tool: my take would be that (1) In typical Faithlife fashion, the tool when first introduced is rudimentary. In other words, it may be able to handle questions later that it cannot for now (it will grow); (2) A search assistant is not a google search: it might put more emphasis on finding how to find something than finding something complex. Not sure about that but try:

    How do I find questions Jesus asked Peter and tell me if it works better.

    Note that "How do I" is boldened in the first post in this thread as well as other type of questions. 

    This might work better than random questions such as "were there Indians who ate rice in ancient Israel?"

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    Francis said:

    I would love to see how it behaves in relation to complex searches. 

    Give me an example and I will try it.....

    Well let's start easy (not really complex) and see how it goes:

    "how do I search for the Trinity in sermons?"

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    Francis said:

    "how do I search for the Trinity in sermons?"

    Nothing.......but if I search for "How do I make notes/a visual filter?" it opens up a notes/visual filter document. Maybe it's meant to be a glorified "Help" tool.

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    Maybe it's meant to be a glorified "Help" tool.

    When I use the assistant in MS Office (or Cortana in Windows 10), the idea is to be able to access commands and content when we do not remember exactly how or where or else it is just faster to use the assistant. But as I said before, I would not be surprised if in its first instalment it is quite limited in what it can do.

    But we may get more details from Faithlife or others in the know soon.

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    A few that work:

    • hello / hi / how are you / i love you / what is your name
    • what is todays date / what is today [ Don't know yet if this recognizes holidays, esp religious holidays / holy days / saints? ]
    • todays verse / show me todays verse [Doesn't work: what is todays verse / what is todays verse art ]
    • create a new note [Doesn't work: Start a new note]
    • take a note on John 3:16 / create a note on John 1:1
    • open a new sermon / start a new sermon / create a new sermon
    • open esv
    • open acts / go to acts 1
    • open nkjv to acts
    • open lectionary
    • define grace / what is grace / tell me about grace
    • run a passage guide on john 1:1 / run exegetical guide on John 1:1 [Doesn't work using the common abbrevs PG, EG]
    • run a word study on grace [NOTE: prints to screen "Opening Bible Word Guide for grace", you'd think then that the command "open bible word guide to grace" would work... ]
    • who is joseph
    • where is bethlehem [!!! I want atlas not factbook]
    • compare jn 1.1
    • check for updates
    • what is factbook / what is atlas
    • how do you pronounce agape [ still doesn't do anything but bring up pronunciation ]

    Any commands that the old command box recognizes should work.

    We need a global hotkey to launch voice recognition at any time from anywhere in the app.

    I'd love to know if this is still actively under development. I haven't seen any mention of updates to the vocabulary / abilities.

    EDIT: To partly answer my own question: I do some things have been added from the suggestion form

    • search my bible for peace
    • show me something cool

    I'm really looking forward to progress on FA. Thanks.

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    We've just added a list of some example commands. Type help and hit enter, then click on the link at the end of the response. It should take you to https://wiki.logos.com/Faithlife_Assistant_Commands.

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    Francis said:

    But as I said before, I would not be surprised if in its first instalment it is quite limited in what it can do.

    It doesn't recognise many Logos 7 Commands (for the Command box), and is very limited with Search e.g.

    Search for <Person Jesus>   is recognised as a Everything Search for Person Jesus 

    search for culture light  is recognised as a Everything Search for culture light

    Search for are the keywords. It won't recognise Culture as search extension/datatype if it can't recognise <Person Jesus>


    Dave
    ===

    Windows 11 & Android 13

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    We've just added a list of some example commands. Type help and hit enter, then click on the link at the end of the response. It should take you to https://wiki.logos.com/Faithlife_Assistant_Commands.

    Woot! That's a huge improvement over what I had read about or stumbled on. Thanks to Adam and team. Looking forward to going through the list and forward to what's more to come.

  • Mike Tourangeau
    Mike Tourangeau Member Posts: 1,547 ✭✭

    I am beginning to see a few uses for this. I am sure it will be very helpful. The one that I like the most right now is "Show me a map of <insert location>"

    I wonder if they will remove the command bar and dedicate more space for shortcuts? Looking forward to seeing how this tool can be utilized

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    Could someone edit the wiki and categorize it so that it's easier to browse? Here's a quick & dirty categorization with nothing added/removed and very minimal rearrangement within the list. Someone might have better ideas for categorizing...

    2543.FA.txt 

  • Could someone edit the wiki ...

    Please accept your invitation to the Logos Wiki Editors, which will enable you to edit => https://wiki.logos.com/Faithlife_Assistant_Commands

    FYI: Logos Wiki has => How to edit the Logos Wiki

    Keep Smiling [:)]

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    Search for are the keywords. It won't recognise Culture as search extension/datatype if it can't recognise <Person Jesus>

    Have you tried to play around with the "browse" commands? I am wondering if the examples below (from Philana's list) are essentially substitutes for "search" and give us clues as to how searches may be syntaxed (but then again, if we are back to having to syntax natural questions properly, it defeats the purpose, doesn't it?):

    Browse verses on the topic of foreign trade
    Browse verses where the figurative language category is structural metaphor
    Browse verses where the intertext relationship is echo
    Browse Bible pericopes having an intertext relationship of allusion
    Browse Bible pericopes where the figurative language target is authority
    Browse Bible including a miracle of provision
    Browse Bible where the figurative language source is the law
    Browse Bible where the figurative language target is the message that Jesus is the Christ
    Browse Bible where the figurative language type is to hear as to learn

    How about Browse Bible where the speaker is Jesus?

    I noticed that none of the "browse" commands apply to anything else but Bibles. I assume that they will broaden commands. I also wonder whether the result appear inline (or else in what form they are displayed).

    It is as of yet not altogether clear what exactly Faithlife wants to do with the Assistant. I hope it is clearly defined enough that it won't be a mess. For my part, I would prefer a concept of assistance which helps find what is already there rather than creates new vocabulary yet (e.g., "browse" which as far as I can tell was not in use before). The idea of an assistant should precisely be that of dispensing with knowing precise vocabulary and having a broader scope of intelligent suggestions. 

    For instance, in Microsoft Word, I know there is a command to shrink a document by one page but I can never remember where it is found on tabs. All I need is to type "shrink" in the "Tell me" box (blue field in the image below) and it instantly comes up as a suggestion (grayed options are those that are contextually not available, eg, "demote shape or bullet" is grayed because there are no shapes or bullets in the document).

    The same applies to other commands, 

    Now of course, the examples above only rely on one keyword whereas we want to be able to use permutations of commands. Nevertheless, I hope that however it is implemented, it will depend mostly on existing vocabulary while reducing the need to know syntax. So, to take up your example of a search for <Person Jesus> I would not want to see the symbols <> required to make it work but that natural language such as "the person Jesus" or "Jesus as a person" would produce the suggestion to search for <Person Jesus>.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    Francis said:

    rather than creates new vocabulary yet (e.g., "browse" which as far as I can tell was not in use before)

    Bible Browser.

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    Francis said:

    rather than creates new vocabulary yet (e.g., "browse" which as far as I can tell was not in use before)

    Bible Browser.

    My point was that "browse" was not an existing command. Do the browse lines in the Faithlife Assistant specifically invoke the Bible browser?

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    Could someone edit the wiki ...

    Please accept your invitation to the Logos Wiki Editors, which will enable you to edit => https://wiki.logos.com/Faithlife_Assistant_Commands

    Thank you, Keep Smiling. I organized the page a bit. Roughly, not having tried all the commands yet.

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    Francis said:

    I would not want to see the symbols <> required to make it work but that natural language such as "the person Jesus" or "Jesus as a person" would produce the suggestion to search for <Person Jesus>.

    I couldn't get Browse commands to work following the example 'syntax' from the Bible Browser e.g.

    Browse bible where the people is Jesus

    Browse Bible where the reported speech speakers is Jesus

    and likewise for

    Browse bible where the person is Jesus

    Browse Bible where the Speakers is Jesus

    Browse Bible where the Speaker is Jesus

    Dave
    ===

    Windows 11 & Android 13

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    I couldn't get Browse commands to work following the example 'syntax' from the Bible Browser e.g.

    I just noticed that Rev 1 examples include many more that do work but are not listed in the final posted examples. Check History.

    Browse pericopes where Jesus speaks 

    Browse pericopes where Jesus speaks to a fig tree

    (pericopes seems to always be not set in all browse commands I've tried so far.)

  • Francis
    Francis Member Posts: 3,816 ✭✭✭

    Browse pericopes where Jesus speaks 

    What does this produce: a Bible search window with {Speaker <Person Jesus>} searched for? The Bible browser with Jesus selected as speaker?

    (pericopes seems to always be not set in all browse commands I've tried so far.)

    Not sure what that means.

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    Francis said:

    Browse pericopes where Jesus speaks 

    What does this produce: a Bible search window with {Speaker <Person Jesus>} searched for? The Bible browser with Jesus selected as speaker?

    The latter. All of the Browse queries open the Bible Browser. Reported Speach => Speakers => Jesus, which is equivalent to a bible search for {Speaker <Person Jesus>}. Bible Browser queries have some hole but there are more options than for regular search.

    I'm not sure that FA will be an advanced (for some definition of advanced) search tool or not soon. I think of it as more useful in two situations: 1) rabbits/trivia: you want a quick ballpark answer to a passing question: Who wrote Hebrews? How long is 50 cubits? Where was Moses born? When was David king? Will I ever finish my payment plan? 2) A Learning tool, both by direct query: How do I ... ? What is ... ? and by example by opening up the proper tool with the proper parameters when given a basic question: What did Jesus say about forgiveness? Where is Goshen? How many times did Jesus mention Grace?

    Francis said:

    (pericopes seems to always be not set in all browse commands I've tried so far.)

    Not sure what that means.

    The Bible Browser has the option in the upper right corner to view results by Verse or by Pericope. 

    Browse verses where Jesus speaks => correctly sets Browser to By Verse

    Browse pericopes where Jesus speaks => does not set Browser to By Pericope on any of the example searches I have tried.

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    Can we have a way to go directly to voice? A hotkey? A verbal que: Shalom FA. Peace FA. Maybe a hand off from Cortana? Hey, Cortana. Can you get FA on the line?

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    Can we have a way to go directly to voice?

    Ctrl+Space will open the Faithlife Assistant panel. Ctrl+Space again will start listening.

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    Can we have a way to go directly to voice?

    Ctrl+Space will open the Faithlife Assistant panel. Ctrl+Space again will start listening.

    Thank you! I had missed that.

  • Kevin A. Purcell
    Kevin A. Purcell Member Posts: 3,408 ✭✭✭

    My evaluation of FL Assistant.

    In a desktop application I will probably NEVER use it. Not because it's bad or good, It might be GREAT but I don't want to talk to my computer. There are too many of these voice activated tools and having another thing to talk to isn't helpful to me.

    Make this work on Alexa or Google Assistant as an add-in skill and I might use it if it has a few useful abilities like...

    1. Read a passage in a translation
    2. Play content available in my library - audio from my courses etc.
    3. Play X video on my TV with the FLTV app chromecasting from my phone or tablet
    4. How many times is the word Truth used in Proverbs or something like that.

    Just my $.02

    Dr. Kevin Purcell, Director of Missions
    Brushy Mountain Baptist Association

    www.kevinpurcell.org