New Feature: Discourse Datasets and Visual Filters (Dataset)
What is it?
Logos' Discourse Datasets and Visual Filters represent the culmination of years of study on discourse features and devices, which speakers and writers of all languages use to convey meaning. The datasets and visual filters constitute a complete discourse analysis of the whole Bible, constructed with graphical representations for numerous communicative devices throughout the Hebrew Old Testament and Greek New Testament. The datasets are searchable, so you can find every occurrence of direct address in the Old or New Testaments. And with the use of our reverse interlinear data, you can use the Discourse features visual filters to view these annotations in several different English, Greek, or Hebrew bibles.
How does it work?
Open any of your Bibles with a reverse interlinear. Navigate to the visual filters icon. From here, you can enable the Discourse Features (Greek) or Discourse Features (Hebrew) visual filters as a whole, or you can individually select the feature you want exposed in your English translation (or Greek and Hebrew texts).*
You can also search the dataset. The syntax for this search for the Greek dataset is <LDGNT = Overspecification> in the basic search. To search the Hebrew dataset use <LDHB = Overspecification>.
The easiest way to search this dataset, however, is to have the visual filters enabled, locate the feature you want to investigate further, right click on any of the words tagged with the feature you're investigating, and select that option from the context menu to search. Logos will automatically generate the search syntax for you.
* Please note that the discourse dataset was developed for the NA28 and the SBLGNT. Accordingly, if you enable the visual filters on a Byzantine Greek text or translation heavily dependent on the Byzantine textual tradition (e.g. KJV), there may be significant discrepancies between the data within this dataset and the text itself.
Where can I learn more?
- Watch this feature in action here: https://logos.wistia.com/medias/q4kqk0jfvh
Comments
-
Jacob Cerone said:
Open any of your Bibles with a reverse interlinear. Navigate to the visual filters icon. From here, you can enable the Discourse Features (Greek) or Discourse Features (Hebrew) visual filters as a whole, or you can individually select the feature you want exposed in your English translation (or Greek and Hebrew texts).*
Definitely do not see this yet. I am a Now subscriber, running 6.12 Beta 2
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
James Taylor said:
Definitely do not see this yet. I am a Now subscriber, running 6.12 Beta 2
If you're not seeing it, I may have jumped the proverbial gun on the post. Be patient and I suspect that you will see it by tomorrow. In the meantime, I will check to see if the license has been issued.
0 -
Jacob Cerone said:
Be patient and I suspect that you will see it by tomorrow. In the meantime, I will check to see if the license has been issued.
Ok, I'll check back. thanks Jacob. Just to clarify on this dataset, is this basically the data we'd already have if we own Runge's discourse resources (HDNT, LDGNT, LDHB etc.) but we'd be gaining the ability to search this data as well as filter it on to any Bible with a reverse interlinear?
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
James Taylor said:
Ok, I'll check back. thanks Jacob. Just to clarify on this dataset, is this basically the data we'd already have if we own Runge's discourse resources (HDNT, LDGNT, LDHB etc.) but we'd be gaining the ability to search this data as well as filter it on to any Bible with a reverse interlinear?
Correct—though not just the New Testament but also the Old Testament.
0 -
Jacob Cerone said:
also the Old Testament.
Yes, owners of Lexham Discourse Hebrew Bible have already had access to that as well.
But this could now be filtered across English Bibles too
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
This is awesome.
0 -
Ryan Robinson said:
This is awesome.
Are you seeing this already, or just saying its (going to be) awesome (when it gets here)?
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
0
-
Ok, just making sure I wasn't having a bug or something :-)
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
Jacob Cerone said:James Taylor said:
Definitely do not see this yet. I am a Now subscriber, running 6.12 Beta 2
If you're not seeing it, I may have jumped the proverbial gun on the post. Be patient and I suspect that you will see it by tomorrow. In the meantime, I will check to see if the license has been issued.
We're hoping to upload the new datasets sometime today (Tuesday, May 3, 2016).
Thanks!
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
Rick Brannan (Faithlife) said:
We're hoping to upload the new datasets sometime today (Tuesday, May 3, 2016).
I'm told these have been uploaded, so they should soon be available for Logos Now users.
We'd love if y'all on 6.12 beta 2 could specifically poke at:
- The visual filter menu in the resource panel. Try selecting/unselecting combinations of features for display.
- Different reverse interlinear resources using the visual filters
- Searching via right-click.
- Searching using the <LDHB = ...> and <LDGNT = ....> syntax (and/or using ~ instead of = ).
Thanks!
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
Will this still work if you are on 6.11?
0 -
Ryan,
If I'm not mistaken, the dataset itself (i.e. running searches from the context menu) should work. The visual filters aspect, however, will be in 6.12.
0 -
Ryan Robinson said:
Will this still work if you are on 6.11?
The visual filters are only available starting in 6.12, which will be available to non-Beta testers in a few weeks. However, Logos Now subscribers running 6.11 will get the datasets now. You can use them to search by using syntax like {Section <LDGNT = Overspecification>}, whereas in 6.12 you can just use <LDGNT = Overspecification>. There are two known issues with the context menu in 6.11:
- the search syntax generated by the context menu will not include the {Section ...} syntax, so the searches won't work in 6.11 unless you manually fix the search syntax
- the context menu will usually show two LDGNT entries for words in the New Testament. This is fixed in 6.12.
0 -
Jacob Cerone said:James Taylor said:
Ok, I'll check back. thanks Jacob. Just to clarify on this dataset, is this basically the data we'd already have if we own Runge's discourse resources (HDNT, LDGNT, LDHB etc.) but we'd be gaining the ability to search this data as well as filter it on to any Bible with a reverse interlinear?
Correct—though not just the New Testament but also the Old Testament.
Great! So, we don't need to purchase Runge's discourse resources (HDNT, LDGNT, LDHB etc.) to use this feature?
For book reviews and more visit sojotheo.com
0 -
John Kight said:
Great! So, we don't need to purchase Runge's discourse resources (HDNT, LDGNT, LDHB etc.) to use this feature?
If you're a subscriber to Logos Now, you don't need to purchase those resources. When 6.12 goes stable, I'm told there will be information made available regarding if and how someone who is not a Logos Now subscriber could obtain these datasets.
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
Rick Brannan (Faithlife) said:
If you're a subscriber to Logos Now
Thanks Rick! Logos Now just keeps getting better and better!!
For book reviews and more visit sojotheo.com
0 -
Rick Brannan (Faithlife) said:John Kight said:
Great! So, we don't need to purchase Runge's discourse resources (HDNT, LDGNT, LDHB etc.) to use this feature?
If you're a subscriber to Logos Now, you don't need to purchase those resources.
But will Lexham Discourse Greek New Testament Glossary be made available to Now subscribers?
Dave
===Windows 11 & Android 13
0 -
Using adventure and community to challenge young people to continually say "yes" to God
0 -
This is awesome!
One request....the VF menu is getting longer and longer, esp if you are someone like me with LOTS of VFs, highlighting notes, etc. As such, would you guys consider 2 VF menus, one for Resource and Discourse features, and the other for our personal VFs (VF documents, highlighting notes, etc). I think this would make the menu much cleaner. I don't see any reason why there couldn't be two VF buttons at the top of a resource, esp given how little landscape space they consume on the resource bar.
Just a thought.
Thanks!
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
I'd prefer a single menu with all expandable units closed by default ... I agree with your diagnosis of the problem.
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 -
Dave it just downloadet today
0 -
Thanks for this new feature.
This leads to another request (or a repeat of an earlier request), which is to make it possible for different visual filters to be placed on the same resource (so in one panel I could have a high-definition NIV, and in another panel I could have a 'normal' NIV with all my highlighting, etc.)
The way multiview is handled is perfect. There, multiview selections are saved with shortcuts/layouts, so I can quickly switch between different multiview configurations. The more visual filters you create, the more we need something similar for visual filters.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
Thanks for this new feature.
This leads to another request (or a repeat of an earlier request), which is to make it possible for different visual filters to be placed on the same resource (so in one panel I could have a high-definition NIV, and in another panel I could have a 'normal' NIV with all my highlighting, etc.)
The way multiview is handled is perfect. There, multiview selections are saved with shortcuts/layouts, so I can quickly switch between different multiview configurations. The more visual filters you create, the more we need something similar for visual filters.
[Y]
0 -
Dave Hooton said:
But will Lexham Discourse Greek New Testament Glossary be made available to Now subscribers?
My understanding is that both the LDHB and LDGNT Glossaries will be made available in Logos Now too.
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
Lawrence Rafferty said:
- the search syntax generated by the context menu will not include the {Section ...} syntax, so the searches won't work in 6.11 unless you manually fix the search syntax
- the context menu will usually show two LDGNT entries for words in the New Testament. This is fixed in 6.12.
Both of these issues have been fixed with 6.11 SR-2
0 -
Rick Brannan (Faithlife) said:
My understanding is that both the LDHB and LDGNT Glossaries will be made available in Logos Now too.
thanks, Rick.
Dave
===Windows 11 & Android 13
0 -
Where can I get:
1. a manual or a short manual/ explanation on this Discourse Datasets and Visual Filters (Dataset)
2. a video on how it works
I have Logos Now and it will be nice to have a in ditto explanation in manual and video on how I can use it.
The videos and explanation of Logos is very nice and important.
0 -
AH Bogaards said:
Where can I get:
1. a manual or a short manual/ explanation on this Discourse Datasets and Visual Filters (Dataset)
2. a video on how it works
The Discourse visual filters are in beta during the 6.12 cycle; at the end of the beta cycle the material should become available. Access to the LDGNT and LDHB introductions and glossaries should happen, I'd guess, in the next week.
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
So, for users who already own the rather expensive discourse databases and also subscribe to Logos Now, if I understand correctly, the only value in owning databases would be the permanent license rather than a temporary license (i.e., for LDHB, LDGNT, LHDOT, LHDNT)? Until fairly recently LDGNT was, in my evaluation, a useful but significantly unfinished beta product (with respect to widespread typos, omissions, and errors), although thankfully it's now improving significantly, especially since updates from around late 2015 and early 2016. That said, I wouldn't have invested in them if I didn't value them. I recall the Greek New Testament Discourse Bundle being a good value.
These new discourse visual filters and improved search databases look like an excellent and natural extension of the work that's been done on the discourse resources. I've always thought that Propositional Outlines would work well with some of the discourse-device symbols such as Topical Frames and Emphasis (e.g., for marked focal constituents). The Propositional Outlines really build on and extend the analysis of LDGNT and LDHB, but I think I'd prefer if they labeled devices such as simple Topical Frames with some of these symbols rather than placing them on their own line and thus separating them from their larger propositional and prosodic units/groupings. I don't think this facilitates fluent, uninterrupted reading. Anyway, I look forward to seeing how these different visual filters interact and complement one another.
Thanks to everyone involved in these projects! Keep up the good work!
0
