Bug: Keller Sermon ("TTAG") Linked to Incorrect Scripture Text
The Logos implementation of the Tim Keller Sermon Archive has his September 16, 2001 sermon “Truth, Tears, Anger, and Grace” linked to the incorrect scripture text. The Logos resource itself has the sermon linked to John 14:27, which is not the the main text of the sermon:
Passage Guide results for the correct text--John 11:20-53 do not include this Keller sermon, but Passage Guide results for the incorrect text--John 14:27 do include it:
Accessing the same sermon directly from the Gospel in Life site itself (Redeemer Presbyterian / Keller resources) results in seeing the correct identification with John 11:20-53, rather than John 14:27:
The support info from the Resource Information for the Logos Resource containing the sermon is:
LLS:TMKLLRSRMNRCHVJ
2019-08-22T21:17:52Z
TMKLLRSRMNRCHVJ.logos4
Comments
-
Bumping this in hopes it will get a useful response.
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 -
Thank you, MJ!
0 -
This resource still has the sermon linked to the incorrect scripture text.
0 -
I have reported with the "typo report" feature numerous linking mistakes with this and other sermon archives. For example, in a passage with the main text in Matthew, Keller will make a reference to Acts and use multiple references, but the links are set to Matthew, not Acts. But I never know if these are ever fixed, because I move on. Do we have access to our past reports?
0 -
Rick Carmickle said:
... I never know if these are ever fixed, because I move on. Do we have access to our past reports?
Great question, Rick. Not that I know of. I finally created a notes file for typo reports, so I can revisit typos I've reported, to verify whether any of them get corrected. Anything I reported prior to creating that notes file, I have long forgotten. It would be handy to have a "typos reported" tool, to give us some status feedback on what we have taken the time to report. If something like this already exists, I hope somebody tells us in this thread.
0 -
Scooter, I have not seen any corrections for the 25 or so typos I have reported over the last three or four years. I do not know how many I reported prior to creating my typos notes file, and whether any of those earlier typos have been corrected.
It is worth noting that I do not know how many of the typos I have reported may be attributed to original source material compared to the Logos implementations, but so far it appears that all of my efforts in reporting typos have been fruitless.
What has been your experience with reporting typos?
0
