Suggestion for Logos 7 -- Tagging Resources with Bundle or Collection associations
I have a suggestion I'd like to see implemented in a future version of Logos. If there is a way to do this now, I would enjoy your feedback!
I have a rather large library, so sometimes it is helpful to search within the various collections and bundles sold by Logos. For example, if I was doing research on the development of Calvinism in church history, it might be helpful to search within the Church History Bundle. My specific suggestion is that each resource be given an additional prepopulated library field that indicates which bundles and collections the resource is part of.
I started to do this in the user tag, but I have too many books for that.
Thanks for your consideration.
Tim
Comments
-
It's worth looking in the Faithlife group about Product Collections - https://faithlife.com/logos-product-collections/documents
this has documents such as:
I'm not at my computer at the moment so can't show you what the document contains
0 -
Sorry
I've checked the "Logos 6 Church History" document (you can add it to your environment from this Faithlife page and it appears as a Collection)
For this particular document it doesn't march the contents of the bundles - but in some other cases the documents do.
0 -
Thanks Graham, I appreciate your suggestions! I wasn't able to get to the page you had indicated above. I do know about the workarounds in which either I or someone else has built a collection document. I'm looking for the embedded functionality in Logos as a durable field for each Library item that contains the bundles and collections in which it is a member. Logos already has this information, but it isn't easily leveraged. For example, when you select a product in the Logos store, there is a pane to the right that tells you which groups and collections it is associated with. I'd like that information as part of a durable tag in the Logos client library.
0 -
Timothy Wallace said:
For example, when you select a product in the Logos store, there is a pane to the right that tells you which groups and collections it is associated with. I'd like that information as part of a durable tag in the Logos client library.
Understood and I can see how it would be useful.
It could be a challenge to implement / manage though as, from time to time, the contents of bundles and packages change so this might require the addition of some sort of "release number".
0 -
There are certainly several implementation options. The first (and easiest) is to maintain the "Collections" tag as a living field, reflecting the current base package, collection, or bundles in which a resource is part of. That would certainly satisfy my needs. The upside is it is very easy to implement for Logos. The downside is as resources move, it could "break" someones special collection depending on the filter term(s) they use. The next (and hardest) to implement is to indicate which base package, collection, or bundles a resource has ever been a part of.
I think the first option is one that could be implemented with relative ease.
Until He returns!
Tim
0
