Prioritized Resource Feature upgrade request

Hello,
I would like to suggest filtering and/or organization be added to prioritized resources panel. I have many prioritized resources and it is difficult to navigate because the software does not organize that panel. Say I have prioritized three dictionaries in a list of thirty prioritized resources. One dictionary might appear 3rd in the list, the next 15th, the last of three 27th. The ability to either filter that panel so that you only see your prioritized dictionaries, or if the panel auto organized resources according to type, would be very helpful. The second of these two suggestions would probably be the most helpful, as a. it would appear that results in the various tools that lean on prioritized resources do so according to type, and b. it would not require as much user knowledge, knowing for instance that Logos lists dictionaries under type:encyclopedia.
Thank You,
Stefan
Comments
-
Stefan Mach said:
The second of these two suggestions would probably be the most helpful, as a. it would appear that results in the various tools that lean on prioritized resources do so according to type, and b. it would not require as much user knowledge, knowing for instance that Logos lists dictionaries under type:encyclopedia.
Welcome [:D]
Please Vote => Prioritize resources by type currently has 24 votes.
Caveat: new feedback website needs a separate login so please vote => Add the feedback website to the Faithlife SSO system that has 7 votes.
Keep Smiling [:)]
0 -
Please Vote => Prioritize resources by type currently has 24 votes.
Now has 26, as I'm struggling with the same difficulty this morning on origination within my library.
0 -
-
Didn’t know this was a thing. But now that I do know, you have my vote added.
WIN 11 i7 9750H, RTX 2060, 16GB RAM, 1TB SSD | iPad Air 3
Verbum Max0 -
<edited>
0 -
Pater Noster said:
In the meantime, if you want a workaround (this request has been around for years) --
Build 1 empty personal docx file. Keep compiling it with different names like this, for example ******** Bibles ********
(....)
Once you have a personal book compiled from the same docx empty file with all the relevant priority names, you can then drag them into the priority list - they don't affect prioritization, as they are blank - but it makes large priority lists (like mine) easy to view, manage, and update! Here's all the categories I believe, they all work for me:
This workaround has been around for years (even pre-dating the personal book feature: people used the Timeline documents in the library). When I see your list, I want to point out a relevant caveat: Logos prioritization internally works by datatype indexes, not (or not only) by library resource type. Those indexes have not been regularly exposed to users in the past - and they overlap between types, and some books have several of them. This makes prioritization even more complex than your example suggests.
Bibles, study bibles, bible notes and bible commentaries all share the same index (the hundreds of bible datatypes are lumped together for this). While guides seem to differentiate between bibles and "the rest", the simple lookup when hovering over a bible reference doesn't, which requires bibles to be prioritized above those to avoid strange system behavior. The rest of those may be at your liking.
Lexicons will utilize Headwords (Greek, Hebrew, Latin) and/or Strongs, Gk-Numbers, TWOT, TDNT... and thus looking up different indexes will follow your prioritization from top down, but only considering those with the respective index. Lexicons are different in giving short definitions and/or glosses and/or lengthy discussions. On the other hand lexicons do have a diverse coverage: some try to tear out the theological meanings of words (but maybe only for a subset of words where this is of significance), others try to be "neutral" or only led by usage, but aim to be exhaustive in coverage. Since sometimes Logos only shows the highest prioritized resource, sometime up to 5, it is relevant to think over which comes in the highest spots not only from a "I like best" perspective, but also under the consideration "I want to see" (example: Spicq's TLNT is theological but not exhaustive. I personally want to see it, thus I make sure it is not crowded out by five exhaustive lexicons that come before it). Those who work with non-tagged bible texts may want to make sure they have analytical lexicons in there to capture all word forms (standard lexicons only work with lemma forms). I may have missed it, but I saw no Greek Septuagint lexicons in your list, which is a worthwhile section (I'd prefer Biblical Greek incl. Analyticals before Septuagint incl. Analyticals before "Standard Greek" - but everyone has their own ideas about that.)
Dictionaries, Encyclopedias, Thesauri, Biblical Concorances and Glossaries will all use English Headwords thus it makes sense to reflect on their order or deliberately put them into one section regardless of type (and not be surprised when a small glossary from a bible comes up first sometimes - to avoid this, Advanced Prioritization can be used or the English Headword indexed resources prioritized above bibles.)
Hope this helps a bit.
EDIT: Pater Noster, I see that you edited out your workaround suggestion and the partial screenshots of your prio list - that was never my intention! It is helpful especially for new users (e.g. former WS-users) to learn how to structure the prio list into meaningful segments, and my comments were not meant to criticise your post, but only to give a bit of additional info for users interested in this topic. You wrote that your large prio list works for you - and that's what is relevant and that is what makes it okay. Others can learn from it and may or may not adopt parts of your practice for themselves.
In fact, prioritization of the various types of resources is a complex effort, that's why people keep asking for a more transparent UI for it and a more easily understood way of prioritizing especially - and using PBs or renamed indexless resources as section dividers, as you showed, is a helpful and needed workaround until we'll see something else from Faithlife. Please consider bringing it back.
Have joy in the Lord!
0