nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tagging issue in PtW Commentary on Mark

Graham Criddle

As per the screenshot below I ran a PG on Matthew 4:16 - and returned a hit from the Preaching the Word Commentary on Mark's Gospel!

As the box at the top-left shows, the Mark commentary has an index entry for Matthew 4:8 which may be contributing to this.

Is this simply a bug or any other thoughts on why this might be happening?

Thanks, Graham

Find more posts tagged with

Comments

Mark Barnes

Is this simply a bug or any other thoughts on why this might be happening?

It's not a bug, it's a feature [;)]. Actually, it's an annoyance, brought about by a compromise between speed/reliability.

In the very early days of Logos 4, in the Passage Guide and parallel resource menu, Logos only used to display resources where the exact reference occurred. The problem was that was very slow. So the feature was changed, so that Logos made an educated guess whether or not the exact reference would be there.

I wonder whether it's time to partly roll-back that decision, given that there have been many other speed improvements, and that most of our PCs are faster now than they were in 2009. If they estimated which resources might hold the data, and then only checked specifically those, I would think that would give good enough performance.

That said, to be solved completely, Logos would need to re-architecture part of their indexing system, but that seems unlikely to happen, sadly.

Graham Criddle

https://community.logos.com/discussion/comment/547625#Comment_547625

It's not a bug, it's a feature . Actually, it's an annoyance, brought about by a compromise between speed/reliability.

In the very early days of Logos 4, in the Passage Guide and parallel resource menu, Logos only used to display resources where the exact reference occurred. The problem was that was very slow. So the feature was changed, so that Logos made an educated guess whether or not the exact reference would be there.

Thanks Mark, I remember the discussion now.