Topic Guide - No results for suggested Topic

Dave Hooton

Run Topic Guide with Related Topics section.

Run TG on Salvation --> See Also Eternal life (a link to My TG)

Run that TG --> See Also "Eternal State and Death"

Run that TG and get no results --> Search for "Eternal State and Death" and also get no results!

Find more posts tagged with

Comments

Sean Boisen

Thanks, we've discovered there are a number of these, probably legacy data that should have gotten cleaned up. Look for these to go away in a future release.

Sean Boisen

https://community.logos.com/discussion/comment/409330#Comment_409330

Thanks, we've discovered there are a number of these, probably legacy data that should have gotten cleaned up. Look for these to go away in a future release.

As we sometimes find ourselves saying here: "that's not a bug, it's a feature!" [:)]

(Thinking a little more clearly now) These represent topics from our general inventory that happen to occur in a dictionary you don't have (in this case, Wycliffe Bible Encyclopedia). We've annotated more than 50 English resources now: i think it's helpful for users to give them some of the benefit of this (like See Also verses), even if they don't have a specific resource. But i'm rethinking what else we can do for these when they fall outside the user's resources.

Jack Caviness

https://community.logos.com/discussion/comment/409615#Comment_409615

But i'm rethinking what else we can do for these when they fall outside the user's resources.

Offer a discounted opportunity?

Dave Hooton

https://community.logos.com/discussion/comment/409615#Comment_409615

But i'm rethinking what else we can do for these when they fall outside the user's resources.

Google it! At least it found the reference to Wycliffe

MJ. Smith

https://community.logos.com/discussion/comment/409615#Comment_409615

But i'm rethinking what else we can do for these when they fall outside the user's resources.

I agree that the current behavior is not optimal but I also appreciate seeing items outside my resources as it helps be build my expectations of what will and will not work.

Mark Barnes

https://community.logos.com/discussion/comment/409615#Comment_409615

We've annotated more than 50 English resources now: i think it's helpful for users to give them some of the benefit of this (like See Also verses), even if they don't have a specific resource. But i'm rethinking what else we can do for these when they fall outside the user's resources.

As a minimum, a message that says something like "No results in unlocked resources". Ideally, resources that have LCV markup should be tagged over at www.logos.com/products so that users know what's marked up before purchasing. LCV has got to the extent where knowledgeable users will be more likely to buy LCV-tagged resources than non-LCV tagged resources. It would be better if the tag was called "supports Topic Guide" (or similar) rather than "LCV".

Dave Hooton

https://community.logos.com/discussion/comment/409717#Comment_409717

As a minimum, a message that says something like "No results in unlocked resources"

This is also complicated by the collection of resources one currently selects for the Definition section i.e. it may be in a resource I own. I think Logos have to finalize how this section should work and perhaps only suggest topics if they can appear in my Definition section.

Ideally, resources that have LCV markup should be tagged over at www.logos.com/products so that users know what's marked up before purchasing.

This would be excellent!

Dave Hooton

https://community.logos.com/discussion/comment/409615#Comment_409615

As we sometimes find ourselves saying here: "that's not a bug, it's a feature!"

Here's another

Sean Boisen

https://community.logos.com/discussion/comment/410301#Comment_410301

In this case, the Basic Search/Topic section is only searching LCV dictionaries, and the only entry we have for this is the Zondervan Encyclopedia of the Bible, which i'm guessing you don't have. But the Definition section is doing broader matching against resources in your library: hence the mismatch.