Bug: Bible Browser results incomplete
In testing before responding to this thread, I found that the Bible Browser results are incomplete (in addition to being limited to the NT). The screenshots demonstrate the problem.
According to BB there's only 1 hit in the entire book of 1 Cor.,
yet there should be at least 6 hits in the first two verses alone!
Is this possibly affected by spotty/slow internet? Is my dataset up to date?:
DB:SD-NT-SYNTACTIC-FORCE
2017-04-04T23:28:24Z
NT-SYNTACTIC-FORCE.lbssd
Comments
-
Reuben Helmuth said:
According to BB there's only 1 hit in the entire book of 1 Cor.,
And that is also the result from the Search {Section <SGNTSyntacticForce = prop. name>} (which explains why it is limited to the NT!) i.e. 2 hits in 1 verse.
Dave
===Windows 11 & Android 13
0 -
This looks like an error in the Syntactic Force dataset. If I right-click on Sosthenes in 1 Cor 1:1, it doesn't show "proper name" on the context menu:
A search for {Section <SGNTSyntacticForce = prop. name>} only shows results in one verse in 1 Corinthians (actually in all of Rom–2 Thess):
0 -
This looks like an error in the Syntactic Force dataset.
Thanks for the response Bradley. It looks like you're getting the same results as I am so I assume my syntactic force dataset is up to date...
0 -
Yes; I've reported it to the data team.
0 -
The Lexham SGNT Syntactic Force dataset (in Bible Browser) was automatically extracted from the analysis performed by Dr Lukaszewski in The Lexham Syntactic Greek New Testament, published in 2010.
It represents that particular scholar's analysis of the text, so Faithlife will not be correcting any problems or omissions. (If we ever work with him again to produce a second edition (which is probably unlikely), it might be corrected then.)
0 -
I think I figured out what might have happened. It looks like the different editors of the analysis were not consistent in how they applied "proper name" tagging. If you continue using this dataset, it may be prudent to assume that proper name tagging only applies to the highlighted books:
And there may be other annotation differences between the three editors.
0 -
If you continue using this dataset, it may be prudent to assume that proper name tagging only applies to the highlighted books:
In this case, I'd say it would be better to pull that dataset entirely. Perhaps this would be a good time to reopen the crowd-sourced tagging can of worms! Please let us do it even on a volunteer basis (repayment was a major drawback according to Eli a couple years ago when I submitted a proposal)!
0 -
Reuben Helmuth said:
In this case, I'd say it would be better to pull that dataset entirely.
It would be prudent to do so. Results are clearly unpredictable, and will only generate further comments.
Dave
===Windows 11 & Android 13
0 -
Today (April 1, 2019) an update to this dataset that incorporates proper noun tagging across all books is scheduled be released.
The very nature of this dataset is subjective; each passage should be read as the editor's opinion of the analysis of the passage. It should be treated more like a commentary, less like an objective and comprehensive application of tags representing grammatical phenomena; and that's pretty much how I've described it publicly since this data was originally published.
Rick Brannan
Data Wrangler, Faithlife
My books in print0 -
Rick Brannan (Faithlife) said:
Today (April 1, 2019) an update to this dataset that incorporates proper noun tagging across all books is scheduled be released.
Thanks, Rick. I hope this doesn't have anything to do with the date! 😉
0
