New Feature: Morph Query Builder (Logos Now)
Morph Query Builder is new in Logos 7.2 to the Cloud Feature Set (included with Logos Now membership).
What is it?
A “Morph Query” document is a new document type that can be found on the Documents menu. This document type specifies a query that is run against a new and improved morph search engine under the hood.
What is it for?
It’s a point-and-click user interface for building complex morph queries.
How does it work?
Each Morph Query document specifies a morphological query using a “grid” approach where each column is a word to find with characteristics of that word that you define. The document also specifies:
-
A set of resources to search (eg, SBL Greek New Testament). For Beta 1, this is restricted to just the SBL Greek New Testament. Other resources should follow before launch.
-
A search context that defines the possible extent of each search, which defaults to 10 segments. For now you can only set a different number of segments, but other result contexts such as verse and clause boundaries are anticipated. (If not by launch, soon thereafter.)
-
A set of “constraints” that defines relationships between the terms in the query. For example, if two or more of the segments in the query must agree on case, number, and gender, that is defined as an agreement constraint on the query. If two or more of the segments must be within so many segments of one another, that is a proximity constraint. If two or more of the segments must appear in the results in the order they appear in the query, that is an ordering constraint. These constraints, along with “filtering” (see below) form the backbone of the improvements to the morph search engine.
The new morph search engine requires large databases, so it is an online service. Queries are constructed and saved locally as documents, which must contact the remote server via the Internet to execute the query and retrieve results, which are shown within the current Morph Search panel.
A new feature of the updated morph engine is “filtering,” that is, specifying segments that cannot exist within the search. Set the “Existence” row on any segment to “Does not exist” (defaults to “Exists”) and the entire potential result will be excluded.
Most properties can be given multiple values. You can read the query where each row implies “and” and each value within that row implies “or.” So in the example below, where “verb” is chosen in the “Part of Speech” row, and “participle, infinitive” are both chosen in the “Mood” row, you can read this as “a segment where the part of speech is verb AND the mood is participle or infinitive.”
Multiple columns can also be “merged” together to create alternation groups, that is, to match this segment or that segment.
For example, you could construct a query where there are three segments: Segment 1 is an article, Segment 3 is a ({noun, adjective, adverb} OR {verb, participle}) (ie, a substantive), and Segment 2 is a similarly-described substantive that appears between them in the query, but is marked as “Does not exist” meaning that it cannot appear between them in the result. Then if all three segments are constrained to agree on case, number, and gender, you end up with a query for finding articles (as defined by Segment 1) and following substantives (as defined by Segment 3) which they most likely modify (as defined by the agreement constraints), but with no other agreeing substantives in between (as defined by Segment 2). See figure below:
How do you use it?
Video: https://www.logos.com/logos-pro/morph-bible-search
Create a document that is then attached to an instance of the Morph Search panel. The document defines the search, and the Search panel shows the results.
-
Go to Documents | New | Morph Query to create a new document.
-
Specify your query in the document as described above. (It’s strongly suggested that you give it a name.)
-
Open a Search panel and choose the Morph search type.
-
Click on the down-pointing triangle at the left side of the morph input box (by launch this will be a grid-like icon) and choose the document you just made.
(Alternately, you can start from a Morph Search panel and choose Create morph query document from this menu to start the document from here. Then come back and do steps 2-4 with that newly created document.)
-
The document is now attached, as evidenced by its name appearing in place of the text input control.
-
Click on the document name to open the Morph Query document and edit it. (Edits are live, so you can make changes in the panel and then re-execute the query within the Morph Search panel as often as you need to.)
-
Click the “x” after the document name to detach it and return to the normal morph text input control.
-
Click right arrow in a circle icon at the far right of the same line of the Morph document to execute the search.
Comments
-
We're thinking about changing the name of the document and the feature. Here are the two options we're considering:
- Morph Query (document name) and Morph Query Builder (marketing feature name)
- Morph Search (document name) and Advanced Morph Search (marketing feature name)
Do you favor one of these over another? Or do you have another recommendation?
Thanks for your feedback!
0 -
Phil Gons (Faithlife) said:
Morph Search (document name) and Advanced Morph Search (marketing feature name)
I vote for #2, but I can hear the confusion with the current Morph search already. So possibly a hybrid. A Morph Query document, that is used in our new Advanced Morph Search.
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
This looks really cool by the way :-)
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
Morph Search parallels Syntax Search for the document name.
Morph Query Builder is what people will actually call it ... "Advanced" may lead to expectations that you don't want.
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."
0 -
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
I have fiddled and I am happy.
This is great. Thanks guys.0 -
Phil Gons (Faithlife) said:
Morph Query (document name) and Morph Query Builder (marketing feature name)
My choice.
Dave
===Windows 11 & Android 13
0 -
Phil Gons (Faithlife) said:
We're thinking about changing the name of the document and the feature. Here are the two options we're considering:
- Morph Query (document name) and Morph Query Builder (marketing feature name)
- Morph Search (document name) and Advanced Morph Search (marketing feature name)
I like Morph Query Builder, particularly if it is launched by a button on the Morph search.
My question is, does this Morph Query Builder have capabilities that are not available with command line Morph searches? In particular, will the ability to force agreement/non-agreement of certain morphological features of specific search terms become part of the Morph search command as well? This is one of the most important missing features in current Morph searches.
0 -
Adam Borries (Faithlife) said:
Morph Grid is planned for release in Logos 7.1 to the Cloud Feature Set (included with Logos Now membership).
When it is released, will this only be available through Logos Now or will it become part of Logos 7.x?
If it is part of the Cloud Feature Set, does this mean it will not work unless there is Internet access? (e.g. on a plane or when traveling on a mission trip)
I am thrilled to see this capability coming in Logos. It means potentially I will no longer need to run a virtual machine with an older 32 bit version of Windows, so I can do this type of search with Gramcord.
0 -
As per Adam's post at the top of the thread it will be made available as part of Logos Now and will require Internet access to work
0 -
Morph Query....great tool. Hopefully it will expand (thinking from the NT perspective) to include the LXX and some works from Philo and Josephus. There is frequently a conversation about the characteristics of semitic greek and having enough underlying material allows those questions to be teased out.
0 -
Harry Hahne said:
particularly if it is launched by a button on the Morph search.
It is.
Harry Hahne said:capabilities that are not available with command line Morph searches?
Existence, proximity, agreement and order constraints are included.
Graham has answered the other questions.
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."
0 -
I LOVE this feature! I assume that it will be extended to the OT as well?!!
While I understand the logic for requiring an internet connection, I would STRONGLY plead for the option to download the required databases. If they're seriously too large for any reasonable personal computer, please allow downloading and installing on an external drive on a LAN or something of the sort. I'm joining a Bible translation project in the next year and internet connectivity is understandably limited if it does exist in the area of the world in question, yet it is precisely this type of work that would benefit the most from this ability. Forgive me for saying that IMHO it is a matter of Christian duty to give preference to those areas of Kingdom building that could be considered more "frontline" than some others, i.e. the "priority of the unreached".
0 -
Reuben Helmuth said:
Forgive me for saying that IMHO it is a matter of Christian duty to give preference to those areas of Kingdom building that could be considered more "frontline" than some others, i.e. the "priority of the unreached".
Sorry, but I can't envision a situation where someone out in the hinterland would require the feature. And I suspect that the processing and storage beside being duplicated would also be very slow processing leading to even less demand. If they want to make the feature available, I have no objections other than the use of resources I'd rather have working on more universal needs.
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."
0 -
This strikes me as exactly the kind of functionality that a translator in the thrid world might well need. There are a variety of ways something can be moved into the foreground in a literary work including the clause structures and the syntax used in light of the options available in the language system. This tool is needed to flesh out backgrond from foreground constructions. I'm a little baffeled at the need for centralized processing, both Accordance and BibleWorks have been doing this for years and years. Something is different with the data structures FL is working with, the client / server architecture suggests that their data structures require considerably more "heft" to query? Personally, I'm hoping this feature lets me shed the use of a competing product in my exegetical work. Let me suggest that there are options that don't require an internet connection should FL ultimatly choose the server centric architecture.
0 -
Adam Borries (Faithlife) said:
The new morph search engine requires large databases, so it is an online service.
I am disappointed that this feature requires on online service. I often do research and writing when I do not have Internet access or only have very slow Internet e.g. on an airplane or hiding out in my RV in the mountains, where there is less distraction to my writing. As has been stated, Bible translation missionaries often need this type of capability and rarely have high speed Internet.
It would be great if there were the option to download a specific database or search feature for offline access, much as the mobile app allows downloading a resource or doing an offline search.
As far as the database size goes, the Gramcord database is less than 50MB total for Greek New Testament, Hebrew Bible, and Septuagint, with the morphological tagging to do all of these kinds of searches. The information needed for these searches is already in the various original language Bible texts in Logos. It would appear that only the search engine would need upgraded features (e.g. agreement, non-agreement) and a new user interface would be required. Nevertheless, I am glad to see this capability coming, even if it is tied to a cloud service.
0 -
Harry Hahne said:
As far as the database size goes, the Gramcord database is less than 50MB total for Greek New Testament, Hebrew Bible, and Septuagint, with the morphological tagging to do all of these kinds of searches. The information needed for these searches is already in the various original language Bible texts in Logos. It would appear that only the search engine would need upgraded features (e.g. agreement, non-agreement) and a new user interface would be required.
I very rarely disagree with you and am always pleased to see you in the forums. However, in this particular case I suspect that your model of what is going on behind the scenes is far from what Logos is actually doing ... because of what they have said about adding translations and features, I suspect that one is talking of a data warehouse style of data behind the scenes ... considerably larger and more powerful than the Gramcord style database.
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."
0 -
MJ. Smith said:
I very rarely disagree with you and am always pleased to see you in the forums. However, in this particular case I suspect that your model of what is going on behind the scenes is far from what Logos is actually doing ... because of what they have said about adding translations and features, I suspect that one is talking of a data warehouse style of data behind the scenes ... considerably larger and more powerful than the Gramcord style database.
You may be right about what they plan to do with this feature down the road. This table interface could be used to search any kind of tag. But I still hope that at least the morphological tags can be searched with this interface without access to the cloud.
0 -
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."
0 -
Announcement: release of this feature has been delayed to 7.2. Updated original post accordingly.
0 -
Adam Borries (Faithlife) said:
Announcement: release of this feature has been delayed to 7.2. Updated original post accordingly.
Does this mean this feature it will eventually be provided to anyone with Logos 7 and a morphologically tagged Greek New Testament, without purchasing Logos Now?
0 -
Harry Hahne said:Adam Borries (Faithlife) said:
Announcement: release of this feature has been delayed to 7.2. Updated original post accordingly.
Does this mean this feature it will eventually be provided to anyone with Logos 7 and a morphologically tagged Greek New Testament, without purchasing Logos Now?
No; as per the original post it is still part of the Cloud Feature Set and only available via subscription.
Adam's post is announcing that it will be available in 7.2 (at the earliest) rather than in 7.1 (as originally planned).
0 -
0
-
Gao Lu said:
Understood
Adam explained the reason for it in his first post in this thread
"The new morph search engine requires large databases, so it is an online service. Queries are constructed and saved locally as documents, which must contact the remote server via the Internet to execute the query and retrieve results, which are shown within the current Morph Search panel."
0 -
Adam Borries (Faithlife) said:
How do you use it?
Create a document that is then attached to an instance of the Morph Search panel. The document defines the search, and the Search panel shows the results.
-
Go to Documents | New | Morph Query to create a new document.
-
Specify your query in the document as described above. (It’s strongly suggested that you give it a name.)
-
Open a Search panel and choose the Morph search type.
-
Click on the down-pointing triangle at the left side of the morph input box (by launch this will be a grid-like icon) and choose the document you just made.
I do not have the option for Morph Query in the Documents menu. I also do not see the down-pointing triangle at the left side of the morph input box.
I have Logos 7.1 and am subscribed to Logos Now. I am on the beta channel.
Is there anything I need to do to make this show up as an option?
0 -
-
They have removed it from the beta builds for now. I assume having made the decision to polish 7.1 for release, it will reappear when the beta is more experimental.
0