KYLE: Missing Bible links in two resources

I've got two versions of Daily Light, but in both the Bible references are incompletely and sometimes wrongly linked:
- Daily Light on the Daily Path: www.logos.com/product/167392/daily-light-on-the-daily-path
- Daily Light: Morning and Evening Devotional: https://www.logos.com/product/33375/daily-light-morning-and-evening-devotional
When we go to January 2, both the morning (Isa 42:10) and the evening (Psa 141:2) first Bible references have no link. On January 3 morning reading (Psa 107:7), we find the same problem. January 5 morning reading (Heb. 4:3) points to 2 Tim 4:3, and so on. You got the idea.
Would you be kind enough to help also here, please?
Comments
-
34 bump
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 -
Hi Lucian
Both these resources are Faithlife ebooks, which means that the process of getting them into Logos format is automated.
That does have an impact on the way Bible links are generated.
It should not result in them having no links - so I don't understand why that is happening. But it can result in incomplete references (such as 4:3) being misinterpreted and defaulting to the last book that was specifically mentioned. But, from your description, that doesn't explain what is happening with Heb 4:3 pointing to 2 Tim 4:3
Could you post a screenshot of the 5 January morning reading please so we can see what it looks like?
Graham
0 -
-
Thanks Lucian
Some speculation on my part!
Assuming that the automatic parser used when importing the book doesn't recognise HEB (i.e. all capitals), then the link to 2 Timothy would "make sense" if the previous fully specified reference was to 2 Timothy as well.
Can you check on previous days and see whether that was the case?
If not, I'm out of ideas!
0 -
Thank you, Graham.
The previous reference was 2 Tim 4:6-8, so you nailed the origin of the problem. What's the next step, in your opinion? Is this an immutable "feature" or we could ask for a fix?
0 -
Lucian Benigno said:
Is this an immutable "feature" or we could ask for a fix?
I'm afraid it's a consequence of how these books are generated, as opposed to the more detailed work done when producing a "Logos" version.
Sometimes they do look at particular resources and try to update them but no guarantees.
I've cross-posted in the Faithlife ebooks forum - https://community.logos.com/forums/t/196377.aspx - as it is more likely to be seen there by someone who could address it.
But it is quite probable that there is nothing to be done.
0 -
Graham Criddle said:
I've cross-posted in the Faithlife ebooks forum - https://community.logos.com/forums/t/196377.aspx - as it is more likely to be seen there by someone who could address it.
Thank you again, Graham, for your much-appreciated help.
0 -
Graham Criddle said:Lucian Benigno said:
Is this an immutable "feature" or we could ask for a fix?
I'm afraid it's a consequence of how these books are generated, as opposed to the more detailed work done when producing a "Logos" version.
An additional consequence is that the eBook only works as a monograph (i.e. a book you position yourself in), not like a Calendar Devotional.
One alternative to solve both issues, but involves some work, would be to export the eBook content to Word, there including Day-Of-Year milestones and fixing all bible references the PB compiler doesn't detect automatically (assuming that those would be roughly the same the automated production process for eBooks doesn't catch).
This PB would not be allowed to be shared, due to copyright reasons, but would make sure you can do your daily bible study and get all bible links. I personally am not allowed to purchase the two books you referred to, but I did a proof of concept for one such situation in the past and it worked very well.
Have joy in the Lord!
0 -
Thank you for your contribution, Mick.
Almost always I prefer reading books on my Android device (where the PB doesn't work), but if Faithlife decides not to fix these resources, I'll have this procedure as the better-than-nothing last resort (kind of) solution.
0 -
If you decide to turn it into a Word doc to create a personal book you can replace HEB by Heb using find and replace in Word if all the HEB mentions are used in text references. This should (!) mean that the compiler automatically picks it up as a text reference.
0 -
I don't know the kindest way to say it, so please, people, bear with me.
I'm grateful for your contribution, John and all others that are tracking the origin of the flaw, but I think there's some misunderstanding here. I'm not trying to discover how the error started, but how I can persuade Faithlife to fix these resources. LOL
0